Fault handling method, device, processor and vehicle of battery management system

Abstract

The present invention discloses a fault handling method, device, processor and vehicle for a battery management system. The method comprises: in response to a fault in the battery management system, obtaining a fault sign corresponding to the fault, wherein the fault sign is used to characterize the type of the fault; detecting the state information of the relay of the battery management system, wherein the state information is used to characterize the open state or closed state of the relay; and processing the fault information of the battery management system based on the fault sign and the state information. The present invention solves the technical problem that the battery management system has poor risk resistance.

Description

Technical Field

[0001] The present invention relates to the field of vehicles, and in particular to a fault handling method, device, processor and vehicle of a battery management system. Background Art

[0002] At present, the battery management system may have faults when running tasks, such as abnormal running memory data, abnormal flash memory data and multiple activation of tasks. These faults will cause the loss of nodes of the battery management system of the whole vehicle and abnormal battery management system. In severe cases, it may cause electrical and thermal runaway of the whole vehicle.

[0003] In the related art, the solution to the fault problem is to immediately re-execute the interrupted task. However, this will cause the relay to be in a closed state when the fault occurs, which may easily cause the relay to stick and generate electric sparks. Therefore, there is still a technical problem of poor risk resistance of the battery management system.

[0004] With respect to the technical problem of poor risk resistance of the battery management system existing in the above-mentioned related technologies, no effective solution has been proposed so far. Summary of the invention

[0005] Embodiments of the present invention provide a fault handling method, device, processor and vehicle for a battery management system, so as to at least solve the technical problem that the battery management system has poor risk resistance.

[0006] According to one aspect of an embodiment of the present invention, a fault processing method for a battery management system is provided. The method may include: in response to a fault in the battery management system, obtaining a fault flag corresponding to the fault, wherein the fault flag is used to characterize the type of the fault; detecting state information of a relay of the battery management system, wherein the state information is used to characterize the open state or closed state of the relay; and processing the fault information of the battery management system based on the fault flag and the state information.

[0007] Optionally, the fault information is processed based on the fault flag and the status information, including: determining the category of the fault information based on the fault flag; and arranging and combining different categories with the status information to process the fault information of the categories corresponding to different status information.

[0008] Optionally, based on the fault flag, determining the category of fault information includes: based on the fault flag, classifying the fault information to obtain first category faults, second category faults, third category faults and fourth category faults, wherein the first category fault is running memory data abnormality, the second category fault is flash memory data abnormality, the third category fault is multiple activation class, and the fourth category fault includes stack overflow class and unknown interrupt class.

[0009] Optionally, the fault information is processed based on the fault flag and status information, including: in response to the fault information being a first category fault or a fourth category fault and the relay being in a disconnected state, initializing the running memory data and re-running the task; in response to the fault information being a first category fault and a fourth category fault and the relay being in a closed state, after a preset time period, initializing the running memory data, disconnecting the relay, and re-running the task.

[0010] Optionally, based on the fault flag and status information, the fault information is processed, including: in response to the fault information being a second category fault, determining the failed flash memory data; extracting the corresponding correct flash memory data from the backup; replacing the failed flash memory data with the correct flash memory data, and re-running the task.

[0011] Optionally, the fault information is processed based on the fault flag and status information, including: in response to the fault information being a third category fault and the relay being in an open state, re-running the task; in response to the fault being a third category fault and the relay being in a closed state, continuing to execute the interrupted task.

[0012] Optionally, detecting status information of a relay of a battery management system includes: reading a high-side drive voltage of the relay; and in response to the high-side drive voltage being greater than a voltage threshold, determining that the relay state represented by the status information is a closed state.

[0013] According to another aspect of an embodiment of the present invention, a fault processing device for a battery management system is also provided. The device may include: an acquisition unit, for acquiring a fault flag corresponding to the fault in response to a fault in the battery management system, wherein the fault flag is used to characterize the type of the fault; a detection unit, for detecting state information of a relay of the battery management system, wherein the state information is used to characterize the open state or closed state of the relay; and a processing unit, for processing the fault information of the battery management system based on the fault flag and the state information.

[0014] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is also provided. The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the fault handling method of the battery management system of the embodiment of the present invention.

[0015] According to another aspect of an embodiment of the present invention, a processor is further provided, wherein the processor is used to run a program, wherein when the program is run, the fault handling method of the battery management system of the embodiment of the present invention is executed.

