Battery management embedded software architecture

Through the embedded software architecture of battery management, the battery model and management strategy are described in XML format, the maintenance problems of battery types and equipment diversity of different projects are solved, and the rapid generation of executable programs and unified management are achieved, which reduces maintenance costs.

CN118885166AActive Publication Date: 2024-11-01LBATTERYCLOUD CO LTD +1
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202410910575.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-08
Publication Date
2024-11-01
Estimated Expiration
2044-07-08

AI Technical Summary

Technical Problem

The various types of batteries and management strategies used in different energy storage projects have led to problems such as large maintenance workload, confusing software versions, and difficult to trace and maintain.

Method used

Provides an embedded software architecture for battery management, including human-computer interaction layer, interface packaging layer, logic processing layer and hardware interface layer. It describes battery models and management strategies through XML format to achieve unified management of different battery types and devices, dynamic Edit the battery management policy process to suit different project needs.

Benefits of technology

It realizes the rapid generation of executable programs for different project requirements, reduces maintenance costs, supports the management of different types of batteries, and does not require software modification, simplifies maintenance of different projects.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118885166A_ABST
    Figure CN118885166A_ABST
Patent Text Reader

Abstract

The invention discloses a battery management embedded software architecture, and relates to the field of new energy, and the software architecture comprises a man-machine interaction layer which receives an operation instruction and displays the current state and battery data of a battery cluster; the interface packaging layer is used for packaging an external interface, sending a packaging result to the man-machine interaction layer and receiving an operation instruction; the logic processing layer calls a corresponding battery model according to the operation instruction, applies a battery management strategy, generates a control instruction, determines the current state and battery data of a battery cluster, and sends the current state and battery data to the man-machine interaction layer through the interface packaging layer; the equipment access layer uniformly packages communication protocols of battery management systems of different manufacturers, accesses corresponding equipment operation interfaces according to the control instruction to obtain parameters of a preset hardware interface, and generates a calling instruction; and the hardware interface layer is used for carrying out secondary packaging on the preset hardware interface and sending corresponding preset data to the preset hardware interface according to the calling instruction. According to the invention, different projects can be maintained more conveniently.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of new energy, and in particular to a battery management embedded software architecture. Background Art

[0002] At present, in the application field of energy storage projects, the following problems mainly exist in the process of project implementation and development:

[0003] 1. Different projects use different types of batteries, including lithium iron phosphate batteries, ternary lithium batteries, sodium ion batteries, etc. Different batteries have different battery parameters and models.

[0004] 2. Different projects have different types of third-party manufacturers' BMS, energy storage inverters and other equipment, and various communication interfaces and protocols.

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

[0006] At present, for different projects, a set of battery management software needs to be maintained separately for each project. With the increase of projects, it is easy to encounter problems such as large maintenance workload, many maintenance contents, and confusion of different software versions that are difficult to trace and maintain. Summary of the invention

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

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

[0009] The present application provides a battery management embedded software architecture, 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 instructions and display the current status and battery data of the battery cluster;

