Fault analysis method and device of power battery, vehicle and medium

Abstract

The invention relates to the technical field of battery faults, in particular to a power battery fault analysis method and device, a vehicle and a medium, and the method comprises the steps: obtaining fault data of a power battery; the fault data are input into a fault analysis model, the fault analysis model outputs a fault identifier, and the fault analysis model analyzes the fault identifier corresponding to the fault data based on the fault signal type and a fault trigger condition corresponding to the fault signal type; and determining a fault reason of the power battery according to the fault identifier. Therefore, the problems that in the prior art, specific faults cannot be refined, rapid troubleshooting is not facilitated, and manual modeling is long in time consumption, prone to errors and the like are solved.

Description

Technical Field

[0001] The present application relates to the technical field of battery failure, and in particular to a method, device, vehicle and medium for analyzing failure of a power battery. Background Art

[0002] As the core component of electric vehicles, battery systems are becoming more and more diverse with the rapid development of new energy vehicles. The performance and reliability of batteries are directly related to the driving efficiency and safety of vehicles. In the existing battery system fault diagnosis and display technology, the fault level is generally evaluated based on the received fault signal, and the corresponding battery fault light is lit and the corresponding text prompt is displayed through the display device.

[0003] However, although this method can initially understand the degree of harm caused by battery system failure, it cannot provide specific and detailed fault information, which makes it difficult for non-technical personnel to conduct temporary troubleshooting. In addition, to display all battery fault information, it is necessary to add all relevant signals and build complex judgment conditions. If this process is completed manually, it will not only consume a lot of time and human resources, but also easily introduce human errors, affecting the accuracy and efficiency of diagnosis. Summary of the invention

[0004] The present application provides a power battery fault analysis method, device, vehicle and medium to solve the problems in the prior art that the specific fault cannot be refined, is not conducive to rapid troubleshooting, and manual modeling is time-consuming and prone to errors.

[0005] A first aspect of the present application provides a method for fault analysis of a power battery, comprising the following steps: acquiring fault data of the power battery; inputting the fault data into a fault analysis model, the fault analysis model outputting a fault identifier, wherein the fault analysis model analyzes the fault identifier corresponding to the fault data based on the fault signal type and the fault trigger condition corresponding to the fault signal type; and determining the cause of the power battery failure according to the fault identifier.

[0006] Optionally, the analysis process of the fault analysis model includes: identifying at least one fault signal and a fault triggering condition in the fault data; and determining a fault identifier corresponding to the fault data according to the fault signal type and the fault triggering condition of the fault signal.

[0007] Optionally, determining the fault identifier corresponding to the fault data according to the fault signal type and the fault trigger condition of the fault signal includes: obtaining a first correspondence table of the fault signal type, the fault trigger condition and the fault identifier; and querying the first correspondence table to obtain the fault identifier corresponding to the fault data using the fault signal type and the fault trigger condition as indexes.

[0008] Optionally, determining the fault cause of the power battery according to the fault identifier includes: acquiring a second correspondence table between the fault identifier and the fault cause; and querying the second correspondence table to determine the fault cause using the fault identifier as an index.

[0009] Optionally, after determining the fault cause of the power battery according to the fault identifier, the method includes: obtaining a display priority of each fault cause; and displaying at least one fault cause according to the display priority.

[0010] Optionally, displaying at least one fault cause according to a display priority includes: acquiring a display length of a display device; determining the number of fault causes that are simultaneously displayed by the display device according to a required display length of the fault cause and the display length of the display device; and displaying according to the display priority and the number of fault causes that are simultaneously displayed by the display device.

[0011] Optionally, if the required display length of the fault cause is greater than the display length of the display device, the fault cause is displayed cyclically according to the display priority.

[0012] A second aspect of the present application provides a fault analysis device for a power battery, comprising: an acquisition module for acquiring fault data of the power battery; an output module for inputting the fault data into a fault analysis model, the fault analysis model outputting a fault identifier, wherein the fault analysis model analyzes the fault identifier corresponding to the fault data based on the fault signal type and the fault trigger condition corresponding to the fault signal type; and a determination module for determining the cause of the power battery failure according to the fault identifier.

[0013] A third aspect of the present application provides a vehicle, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement a power battery fault analysis method as described in the above embodiment.

[0014] A fourth aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to implement a power battery fault analysis method as described in the above embodiment.