[0016] According to another aspect of an embodiment of the present invention, a vehicle is further provided, wherein the vehicle is used to execute the fault handling method of the battery management system according to an embodiment of the present invention.

[0017] In an embodiment of the present invention, in response to a fault in a battery management system, a fault flag corresponding to the fault is obtained, wherein the fault flag is used to characterize the type of fault; the status information of the relay of the battery management system is detected, wherein the status information is used to characterize the disconnected state or closed state of the relay; based on the fault flag and the status information, the fault information of the battery management system is processed. That is to say, in the process of running a task, when a fault occurs in the battery management system of an embodiment of the present invention, the fault flag corresponding to the current fault can be determined, and the current relay can be detected to be in an open state or a closed state. The fault information of the fault can be processed by analyzing the situations corresponding to different fault flags and different status information, thereby achieving the purpose of resolving the faults occurring in the battery management system under different fault situations, thereby solving the technical problem of the poor risk resistance of the battery management system, and achieving the technical effect of improving the risk resistance of the battery management system. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0019] Figure 1 is a flow chart of a fault handling method of a battery management system according to an embodiment of the present invention;

[0020] Figure 2 is a flow chart of a method for handling unexpected faults according to an embodiment of the present invention;

[0021] Figure 3 is a schematic diagram of a fault handling device of a battery management system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0024] Example 1

[0025] According to an embodiment of the present invention, an embodiment of a fault handling method for a battery management system is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0026] Figure 1 is a flow chart of a fault handling method of a battery management system according to an embodiment of the present invention. Figure 1 As shown, the method may include the following steps:

[0027] Step S102, in response to a fault occurring in the battery management system, a fault flag corresponding to the fault is obtained, wherein the fault flag is used to characterize the type of the fault.

[0028] In the technical solution provided in the above step S102 of the present invention, when a fault occurs in the battery management system, the type of the fault can be determined, and a fault flag corresponding to the type of the fault can be obtained, wherein the fault can include abnormal data of the running memory (Random-Access Memory, referred to as RAM), abnormal data of the flash memory (Flash), multiple activation type and access to illegal address (unknown interrupt type) and other faults. The fault flag can be used to characterize the type of fault, and can be the number of multiple faults. It should be noted that this is only for example, and does not limit the type of fault.

[0029] Optionally, the fault type can be numbered in binary, octal, decimal or hexadecimal, and the fault flags of all faults can be determined. When the battery management system is running a task, if the battery management system fails, the currently running task can be interrupted to obtain the type of fault and determine the fault flag corresponding to the type of fault. It should be noted that this is only an example and does not impose specific restrictions on the form of expression and numbering method of the fault flag.

[0030] For example, a microcontroller unit (MCU) can be deployed in the battery management system, such as a fault register. When a fault occurs in the battery management system, the running task can be interrupted immediately, the fault flag of the fault stored in the fault register can be read, and the fault flag stored at the time of the last fault can be updated and replaced with the fault flag of this time.

[0031] Step S104, detecting state information of a relay of the battery management system, wherein the state information is used to represent an open state or a closed state of the relay.

[0032] In the technical solution provided in the above step S104 of the present invention, after obtaining the fault sign corresponding to the fault in the battery management system at this time, it is possible to detect whether the relay of the battery management system is in a disconnected state to determine the status information of the relay, wherein the status information can be used to characterize whether the relay is in an open state or in a closed state.

[0033] For example, the magnitude of the high-side driving voltage of the relay can be detected to determine whether the high-side driving voltage exceeds the voltage threshold. If it exceeds, it can be said that the relay is in a closed state; if it does not exceed, it can be said that the relay is in an open state. It should be noted that this is only an example, and the method and process for determining the state information of the relay are not specifically limited.

[0034] Step S106: Processing the fault information of the battery management system based on the fault flag and status information.

[0035] In the technical solution of the above-mentioned step S106 of the present invention, different situations can be determined based on different fault signs and different status information, and the fault information in the battery management system under different situations can be processed, wherein the fault information can be fault data, which can include running memory data and flash memory data where the fault occurs, etc.

[0036] Optionally, different fault signs and different status information are arranged and combined. For example, the abnormality of running memory data can be divided into two states: the relay is disconnected and closed. The data that fails in different situations can be processed. For example, the faulty data can be initialized or replaced with correct data, etc., so as to solve the fault problem of the battery management system. The processing method here is only for illustration and is not specifically limited.