[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 results to the human-computer interaction layer, and 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 the battery management strategy to the battery model, and generate control instructions according to the battery management strategy, determine the current state and battery data of the battery cluster, and send them to the human-computer interaction layer through the interface encapsulation layer; the control instructions include obtaining data of the preset hardware interface and sending corresponding preset data to the preset hardware interface; the battery model describes the parameters of the battery through a description file in XML format; the parameters include the battery's charge and discharge cut-off voltage, the battery's temperature and the corresponding relationship between the maximum charge and discharge power, and the battery's charge and 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 of different manufacturers, and access the corresponding device operation interface according to the control instruction to obtain the parameters of the preset hardware interface, and generate a call instruction;

[0014] The hardware interface layer is connected to the device access layer; the hardware interface layer is used to perform secondary packaging on 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 interface.

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

[0017] Optionally, the battery management strategy describes the execution steps through a description file in XML format.

[0018] Optionally, the battery management strategy includes a startup process, a shutdown process, a charge and 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 a current state of the battery cluster according to a result of the comparison; the current state includes a fault state, a full state, and an empty 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 a memory in a key-value manner.

[0021] Optionally, during the charging process, when the collected voltage data of the battery module in the battery cluster exceeds the battery module charging cut-off voltage configuration value stored in the memory, the battery module is marked as being in a fully charged state;

[0022] During the discharge process, when the collected voltage data of the battery module in the battery cluster is lower than the battery module discharge cut-off voltage configuration value stored in the memory, the battery module is marked as being in a discharge state;

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

[0024] During the charging process, when the collected voltage data of each electric cell in the battery module of the battery cluster exceeds the single cell charging cut-off voltage configuration value stored in the memory, the battery module is marked as being in a full state;

[0025] During the discharge process, when the collected voltage data of each electric cell in the battery module of the battery cluster is lower than the single cell discharge cut-off voltage configuration value stored in the memory, the battery module is marked as being in a discharge state;

[0026] During the charging and discharging process, when the collected voltage data of each electric cell in the battery module of the battery cluster is lower than the single cell fault voltage configuration value stored in the 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 an empty state, the battery cluster is marked as being in an empty state;

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

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

[0031] The present application provides a battery management embedded software architecture that can quickly generate executable programs for different project requirements by dynamically editing the battery management strategy process; and can accommodate 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 A schematic diagram of a battery management embedded software architecture provided for this application;

[0034] Figure 2 This is the architecture diagram of the energy storage battery management system provided for this application. DETAILED DESCRIPTION

[0035] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0036] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

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

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

[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 results to the human-computer interaction layer, and 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 the battery management strategy to the battery model, and generate control instructions according to the battery management strategy, determine the current state and battery data of the battery cluster, and send them to the human-computer interaction layer through the interface encapsulation layer; the control instructions include obtaining data of a preset hardware interface and sending corresponding preset data to the preset hardware interface; the battery model describes the parameters of the battery through a description file in XML format; the parameters include the battery's charge and discharge cut-off voltage, the battery's temperature and the corresponding relationship between the maximum charge and discharge power, and the battery's charge and 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 of different manufacturers, and access the corresponding device operation interface according to the control instruction to obtain the parameters of the preset hardware interface, and generate a calling instruction.

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

[0043] Specifically, the preset hardware interface includes RS485, CAN, SPI, IIC and Ethernet interface. The battery management strategy is programmable. The battery management strategy describes the execution steps through a description file in XML format. The battery management strategy includes a startup process, a shutdown process, a charge and 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 according to the comparison result; the current state includes a fault state, a full state, and an empty state.

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

[0046] During the charging process, when the collected voltage data of the battery module in the battery cluster exceeds the battery module charging cut-off voltage configuration value stored in the memory, the battery module is marked as being in a fully charged state.

[0047] During the discharge process, when the collected voltage data of the battery module in the battery cluster is lower than the battery module discharge cut-off voltage configuration value stored in the memory, the battery module is marked as being in an empty state.

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

[0049] During the charging process, when the collected voltage data of each electric body and cell inside the battery module in the battery cluster exceeds the single cell charging cut-off voltage configuration value stored in the memory, the battery module is marked as being in a fully charged state.

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

[0051] During the charging and discharging process, when the collected voltage data of each electric cell inside the battery module in the battery cluster is lower than the single cell fault voltage configuration value stored in the 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 in a fully charged state, the battery cluster is marked as being in a fully charged state.

[0053] During the discharge 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.

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

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

[0056] The software architecture is designed from bottom to top as follows:

[0057] BOS-HIL layer (battery operating system hardware interface layer) is responsible for the unified encapsulation of hardware interfaces.

[0058] BOS-HDL layer (battery operating system hardware device layer) device access layer. This layer is responsible for the communication protocol interface encapsulation of various peripherals.

[0059] 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] BOS-API layer (battery operating system Application Programming Interface) is the API interface encapsulation layer of the above three layers. This layer is responsible for the unified encapsulation of the functional interfaces of BOS-HIL, BOS-HDL and BOS-CORE layers.

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

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

[0063] The BMS inside the battery pack includes the functions of collecting the internal voltage, current, temperature, single cell voltage and open circuit voltage of the battery pack. At the same time, the BMS also includes the charging and discharging control functions of the current pack.