[0015] Therefore, this application includes the following beneficial effects:

[0016] The embodiment of the present application automatically analyzes fault data through a fault analysis model, which can quickly locate faults and greatly improve diagnostic efficiency; the fault analysis model is trained and optimized based on a large amount of fault data and signal types, and can more accurately identify the fault signal type and the corresponding trigger condition, thereby outputting an accurate fault identification and avoiding errors in human judgment; timely detection and processing of power battery faults can avoid safety accidents caused by faults. Thus, the technical problems in the prior art that it is impossible to refine specific faults, which is not conducive to rapid troubleshooting, and manual modeling is time-consuming and error-prone, etc. are solved.

[0017] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0019] Figure 1 A flowchart of a method for analyzing a power battery failure according to an embodiment of the present application;

[0020] Figure 2 A flowchart of a method for analyzing a power battery failure according to an embodiment of the present application;

[0021] Figure 3 A flowchart of fault automation coding provided according to an embodiment of the present application;

[0022] Figure 4 This is an example diagram of a fault analysis device for a power battery according to an embodiment of the present application;

[0023] Figure 5 It is a schematic diagram of the structure of a vehicle according to an embodiment of the present application. DETAILED DESCRIPTION

[0024] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0025] The following describes the power battery fault analysis method, device, vehicle and medium of the embodiment of the present application with reference to the accompanying drawings. In view of the problem that the fault cannot be refined mentioned in the above background technology, the present application provides a power battery fault analysis method, in which the fault data is automatically analyzed by a fault analysis model, and the fault can be quickly located, greatly improving the diagnostic efficiency; the fault analysis model is trained and optimized based on a large amount of fault data and signal types, and can more accurately identify the fault signal type and the corresponding trigger condition, thereby outputting an accurate fault identification, avoiding errors in human judgment; timely detection and processing of power battery faults can avoid safety accidents caused by faults. Thus, the problems of the prior art that it is impossible to refine specific faults, which is not conducive to rapid troubleshooting, and manual modeling is time-consuming and error-prone, are solved.

[0026] Specifically, Figure 1A schematic flow chart of a method for analyzing a power battery failure according to an embodiment of the present application.

[0027] like Figure 1 As shown, the power battery failure analysis method includes the following steps:

[0028] In step S101 , fault data of the power battery is obtained.

[0029] Among them, the fault data may be information generated by the power battery during operation, reflecting its abnormal working state or fault.

[0030] It can be understood that the embodiments of the present application acquire the fault data of the power battery in real time, and can continuously monitor the health status of the battery, so as to facilitate the subsequent analysis of the cause of the power battery failure.

[0031] In step S102, the fault data is input into the fault analysis model, and the fault analysis model outputs a fault identification, wherein the fault analysis model analyzes the fault identification corresponding to the fault data based on the fault signal type and the fault trigger condition corresponding to the fault signal type.

[0032] Among them, the fault analysis model can be an algorithm or program built based on technologies such as data analysis, machine learning or expert systems, which is used to parse and process the fault data of the power battery. The fault signal type refers to the specific signal pattern or characteristics generated by the power battery when a fault occurs.

[0033] It is understandable that the embodiment of the present application inputs the fault data of the power battery into the fault analysis model, and the model can accurately and quickly output the fault identification based on the fault signal type and the corresponding trigger condition, which not only improves the accuracy and efficiency of fault diagnosis, but also helps to find and handle faults in time, ensuring the safety and reliability of new energy vehicles. At the same time, this also provides users with a better user experience and reduces operating costs.

[0034] In an embodiment of the present application, the analysis process of the fault analysis model includes: identifying at least one fault signal and a fault trigger condition in the fault data; and determining a fault identifier corresponding to the fault data according to the fault signal type and the fault trigger condition of the fault signal.

[0035] It can be understood that the embodiments of the present application are based on complex algorithms and data processing technologies, and can accurately extract key fault signals from massive fault data; based on the type of fault signal and the fault trigger condition, it can automatically match the preset fault database or rule set to determine the specific fault identifier, thereby realizing the mapping from raw fault data to specific fault types, and providing clear guidance for subsequent fault processing.

[0036] In an embodiment of the present application, the fault identifier corresponding to the fault data is determined according to the fault signal type and the fault trigger condition of the fault signal, including: obtaining a first correspondence table of the fault signal type, the fault trigger condition and the fault identifier; using the fault signal type and the fault trigger condition as an index, querying the first correspondence table to obtain the fault identifier corresponding to the fault data.