[0037] For example, when a battery management system fails while running a task, the currently running task can be interrupted. If the current fault is abnormal running memory data, the fault register obtains the fault flag corresponding to the abnormal running memory data, and can detect the status information of the relay under the current fault condition. If the relay is in the disconnected state, the running memory data that has failed at this time can be initialized, and the interrupted task can be re-executed, thereby solving the fault problem of the battery management system.

[0038] In an embodiment of the present invention, when a fault occurs in the battery management system, the fault sign is detected and the status information of the relay is determined. A variety of fault conditions can be determined through different fault signs and different status information, and different processing processes and methods are performed for different fault conditions, thereby solving the technical problem of the poor risk resistance of the battery management system and improving the risk resistance of the battery management system.

[0039] In the above steps S102 to S106 of the present application, in response to a fault in the battery management system, a fault flag corresponding to the fault is obtained, wherein the fault flag is used to characterize the type of fault; the status information of the relay of the battery management system is detected, wherein the status information is used to characterize the disconnected state or closed state of the relay; based on the fault flag and the status information, the fault information of the battery management system is processed. That is to say, when the battery management system of the embodiment of the present invention fails during the operation of the task, the fault flag corresponding to the current fault can be determined, and the current relay can be detected to be in the disconnected state or closed state. The fault information of the fault can be processed by analyzing the situations corresponding to different fault flags and different status information, thereby solving the faults of the battery management system under different fault situations, thereby solving the technical problem of the poor risk resistance of the battery management system, and achieving the technical effect of improving the risk resistance of the battery management system.

[0040] The above method of this embodiment is further introduced below.

[0041] As an optional implementation method, step S106 processes the fault information based on the fault flag and status information, including: determining the category of the fault information based on the fault flag; and arranging and combining different categories and status information to process fault information of categories corresponding to different status information.

[0042] In this embodiment, fault information can be classified based on fault signs, and different types of fault and status information can be arranged and combined to obtain different fault conditions. Different status information of the same type of fault information can process the fault information differently.

[0043] For example, when the fault in the battery management system is of the stack overflow type, the fault can be divided into two states: a relay disconnected state and a relay closed state, and different processing methods can be adopted for the fault information in different states.

[0044] As an optional implementation method, step S106, based on the fault flag, determines the category of fault information, including: based on the fault flag, classifies the fault information to obtain first category faults, second category faults, third category faults and fourth category faults, wherein the first category fault is running memory data abnormality, the second category fault is flash memory data abnormality, the third category fault is multiple activation class, and the fourth category fault includes stack overflow class and unknown interrupt class.

[0045] In this embodiment, fault information can be classified based on fault flags and can be divided into first category faults, second category faults, third category faults and fourth category faults, wherein first category faults may include running memory data abnormalities, second category faults may include flash memory data abnormalities, third category faults may include multiple activation categories, fourth category faults may include stack overflow categories and unknown interrupt categories, etc.

[0046] Optionally, since there are a large number of faults in the battery management system, some of the faults may have the same solution. Therefore, in an embodiment of the present invention, some faults with the same solution can be classified into one category, thereby improving the technical effect of the efficiency of solving the battery management system faults.

[0047] As an optional implementation method, step S106 processes the fault information based on the fault flag and status information, including: in response to the fault information being a first category fault or a fourth category fault and the relay being in a disconnected state, initializing the running memory data and re-running the task; in response to the fault information being a first category fault and a fourth category fault and the relay being in a closed state, after a preset time period, initializing the running memory data, disconnecting the relay, and re-running the task.

[0048] In this embodiment, when a fault occurs in the battery management system, the currently running task can be interrupted and the fault sign of the fault can be determined. When the fault information is a first category fault or a fourth category fault, the status information of the relay in the battery management system at this time can be detected. If the status information is a disconnected state, the running memory data can be initialized and the task can be re-run; if the status information is a closed state, the running memory data can be initialized after a preset time period, the relay can be disconnected, the relay can be in a disconnected state, and the task can be re-run.

[0049] Optionally, when the fault information is a first category fault or a fourth category fault and the relay is in the disconnected state, the battery management system will quickly repair the current fault and reset the interrupted task. After the task is reset, the task can be rerun. During this process, the battery management system can set the initialization flag to "invalid" in a short time and can send an invalid value to the vehicle's controller. The controller can control the battery management system to quickly resolve the fault, thereby avoiding the fault from affecting the vehicle's overall function.