[0064] The BOS-HIL layer is used to repackage common hardware interfaces, mainly RS485, CAN, SPI, IIC, Ethernet interfaces, etc. It also repackages network operation and file system operation interfaces to facilitate compatibility with different operating systems. In addition, the BOS-HIL layer also repackages some operating system interfaces that need to be used, mainly including semaphores, mutexes, system clock acquisition, delay function interfaces provided by the system, etc. This facilitates the porting and operation of software architecture on different operating systems.

[0065] The BOS-HDL layer is used to uniformly encapsulate the communication protocols of BMSs from different manufacturers, supporting data access and control of different models of BMSs.

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

[0067] This software architecture is used for the model data of each battery in the battery pack array. The data model data of each battery module will be input to the battery data analysis and processing module of the BOS-CORE layer. The battery data analysis and processing module will summarize and calculate the current charge and discharge power based on each battery model data and the real-time data of each battery module, and send the control command 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 data to the corresponding peripheral device.

[0068] Data processing process of 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 the memory in a key-value format.

[0070] (2) The battery data analysis and processing module collects information such as voltage, current, and temperature of each battery module and single 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 compares the collected battery module pack voltage data with the battery module charging cut-off voltage configuration stored in the memory in step (1). If the voltage exceeds the configured value, the battery module is marked as fully charged.

[0072] (4) During the discharge process, the battery data analysis and processing module compares the collected battery module pack voltage data with the battery module discharge cut-off voltage configuration stored in the memory in step (1). If the voltage is lower than the configured value, the battery module is marked as being discharged.