[0037] The first correspondence table may be a database or a data structure, which is used to store the correspondence between the fault signal type, the fault triggering condition and the fault identifier.

[0038] It can be understood that the embodiment of the present application constructs and queries a correspondence table including fault signal type, fault trigger condition and fault identification, thereby realizing rapid and accurate diagnosis of power battery faults; by indexing and querying the first correspondence table, the detected fault signal and trigger condition can be quickly mapped to a specific fault identification, thereby significantly shortening the fault diagnosis time.

[0039] In step S103, the fault cause of the power battery is determined according to the fault identifier.

[0040] Among them, the cause of failure refers to the root cause of the power battery failure.

[0041] It can be understood that the embodiment of the present application determines the cause of the power battery failure based on the fault identification, which can guide the diagnostic technician to directly locate the specific cause of the power battery failure, reduce the blindness and uncertainty in the diagnostic process, and improve the accuracy and efficiency of the diagnosis.

[0042] In an embodiment of the present application, determining the cause of the power battery failure according to the fault identifier includes: obtaining a second correspondence table between the fault identifier and the fault cause; and querying the second correspondence table to determine the fault cause using the fault identifier as an index.

[0043] The second correspondence table may be a database or a data structure, which is used to store the correspondence between the fault identifier and the fault cause.

[0044] It can be understood that the embodiment of the present application uses an index to query the second correspondence table to quickly map the fault identifier to the corresponding fault cause, thereby reducing the need for manual intervention and shortening the time users wait for maintenance.

[0045] In an embodiment of the present application, after determining the fault cause of the power battery according to the fault identifier, the method includes: obtaining a display priority of each fault cause; and displaying at least one fault cause according to the display priority.

[0046] It is understandable that the embodiment of the present application sets the display priority of the fault cause, which can ensure that the most important or most likely fault cause is displayed first within the limited display space or time. The technician can obtain key information more quickly, narrow the scope of the fault, and improve the diagnosis efficiency.

[0047] In an embodiment of the present application, at least one fault cause is displayed according to a display priority, including: obtaining a display length of a display device; determining the number of fault causes that are simultaneously displayed by the display device according to a required display length of the fault cause and the display length of the display device; and displaying according to the display priority and the number of fault causes that are simultaneously displayed by the display device.

[0048] Among them, the display length of the display device can be the maximum length or capacity of the text, image or other content that the display device can display at one time under the current settings or resolution; the required display length of the fault cause can be the length or space required for each fault cause to be displayed on the display device.

[0049] It can be understood that the embodiment of the present application can reasonably plan the interface layout by accurately calculating the display length and the required display length, ensuring that all important fault causes can be displayed to the user without causing information overload; the display of fault causes in combination with display priority improves the efficiency and convenience of information acquisition.

[0050] In an embodiment of the present application, if the required display length of the fault cause is greater than the display length of the display device, the fault cause is displayed cyclically according to the display priority.

[0051] It is understandable that, in the embodiment of the present application, when the required display length of the fault cause exceeds the display capacity of the display device, the fault cause is displayed cyclically according to the display priority, ensuring that even when faced with longer fault cause information, the user can view the complete content of all fault causes step by step according to the re-display priority through the cyclic display mechanism, which not only ensures the integrity and orderliness of the information, but also optimizes the user experience and reduces the inconvenience caused by information truncation or paging. The user can obtain all key information in a smooth process, so as to make maintenance decisions or take corresponding measures more accurately.

[0052] According to the power battery fault analysis method proposed in the embodiment of the present application, the fault analysis model automatically analyzes the fault data, which can quickly locate the fault and greatly improve the diagnostic efficiency; the fault analysis model is trained and optimized based on a large amount of fault data and signal types, and can more accurately identify the fault signal type and the corresponding trigger condition, thereby outputting an accurate fault identification and avoiding errors in human judgment; timely detection and processing of power battery faults can avoid safety accidents caused by faults. Thus, the problems of the prior art that it is impossible to refine specific faults, which is not conducive to rapid troubleshooting, and manual modeling is time-consuming and error-prone, are solved.

[0053] The following will be combined Figure 2 The fault analysis method of power battery is specifically described as follows:

[0054] S1. Obtaining fault information of the battery system after the vehicle is powered on, wherein the fault signal is used to indicate the specific fault status of the vehicle battery system;

[0055] S2. Inputting the fault information of the battery system into the fault judgment module to obtain the current fault of the vehicle, and obtaining the current fault sequence number of the vehicle according to the fault judgment module;

[0056] It should be noted that the fault automation coding, such as Figure 3 As shown, a connection is established with a fault definition file through a matlab script, a fault definition file in a first format is called, wherein the first format is an excel format, and the matlab script is called to extract target information in the fault definition file, the target information includes the definition of the fault signal, the fault signal value judgment condition, and the fault sequence number information;

[0057] According to the first set of information in the fault signal, a judgment model of the first set of signals is first generated, and all the modules used are added from the model basic library according to the fault judgment logic application script;

[0058] The first group of modules are laid out in sequence according to the pre-set judgment logic. The layout module includes setting the module width and height, clarifying the absolute position of the first module, and the relative position and spacing between subsequent modules to ensure that the entire layout is compact and efficient. At the same time, the system is also responsible for connecting the input and output between each module to build a complete fault judgment logic link;

[0059] Modify module attributes according to target information extracted from the first format file fault file by the script, the module attributes include module name, module value, module type, and output the fault sequence number corresponding to the fault when the fault trigger condition is met;

[0060] Set the distance between the second group of input signals and the first group of modules, set the number of signal cycles, and apply the script to add each module component in sequence according to the layout and wiring logic of the first group of modules and set the module properties;

[0061] After all fault signal module groups have been added, all signal fault judgment module outputs are connected and compared to obtain the maximum value output;

[0062] S3. A trigger signal is obtained according to a certain fault display trigger condition. When the condition is triggered, the fault sequence number is periodically sent to the display device according to the sequence value from large to small. Among them, the trigger condition can be set to different conditions at different stages. In the mule car, OTS car and commercial car stage, according to the available devices at different stages, the operation of different components such as combination switches and instruments can be considered to trigger the display fault condition. Among them, the display device includes instruments, central control and mobile phone APP;

[0063] S4. According to the fault signal displayed by the display device, query the fault definition file to obtain specific fault information to facilitate subsequent fault investigation and maintenance.

[0064] In summary, the embodiment of the present application uses a script to extract the target information in the fault definition file, including the fault number, fault signal name and judgment conditions, and then generates a fault judgment model for the fault signal and its judgment trigger conditions according to the preset judgment logic. Then, after the vehicle is powered on, the battery status signals are received and input into the fault judgment model to determine whether there is a fault and output the corresponding fault number. Finally, when there is a battery-related fault, the current battery fault number is displayed on the display device through interaction with the central control or a series of operations on the vehicle that are not easy to trigger. The current specific fault information can be obtained by querying the fault definition file for processing. It can not only clearly display the specific fault status of the current vehicle without the need for any external equipment for maintenance, but also has the advantage of platformization. It only needs to generate fault judgment and coding models according to the fault definition file, which is applicable to all projects, which can greatly save development time.

[0065] Next, a fault analysis device for a power battery according to an embodiment of the present application will be described with reference to the accompanying drawings.

[0066] Figure 4 It is a block diagram of a fault analysis device for a power battery according to an embodiment of the present application.

[0067] like Figure 4 As shown, the vehicle fault analysis device 10 includes: an acquisition module 100 , an output module 200 and a determination module 300 .

[0068] Among them, the acquisition module 100 is used to obtain the fault data of the power battery; the output module 200 is used to input the fault data into the fault analysis model, and the fault analysis model outputs the fault identification, wherein the fault analysis model analyzes the fault identification corresponding to the fault data based on the fault signal type and the fault trigger condition corresponding to the fault signal type; the determination module 300 is used to determine the cause of the power battery failure according to the fault identification.

[0069] It should be noted that the above explanation of the embodiment of the power battery fault analysis method is also applicable to the power battery fault analysis device of this embodiment, and will not be repeated here.

[0070] According to the power battery fault analysis device proposed in the embodiment of the present application, the fault analysis model automatically analyzes the fault data, can quickly locate the fault, and greatly improve the diagnostic efficiency; the fault analysis model is trained and optimized based on a large amount of fault data and signal types, and can more accurately identify the fault signal type and the corresponding trigger condition, thereby outputting an accurate fault identification, avoiding errors in human judgment; timely detection and processing of power battery faults can avoid safety accidents caused by faults. Thus, the problems of the prior art that it is impossible to refine specific faults, which is not conducive to rapid troubleshooting, and manual modeling is time-consuming and error-prone, are solved.