[0050] Optionally, when the fault information is a first-category fault or a fourth-category fault, and the relay is in a closed state, the battery management system can initialize the running memory after a delay of one minute, and can set the driving pin of the relay to a low level, so that the relay can be in a disconnected state, and the interrupted task can be re-run, and the current running memory data and fault flag can be stored in an electrically erasable programmable read only memory (EEPROM), which is convenient for troubleshooting and solving faults. It should be noted that this is only an example, and there is no specific restriction on the preset time period.

[0051] In an embodiment of the present invention, when the fault information is a first category fault or a fourth category fault and the relay is in a closed state, since the battery management system can repair the fault after a delay of a preset time period and can re-run the interrupted task, the fault will continue to be reported during the delay of the preset time period, so that other controllers of the battery management system can respond, thereby cutting off the load current and preventing the battery management system from generating sparks due to excessive current after the fault is repaired and the task is reset, thereby reducing the impact on the function of the entire vehicle, thereby solving the technical problem of the poor risk resistance of the battery management system and improving the risk resistance of the battery management system.

[0052] As an optional implementation method, step S106 processes the fault information based on the fault flag and status information, including: in response to the fault information being a second category fault, determining the failed flash memory data; extracting the corresponding correct flash memory data from the backup; replacing the failed flash memory data with the correct flash memory data, and re-running the task.

[0053] In this embodiment, when a battery management system fails, the currently running task can be interrupted and the sign of the fault can be determined. When the fault information is a second category fault, the failed flash memory data can be determined, and the correct flash memory data corresponding to the failed flash memory data can be determined from the backup, the failed flash memory data can be replaced with the correct flash memory data, and the interrupted task can be rerun.

[0054] Optionally, when the fault information is a second category fault, the specific area of ​​the flash memory data where the fault occurs can be determined, the flash memory data area where the fault occurs can be erased, the corresponding flash memory data can be read from the flash memory data backup, and the interrupted task can be re-run. During this process, the battery management system can set the initialization flag to "invalid" in a short period of time, and can send an invalid value to the vehicle's controller. The controller can control the battery management system to quickly resolve the fault, thereby avoiding the fault from affecting the vehicle's overall function, and storing the faulty flash memory data and the fault flag of the flash memory data abnormality in a live erasable programmable read-only memory, which is convenient for troubleshooting and resolving the fault.

[0055] As an optional implementation method, step S106 processes the fault information based on the fault flag and status information, including: in response to the fault information being a third category fault and the relay being in an open state, re-running the task; in response to the fault information being a third category fault and the relay being in a closed state, continuing to execute the interrupted task.

[0056] In this embodiment, when a fault occurs in the battery management system, the currently running task can be interrupted and the fault sign of the fault can be determined. If the current fault information is a third category fault, the status information of the relay in the battery management system at this time can be detected. If the status information is a disconnected state, the interrupted task can be re-run; if the status information is a closed state, the interrupted task can continue to be executed.

[0057] Optionally, when the fault information is a third category fault and the relay is in the disconnected state, the interrupted task can be re-executed. During this process, the battery management system can set the initialization flag to "invalid" in a short period of time and can send an invalid value to the vehicle's controller. The controller can control the battery management system to quickly resolve the fault, thereby avoiding the fault from affecting the vehicle's overall function. The fault flags of multiple activation types can be stored in a powered erasable programmable read-only memory to facilitate fault detection and resolution.

[0058] As an optional implementation method, step S104, detecting the status information of the relay of the battery management system, includes: reading the high-side drive voltage of the relay; in response to the high-side drive voltage being greater than the voltage threshold, determining that the relay state represented by the status information is a closed state.

[0059] In this embodiment, the high-side drive voltage on the relay can be read, and the relationship between the high-side drive voltage and the voltage threshold can be determined. If the high-side drive voltage is greater than the voltage threshold, the state information of the relay can be determined to be a closed state; if the high-side drive voltage is less than or equal to the voltage threshold, the state information of the relay can be determined to be a disconnected state, wherein the voltage threshold can be a preset value or a self-set value. This is only for example, and no specific limitation is imposed on the counting threshold.

[0060] In an embodiment of the present invention, in response to a fault in a battery management system, a fault flag corresponding to the fault is obtained, wherein the fault flag is used to characterize the type of fault; the status information of the relay of the battery management system is detected, wherein the status information is used to characterize the disconnected state or closed state of the relay; based on the fault flag and the status information, the fault information of the battery management system is processed. That is to say, in the process of running a task, when a fault occurs in the battery management system of an embodiment of the present invention, the fault flag corresponding to the current fault can be determined, and the current relay can be detected to be in an open state or a closed state. The fault information of the fault can be processed by analyzing the situations corresponding to different fault flags and different status information, thereby solving the purpose of solving the faults of the battery management system under different fault situations, thereby solving the technical problem of the poor risk resistance of the battery management system, and achieving the technical effect of improving the risk resistance of the battery management system.