[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 the memory in step (1). If the voltage is lower than the configured value, the battery module is marked as being in a faulty state.

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

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

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

[0077] (9) During the charging process, if the battery data analysis and processing module determines that any battery module is fully charged, the battery cluster is considered to be fully charged. During the discharging process, if any battery module is discharged, the battery cluster is considered to be discharged. If any battery module is faulty during the charging and discharging process, the battery cluster is considered 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 current charging and discharging power value of the system is obtained by multiplying the voltage and current.

[0079] The battery management strategy of this software architecture is programmable. It is not a fixed logic that cannot be modified by code. In order to adapt to different project requirements, it is convenient to dynamically edit and generate battery management strategy steps. The results output by the battery data analysis and processing module are used as the input of the battery management strategy operation module to provide a basis for strategy operation. The battery management strategy is modified because different project requirements are different. For example, if there are no special requirements for the project, the system will automatically adjust to reduce power and protect the battery at the end of charging and discharging. Some projects require that the battery management system cannot reduce power at any time to ensure that power output is prioritized. In this way, at the end of battery charging and discharging, it cannot automatically reduce power.

[0080] First, logic programming uses XML format description files to describe the steps. XML files are a markup language used to describe data, which is highly readable, easy to parse and expand. Each command consists of a command word + command parameters.

[0081] This software architecture divides the battery management strategy into the following business scenarios, including startup process, shutdown process, charging and discharging process, battery maintenance process, standby process and other business processes. Each process corresponds to an editable XML process description file. The description file contains the command list and parameters in the corresponding process.

[0082] In response to different project requirements, the different scenario BMS or energy storage inverter PCS used in the project can quickly generate the steps of each business process of the corresponding project through logical programming. It has strong compatibility and scalability, can greatly save labor costs and time, and reduce maintenance costs.

[0083] Among them, the BOS-API layer mainly encapsulates the external interfaces provided by the BOS-CORE layer, BOS-HDL layer and BOS-HIL layer, publishes the telemetry and telesignaling data to each app through the MQTT protocol, and subscribes to the control commands and data published by each app.

[0084] The BOS-APP layer mainly implements the human-computer interaction interface, displays the current status and battery data of the battery cluster, and provides a manually operated UI interaction interface. The current status includes: power on, power off, charging, discharging, standby, etc.; battery data includes: the maximum voltage and minimum voltage of the battery module pack, and the specific topological position of the battery module in the battery cluster. The maximum and minimum voltage of the battery cell, and the specific topological position of the battery cell in the battery cluster. The maximum and minimum temperature of the battery module and its position, etc. The manually operated UI interaction interface includes the following operations: power on, power off, standby, setting the charge and discharge power, viewing the battery module voltage and temperature of the battery cluster, viewing the battery cell voltage and temperature of the battery cluster, and viewing the historical charge and discharge power curve.

[0085] The software architecture of the present invention is organized in the form of steps, as described below:

[0086] Step 1: Layer the software, divide each layer into different modules according to function, define the external API interface of each layer, and reduce the coupling between different layers.

[0087] Step 2: Define the battery data analysis and processing module, and define the battery attribute information in XML using XML file configuration. The 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 include: defining the tag structure of each battery module in the XML file, defining the tag name as <packn> …< / packn> Where n represents the battery module serial number. <pack>The battery attribute tag is defined inside the tag, and the attributes include the following:

[0089] 1. Battery module charging cut-off voltage <packfullvol>.

[0090] 2. Battery module discharge cut-off voltage <packlowvol>.

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

[0092] Each battery module <pack>The label contains single attribute labels, which are familiar as follows:

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

[0094] 2. Battery cell charging cut-off voltage <batfullvol>.

[0095] 3. Battery cell discharge cut-off voltage <batlowvol>.

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

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

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

[0099] 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 the memory in a key-value format. 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. The battery data analysis and processing module compares the collected battery information with the key-value data stored in the memory to determine the battery's fault status, as well as the full and empty status.

[0100] Step 3: Define the battery management strategy operation function module, define each battery control sub-command by XML file configuration, and dynamically define the battery management strategy in a programmable way. Among them, the battery management strategy is decomposed into sub-commands one by one. Different types of sub-commands with different permutations and combinations will constitute a specific battery management strategy. The sub-commands mainly include the following: 1. Network card power on; 2. Adapter power on; 3. Energy storage inverter power on; 4. Network card power off; 5. Adapter power off; 6. Energy storage inverter power off; 7. Set the current operating charge and discharge power; 8. Get whether the battery cluster is full; 9. Get whether the battery cluster is empty; 10. Get whether there are faulty batteries in the battery cluster.

[0101] Step 4: The BOS-APP layer application calls the functional module interfaces of each layer below it to implement the final business logic application.

[0102] Taking issuing a charging instruction to a battery management system as an example, the working process of the present invention is described as follows:

[0103] Human-computer interaction layer: The operator clicks the charging button on the interface and enters the charging power value, such as 100kw. Click the OK button. The power setting instruction of the interface encapsulation layer is called.

[0104] Interface encapsulation layer: The power setting instruction of the interface encapsulation layer. Call the power setting instruction of the logic processing layer.

[0105] Logical processing layer: The power setting instruction enters the logical processing layer, and further logical processing judgment is performed. For example, according to the current battery cluster situation, whether there is a faulty battery, and the current SOC state, it is judged whether 100kw charging power is allowed or whether the power needs to be reduced. The final power setting instruction is passed to the device access layer.

[0106] Device access layer: After being judged by the logic processing layer, the power setting instruction reaches the device access layer. At the device access layer, according to the current system configuration, the specified model of energy storage inverter will be selected, and the hardware interface and communication protocol used by the energy storage inverter will be selected. The interface of the hardware interface layer is called to send the command to the energy storage inverter.

[0107] Hardware interface layer: The power setting instructions of the hardware interface layer will send the instructions to the specified hardware device, detect the response confirmation of the device, and feedback the setting results.

[0108] This application has the following advantages:

[0109] The software architecture provided in this application can run on different embedded operating systems, including but not limited to Linux systems, VxWorks systems, and various RTOS (UCOS, FreeRTOS, etc.). Supports different types of batteries, including but not limited to lithium-ion batteries, sodium-ion batteries, etc. Supports mixed use of different types of batteries, and can effectively manage mixed battery systems. Supports input of battery model data for each battery module in the system, supports expansion of different types of batteries, and supports the existence of different types of batteries in the system. For the battery management strategy, it is designed as a logic programming method. According to different project requirements, the battery management strategy process can be dynamically edited without re-modifying the code.

[0110] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, 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 article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and core ideas of this application. At the same time, for those skilled in the art, according to the ideas of this application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.< / battemplow> < / battemphigh> < / batfaultvol> < / batlowvol> < / batfullvol> < / batnum> < / pack> < / packfaultvol> < / packlowvol> < / packfullvol> < / pack>

Claims

1. A battery management embedded software architecture, characterized in that: The battery management embedded software architecture 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; The human-computer interaction layer is used to receive operation instructions and display the current status and battery data of the battery cluster; 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 results to the human-computer interaction layer, and receive the operation instructions; 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 the battery management strategy to the battery model, and generate control instructions according to the battery management strategy, determine the current state and battery data of the battery cluster, and send them to the human-computer interaction layer through the interface encapsulation layer; the control instructions include obtaining data of the preset hardware interface and sending corresponding preset data to the preset hardware interface; the battery model describes the parameters of the battery through a description file in XML format; the parameters include the battery's charge and discharge cut-off voltage, the battery's temperature and the corresponding relationship between the maximum charge and discharge power, and the battery's charge and discharge curve data; 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 of different manufacturers, and access the corresponding device operation interface according to the control instruction to obtain the parameters of the preset hardware interface, and generate a call instruction; The hardware interface layer is connected to the device access layer; the hardware interface layer is used to perform secondary packaging on the preset hardware interface and send corresponding preset data to the preset hardware interface according to the calling instruction.

2. The battery management embedded software architecture according to claim 1, characterized in that: The preset hardware interfaces include RS485, CAN, SPI, IIC and Ethernet interfaces.

3. The battery management embedded software architecture according to claim 1, characterized in that: The battery management strategy is programmable.

4. The battery management embedded software architecture according to claim 1, characterized in that: The battery management strategy describes the execution steps through a description file in XML format.

5. The battery management embedded software architecture according to claim 1, characterized in that: The battery management strategy includes a startup process, a shutdown process, a charge and discharge process, a battery maintenance process and a standby process.

6. The battery management embedded software architecture according to claim 1, characterized in that: The logic processing layer also compares the battery data with a preset battery threshold, and determines the current state of the battery cluster according to the comparison result; the current state includes a fault state, a full state, and an empty state.

7. The battery management embedded software architecture according to claim 6, characterized in that: Obtain an XML configuration file; parse the XML configuration file to obtain battery attribute data, and store the battery attribute data in a key-value manner in a memory.

8. The battery management embedded software architecture according to claim 1, characterized in that: During the charging process, when the collected voltage data of the battery module in the battery cluster exceeds the battery module charging cut-off voltage configuration value stored in the memory, the battery module is marked as being in a fully charged state; During the discharge process, when the collected voltage data of the battery module in the battery cluster is lower than the battery module discharge cut-off voltage configuration value stored in the memory, the battery module is marked as being in a discharge state; During the charging and discharging process, when the collected voltage data of the battery module in the battery cluster is lower than the battery module fault voltage configuration value stored in the memory, the battery module is marked as being in a fault state; During the charging process, when the collected voltage data of each electric cell in the battery module of the battery cluster exceeds the single cell charging cut-off voltage configuration value stored in the memory, the battery module is marked as being in a full state; During the discharge process, when the collected voltage data of each electric cell in the battery module of the battery cluster is lower than the single cell discharge cut-off voltage configuration value stored in the memory, the battery module is marked as being in a discharge state; During the charging and discharging process, when the collected voltage data of each electric cell in the battery module of the battery cluster is lower than the single cell fault voltage configuration value stored in the memory, the battery module is marked as being in a fault state; During the charging process, when any battery module in the battery cluster is fully charged, the battery cluster is marked as fully charged; During the discharge 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; During the charging and discharging process, when any battery module in the battery cluster is in a fault state, the battery cluster is marked as being in a fault state.

Citation Information

Patent Citations

  • Distributed modular vehicle-mounted battery management system

    CN110758174A

  • Universal architecture applied to embedded system

    CN112328313A

  • Power domain controller and system, electric vehicle and control method

    CN114834371A

  • Safety management system and safety management method of energy storage battery

    CN117276722A

  • Embedded energy storage battery thermal runaway early warning thermoelectric sensing device

    CN118017058A