[0071] Figure 5 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. The vehicle may include:

[0072] A memory 501 , a processor 502 , and a computer program stored in the memory 501 and executable on the processor 502 .

[0073] When the processor 502 executes the program, the power battery fault analysis method provided in the above embodiment is implemented.

[0074] Furthermore, the vehicle also includes:

[0075] The communication interface 503 is used for communication between the memory 501 and the processor 502 .

[0076] The memory 501 is used to store computer programs that can be executed on the processor 502 .

[0077] The memory 501 may include a high-speed RAM (Random Access Memory) memory, and may also include a non-volatile memory, such as at least one disk memory.

[0078] If the memory 501, the processor 502 and the communication interface 503 are implemented independently, the communication interface 503, the memory 501 and the processor 502 can be connected to each other through a bus and communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0079] Optionally, in a specific implementation, if the memory 501, the processor 502 and the communication interface 503 are integrated on a chip, the memory 501, the processor 502 and the communication interface 503 can communicate with each other through an internal interface.

[0080] The processor 502 may be a CPU (Central Processing Unit), or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0081] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-mentioned power battery fault analysis method.

[0082] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0083] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0084] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or N executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0085] It should be understood that the various parts of the present application can be implemented in hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, the steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array, a field programmable gate array, etc.

[0086] A person of ordinary skill in the art may understand that all or part of the steps carried by the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the above-mentioned program may be stored in a computer-readable storage medium, which, when executed, includes one of the steps of the method embodiment or a combination thereof.

[0087] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A method for analyzing a power battery failure, characterized in that: The following steps are involved: Obtaining power battery fault data; Inputting the fault data into a fault analysis model, the fault analysis model outputting a fault identifier, wherein the fault analysis model analyzes the fault identifier corresponding to the fault data based on a fault signal type and a fault trigger condition corresponding to the fault signal type; The cause of the power battery failure is determined according to the failure identifier.

2. The power battery failure analysis method according to claim 1, characterized in that: The analysis process of the fault analysis model includes: identifying at least one fault signal and a fault triggering condition in the fault data; A fault identifier corresponding to the fault data is determined according to the fault signal type of the fault signal and the fault triggering condition.

3. The power battery failure analysis method according to claim 2, characterized in that: The determining the fault identifier corresponding to the fault data according to the fault signal type of the fault signal and the fault triggering condition includes: Obtain a first correspondence table of fault signal types, fault triggering conditions, and fault identifiers; The first corresponding relationship table is queried using the fault signal type and the fault trigger condition as indexes to obtain a fault identifier corresponding to the fault data.

4. The power battery failure analysis method according to claim 1, characterized in that: Determining the fault cause of the power battery according to the fault identifier includes: Obtaining a second correspondence table between the fault identifier and the fault cause; The fault identifier is used as an index to query the second correspondence table to determine the cause of the fault.

5. The power battery failure analysis method according to claim 1 or 4, characterized in that: After determining the fault cause of the power battery according to the fault identifier, the method further includes: Get the display priority of each fault cause; At least one fault cause is displayed according to the display priority.

6. The power battery failure analysis method according to claim 5, characterized in that: The displaying at least one fault cause according to the display priority includes: Get the display length of the display device; Determining the number of fault causes that are displayed simultaneously by the display device according to the required display length of the fault cause and the display length of the display device; The display is performed according to the display priority and the number of fault causes displayed simultaneously by the display device.

7. The power battery failure analysis method according to claim 6, characterized in that: If the required display length of the fault cause is greater than the display length of the display device, the fault cause is displayed cyclically according to the display priority.

8. A power battery fault analysis device, characterized in that: include: An acquisition module, used to acquire fault data of the power battery; An output module, used to input the fault data into a fault analysis model, the fault analysis model outputs a fault identifier, wherein the fault analysis model analyzes the fault identifier corresponding to the fault data based on the fault signal type and the fault trigger condition corresponding to the fault signal type; A determination module is used to determine the cause of the failure of the power battery according to the failure identifier.

9. A vehicle, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the power battery fault analysis method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed, the power battery fault analysis method according to any one of claims 1 to 7 is implemented.

Images