[0061] Example 2

[0062] The technical solution of the embodiment of the present invention is illustrated below in conjunction with preferred implementation modes.

[0063] At present, common faults in battery management systems include: multiple activation of tasks, stack overflow, access to illegal addresses, flash data anomalies, and running memory anomalies. These faults are usually caused by fluctuations in the external power supply voltage of the battery management system, increased signal load of the vehicle, aging of the chip, etc., and are difficult to find during the software development phase. Such faults will cause the loss of battery management system nodes, abnormal reset of the battery management system, and in severe cases, the whole vehicle will heat up and lose control. How to quickly and accurately solve these faults is very important.

[0064] In a related technology, a method and system for handling faults of equipment operation monitoring software are proposed. By monitoring the underlying status information of the equipment operation monitoring software, rapid diagnosis and handling of software faults are achieved. By distinguishing the types of software faults, different fault handling methods such as reconfiguration, underlying vulnerability repair, and temporary emergency use are adopted for different fault types, thereby achieving rapid handling of faults of equipment operation monitoring software. The method and system for handling faults of equipment operation monitoring software in the present invention utilizes real-time classification and degree-based repair to shorten the repair time, reduce the repair cost, and improve the overall efficiency of software repair.

[0065] In another related technology, a fault diagnosis and processing method, device and vehicle for a battery management system are proposed. The method includes: detecting the fault information of the battery system; determining the fault level according to the fault information of the battery system; when it is a level 1 fault, controlling the whole vehicle system to give a light alarm; when it is a level 2 fault, controlling the whole vehicle system to enter a power-limited operation mode or a slope mode, and giving a light alarm; when it is a level 3 fault, after a delay, cutting off the battery high-voltage power supply circuit to protect the battery, and giving a light alarm; when it is a level 4 fault, controlling the whole vehicle system to send an audible and visual alarm message to remind the driver to evacuate quickly, and sending the level 4 fault status to the whole vehicle main network. Through the fault diagnosis and processing method of the battery management system, it is possible to classify the faults according to their severity and degree of harm, and formulate reasonable fault handling methods according to the classified fault levels, so as to achieve reasonable and efficient handling of the faults.

[0066] However, none of the above problems solve the technical problem of the poor risk resistance of the battery management system.

[0067] To solve the above problems, an embodiment of the present invention proposes a method for handling unexpected faults in battery management system software, the method comprising: during the operation of the battery management system software, detecting whether there is an unexpected fault, and if so, interrupting the running task; entering the unexpected fault handling function, reading the fault flag in the fault register, evaluating the impact of the fault on the battery management system, and classifying the fault; reading the current battery management relay closing state; according to the fault classification and the relay closing state, the software performs separate processing, thereby achieving the purpose of solving the faults occurring in the battery management system under different fault conditions, thereby solving the technical problem of the poor risk resistance of the battery management system and achieving the technical effect of improving the risk resistance of the battery management system.

[0068] The embodiments of the present invention are further described below.

[0069] Figure 2 is a flow chart of a method for handling unexpected faults according to an embodiment of the invention. Figure 2 As shown, the method may include the following steps:

[0070] Step S201, reading the fault flag in the fault register.

[0071] In the technical solution provided in the above step S201 of the present invention, when a battery management failure occurs, the currently running task can be interrupted, and the fault flag of the fault can be determined, wherein the fault may include abnormal running memory data, abnormal flash memory data, multiple activations, and access to illegal addresses (unknown interruption type) and other faults. The fault flag can be used to characterize the type of fault, and can be the number of multiple faults. It should be noted that this is only for example, and does not limit the type of fault.

[0072] Optionally, the fault types can be labeled by binary, octal or decimal system, and the fault flags of all faults can be determined. It should be noted that this is only an example and does not specifically limit the method for determining the fault flag and the form of expression.

[0073] Step S202, reading the status information of the relay.

[0074] In the technical solution provided in the above step S202 of the present invention, after obtaining the fault flag corresponding to the fault occurring in the battery management system at this time, the status information of the relay in the battery management system at this time can be read, wherein the status information can be used to characterize whether the relay is in an open state or a closed state.

[0075] Optionally, by reading the high-side drive voltage on the relay and determining the magnitude relationship between the high-side drive voltage and the voltage threshold, if the high-side drive voltage is greater than the voltage threshold, it can be determined that the state information of the relay is in a closed state; if the high-side drive voltage is less than or equal to the voltage threshold, it can be determined that the state information of the relay is in a disconnected state, wherein the voltage threshold can be a preset value or a self-set value. This is only an example and no specific restriction is imposed on the counting threshold.

[0076] Step S203, running memory data is abnormal.

[0077] In the technical solution provided in the above step S203 of the present invention, when a fault occurs in the battery management system, a fault sign of the fault can be determined. If it is determined that the current fault is abnormal running memory data, step S204 can be further executed.

[0078] Step S204: status information of the relay.

[0079] In the technical solution provided in the above step S204 of the present invention, when the fault of the battery management system is abnormal running memory data, the state information of the relay in this case can be determined. If the relay is in a disconnected state, step S207 can be executed; if the relay is in a closed state, step S205 can be executed.

[0080] Step S205, delay for one minute and initialize the running memory data.

[0081] In the technical solution provided by the above step S205 of the present invention, when the running memory data of the battery management system is abnormal and the relay is in a closed state, it can be delayed for one minute, and then the running memory data is initialized, and step S206 can be executed.

[0082] In the embodiment of the present invention, when certain faults occur in the battery management system, the fault can be repaired after a period of delay. During the delay period, the fault will continue to be reported, which is convenient for other controllers of the battery management system to respond, thereby cutting off the load current and preventing the battery management system from generating sparks due to excessive current after the fault is repaired and the task is reset, thereby reducing the impact on the function of the entire vehicle, thereby solving the technical problem of the poor risk resistance of the battery management system and improving the risk resistance of the battery management system.

[0083] Step S206, the relay is safely disconnected, and the operation memory data and / or fault flag are stored.

[0084] In the technical solution provided in the above step S206 of the present invention, when the running memory data of the battery management system is abnormal and the relay is in a closed state, the relay can be safely disconnected after a delay of one minute, and the running memory data and the fault flag can be stored, and step S207 can be executed.

[0085] Optionally, setting the driving pin of the relay to a low level can disconnect the relay safely, and can store the current running memory data and fault flag in a powered erasable programmable read-only memory, so as to facilitate troubleshooting and solving the fault.

[0086] Step S207, software reset.

[0087] In the technical solution provided in the above step S207 of the present invention, the interrupted task can be reset and re-run.

[0088] Step S208: the flash memory data is abnormal.

[0089] In the technical solution provided in the above step S208 of the present invention, when a fault occurs in the battery management system, a fault sign of the fault can be determined. If it is determined that the current fault is a flash memory data abnormality, step S209 can be further executed.

[0090] Step S209, erasing the failed flash memory data area.

[0091] In the technical solution provided in the above step S209 of the present invention, when the fault of the battery management system is abnormal flash memory data, the specific area of ​​the flash memory data where the fault occurs can be determined, and the faulty flash memory data area can be erased.

[0092] Step S210, reading the flash memory data in the backup.

[0093] In the technical solution provided in the above step S210 of the present invention, the correct flash memory data corresponding to the failed flash memory data can be extracted from the flash memory data backup, and step S206 can be executed to store the flash memory data and the fault flag at this time, and the interrupted task can be re-run.

[0094] Step S211, the task activates the class multiple times.

[0095] In the technical solution provided in the above step S211 of the present invention, when a fault occurs in the battery management system, a fault sign of the fault can be determined. If it is determined that the current fault is a task multiple activation type, step S209 can be further executed.

[0096] Step S212, status information of the relay.

[0097] In the technical solution provided in the above step S212 of the present invention, when the fault of the battery management system is abnormal running memory data, the status information of the relay in this case can be determined. If the relay is in a disconnected state, step S206 can be executed; if the relay is in a closed state, step S213 can be executed.

[0098] Step S213, continue to execute the interrupted task.

[0099] In the technical solution provided in the above step S213 of the present invention, when the fault is of the task multiple activation type and the relay is in a closed state, the interrupted task can be immediately continued to be executed.

[0100] Optionally, when the fault is of the task multiple activation type and the relay is in the disconnected state, the fault flag can be stored in the electrically erasable programmable read-only memory and the task can be restarted.

[0101] Step S214, other faults.

[0102] In the technical solution provided in the above step S214 of the present invention, when a fault occurs in the battery management system, the fault sign of the fault can be determined. If it is determined that the current fault is not any of the above four faults, it can be determined that the fault is other faults, and step S215 can be further executed.

[0103] Step S215, status information of the relay.

[0104] In the technical solution provided in the above step S215 of the present invention, when the fault of the battery management system is other faults, the status information of the relay in this case can be determined. If the relay is in a disconnected state, step S206 can be executed; if the relay is in a closed state, step S216 can be executed, wherein other faults can include at least stack overflow and unknown interrupt types, which are only used for illustration here without specific limitation.

[0105] Step S216, delay for one minute, and the relay is safely disconnected.

[0106] In the technical solution provided in the above step S216 of the present invention, when other faults occur in the battery management system and the relay is in a closed state, a delay of one minute can be made and then the relay drive pin can be set to a low level, so that the relay can be safely disconnected.

[0107] Optionally, when other faults occur in the battery management system and the relay is in the disconnected state, the fault flags of the other faults at this time can be stored in the electrically erasable programmable read-only memory, and the interrupted task can be re-executed.

[0108] When the battery management system of the embodiment of the present invention is running a task, when a fault occurs in the battery management system, the fault sign corresponding to the current fault can be determined, and it can be detected whether the current relay is in an open state or a closed state. By analyzing the situations corresponding to different fault signs and different status information, the fault information of the fault can be processed, thereby achieving the purpose of resolving the faults occurring in the battery management system under different fault situations, thereby solving the technical problem of the poor risk resistance of the battery management system and achieving the technical effect of improving the risk resistance of the battery management system.

[0109] Example 3

[0110] According to an embodiment of the present invention, a fault handling device for a battery management system is also provided. It should be noted that the fault handling device for a battery management system can be used to execute the fault handling method for a battery management system in Example 1.

[0111] Figure 3 Schematic diagram of a fault handling device of a battery management system according to an embodiment of the present invention. Figure 3 As shown, the fault handling device 300 of the battery management system may include: an acquisition unit 302 , a detection unit 304 and a processing unit 306 .

[0112] The acquisition unit 302 is used to acquire a fault flag corresponding to the fault in response to a fault occurring in the battery management system, wherein the fault flag is used to characterize the type of the fault.

[0113] The detection unit 304 is used to detect the state information of the relay of the battery management system, wherein the state information is used to represent the open state or the closed state of the relay.

[0114] The processing unit 306 is used to process the fault information of the battery management system based on the fault flag and the status information.

[0115] Optionally, the processing unit 306 includes: a first determination module, used to determine the category of fault information based on the fault sign; a first processing module, used to arrange and combine different categories and state information to process fault information of categories corresponding to different state information.

[0116] Optionally, the first determination module includes: a classification submodule, which is used to classify fault information based on fault signs to obtain first category faults, second category faults, third category faults and fourth category faults, wherein the first category faults are running memory data abnormalities, the second category faults are flash memory data abnormalities, the third category faults are multiple activation categories, and the fourth category faults include stack overflow categories and unknown interrupt categories.

[0117] Optionally, the processing unit 306 includes: a second processing module, used to initialize the running memory data and re-run the task in response to the fault information being a first category fault or a fourth category fault and the relay being in a disconnected state; a third processing module, used to initialize the running memory data, disconnect the relay, and re-run the task after a preset time period in response to the fault information being a first category fault and a fourth category fault and the relay being in a closed state.

[0118] Optionally, the processing unit 306 includes: a second determination module, used to determine the failed flash memory data in response to the fault information being a second category fault; an extraction module, used to extract the corresponding correct flash memory data from the backup; and a fourth processing module, used to replace the failed flash memory data with the correct flash memory data and re-run the task.

[0119] Optionally, the processing unit 306 includes: a running module, used to re-run the task in response to the fault information being a third category fault and the relay being in an open state; and an execution module, used to continue executing the interrupted task in response to the fault being a third category fault and the relay being in a closed state.

[0120] Optionally, the detection unit 304 includes: a reading module for reading the high-side driving voltage of the relay; and a third determining module for determining that the relay state represented by the state information is a closed state in response to the high-side driving voltage being greater than a voltage threshold.

[0121] In an embodiment of the present invention, an acquisition unit responds to a fault in a battery management system to acquire a fault flag corresponding to the fault, wherein the fault flag is used to characterize the type of fault; a detection unit detects status information of a relay of the battery management system, wherein the status information is used to characterize an open state or a closed state of the relay; a processing unit processes the fault information of the battery management system based on the fault flag and the status information, thereby achieving the purpose of resolving faults occurring in the battery management system under different fault conditions, thereby solving the technical problem of poor risk resistance of the battery management system and achieving the technical effect of improving the risk resistance of the battery management system.

[0122] Example 4

[0123] According to an embodiment of the present invention, a computer-readable storage medium is further provided. The storage medium includes a stored program, wherein the program executes the fault handling method of the battery management system described in Embodiment 1.

[0124] Example 5

[0125] According to an embodiment of the present invention, a processor is further provided, which is used to run a program, wherein the fault handling method of the battery management system described in Example 1 is executed when the program is run.

[0126] Example 6

[0127] According to an embodiment of the present invention, a vehicle is further provided. The vehicle is used to execute the fault handling method of the battery management system according to the embodiment of the present invention.

[0128] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0129] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0130] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0131] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0132] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0133] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0134] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A fault handling method for a battery management system, characterized in that: include: In response to a fault occurring in the battery management system, obtaining a fault flag corresponding to the fault, wherein the fault flag is used to characterize the type of the fault; Detecting state information of a relay of the battery management system, wherein the state information is used to represent an open state or a closed state of the relay; Based on the fault flag and the status information, processing the fault information of the battery management system; The processing of the fault information based on the fault flag and the status information includes: determining the category of the fault information based on the fault flag; arranging and combining different categories with different status information to process the fault information of the category corresponding to different status information; Determining the category of the fault information based on the fault flag includes: classifying the fault information based on the fault flag to obtain a first category fault, a second category fault, a third category fault and a fourth category fault, wherein the first category fault is an abnormality in running memory data, the second category fault is an abnormality in flash memory data, the third category fault is a multiple activation category, and the fourth category fault includes a stack overflow category and an unknown interrupt category; Based on the fault flag and the status information, the fault information is processed, including: in response to the fault information being the first category fault or the fourth category fault and the relay being in a disconnected state, initializing the running memory data and re-running the task; in response to the fault information being the first category fault or the fourth category fault and the relay being in a closed state, after a preset time period, initializing the running memory data, disconnecting the relay, and re-running the task.

2. The method according to claim 1, characterized in that: Processing the fault information based on the fault flag and the state information includes: In response to the fault information being the second type of fault, determining the flash memory data where the fault occurs; Extracting the corresponding correct flash memory data from the backup; The flash memory data where the fault occurs is replaced with the correct flash memory data, and the task is re-run.

3. The method according to claim 1, characterized in that Processing the fault information based on the fault flag and the state information includes: In response to the fault information being the third category fault and the relay being in an off state, re-running the task; In response to the fault information being the third category fault and the relay being in a closed state, the interrupted task continues to be executed.

4. The method according to claim 1, characterized in that: Detecting the status information of the relay of the battery management system includes: reading the high side drive voltage of the relay; In response to the high-side drive voltage being greater than a voltage threshold, it is determined that the state of the relay represented by the state information is the closed state.

5. A fault handling device for a battery management system, characterized in that: The device comprises: an acquisition unit, configured to acquire a fault flag corresponding to a fault in response to a fault occurring in the battery management system, wherein the fault flag is used to characterize a type of the fault; A detection unit, used to detect state information of a relay of the battery management system, wherein the state information is used to represent an open state or a closed state of the relay; a processing unit, processing the fault information of the battery management system based on the fault flag and the status information; The processing unit is used to perform the following steps to process the fault information: determine the category of the fault information based on the fault flag; arrange and combine different categories with different status information to process the fault information of the category corresponding to different status information; The processing unit is used to perform the following steps to determine the category: based on the fault flag, classify the fault information to obtain a first category fault, a second category fault, a third category fault and a fourth category fault, wherein the first category fault is an abnormality in running memory data, the second category fault is an abnormality in flash memory data, the third category fault is a multiple activation category, and the fourth category fault includes a stack overflow category and an unknown interrupt category; The processing unit is used to execute the following steps to process the fault information: in response to the fault information being the first category fault or the fourth category fault and the relay being in a disconnected state, initializing the running memory data and re-running the task; in response to the fault information being the first category fault or the fourth category fault and the relay being in a closed state, after a preset time period, initializing the running memory data, disconnecting the relay, and re-running the task.

6. A processor, characterized in that: The processor is used to run a program, wherein the program executes the method according to any one of claims 1 to 4 when running.

7. A vehicle, characterized in that: Used to perform the method according to any one of claims 1 to 4.

Images