CN115825745A

CN115825745A - Battery fault diagnosis method, battery fault diagnosis device and computer equipment

Info

Publication number: CN115825745A
Application number: CN202211135649.5A
Authority: CN
Inventors: 练隆华; 林晓
Original assignee: Contemporary Amperex Technology Co Ltd
Current assignee: Contemporary Amperex Technology Co Ltd
Priority date: 2022-09-19
Filing date: 2022-09-19
Publication date: 2023-03-21

Abstract

The application relates to a battery fault diagnosis method and device. The method comprises the following steps: acquiring a target fault code of a battery to be tested; determining a target configuration file corresponding to the target fault code; reading a target signal variable identification from the target configuration file; acquiring a signal variable address corresponding to the target signal variable identifier from a calibration description file based on the target signal variable identifier; and generating a data acquisition request, and sending the data acquisition request to a battery to be tested, wherein the data acquisition request carries the signal variable address, and the data acquisition request is used for indicating to acquire signal data corresponding to the signal variable address.

Description

Battery fault diagnosis method, battery fault diagnosis device and computer equipment

Technical Field

The present application relates to the field of fault diagnosis technology, and in particular, to a method for diagnosing a fault of a battery, a device for diagnosing a fault of a battery, a computer apparatus, a computer-readable storage medium, and a computer program product.

Background

In the field of fault diagnosis technology, for example, fault diagnosis of a battery management system is performed, and when a fault occurs in the system, it is generally preliminarily determined what type of fault has occurred by reading a fault code. However, in many cases, the specific cause of the fault cannot be accurately located based on the fault code, so the specific fault data of the battery needs to be read again, and the read fault data needs to be analyzed to determine the specific cause of the fault.

The conventional process of acquiring the fault data of the battery is performed based on a defined calibration description file. The calibration description file is a description file of an information reading and writing protocol, and the information reading and writing protocol defines the protocol content for reading and writing access to variables and variable addresses in the battery. In the process of acquiring fault data, the battery is accessed based on variables defined in the calibration description file and corresponding variable addresses to read corresponding fault data, and fault diagnosis of the battery is performed according to the corresponding fault data. However, the inventors found that the failure diagnosis of the battery in the conventional manner is inefficient.

Disclosure of Invention

In view of the above, it is necessary to provide one or more of a battery fault diagnosis method, a battery fault diagnosis apparatus, a computer device, a computer readable storage medium, and a computer program product for solving the above technical problems.

In a first aspect, the present application provides a method of diagnosing a fault of a battery. Wherein the method comprises the following steps:

acquiring a target fault code of a battery to be tested;

determining a target configuration file corresponding to the target fault code;

reading a target signal variable identification from the target configuration file;

acquiring a signal variable address corresponding to the target signal variable identifier from a calibration description file based on the target signal variable identifier;

and generating a data acquisition request, and sending the data acquisition request to the battery to be tested, wherein the data acquisition request carries the signal variable address, and the data acquisition request is used for indicating to acquire signal data corresponding to the signal variable address.

According to the battery fault diagnosis method, the fault codes and the configuration files have corresponding relations, namely each fault code has the configuration file corresponding to the fault code, the configuration file is configured with the signal variable identification of the signal data required to be read for positioning the specific fault reason corresponding to the fault code, therefore, after the specific fault reason needs to be positioned, the target configuration file corresponding to the target fault code is determined, the target signal variable identification of the signal data for positioning the specific fault reason of the target fault code is read from the target configuration file, the signal variable address of the target signal variable identification is obtained from the calibration description file based on the read target signal variable identification, and then the data acquisition request carrying the signal variable address is sent to the battery to be tested.

In some embodiments, the method further comprises the steps of:

acquiring the signal data returned by the battery to be tested based on the data acquisition request;

and acquiring the fault description information of the battery to be tested from the configuration file based on the signal data.

Therefore, fault description information corresponding to the signal variable identifications is also configured in the configuration file, and after signal data are obtained from the battery to be tested, corresponding fault description information can be further obtained from the configuration file based on the signal data, so that the specific fault reason of the battery to be tested can be diagnosed and determined based on the fault description information and the numerical value of the specific signal data.

In some embodiments, the determining the configuration file corresponding to the target fault code includes:

and receiving a configuration file selection instruction, and determining a configuration file corresponding to the configuration file selection instruction as a target configuration file corresponding to the target fault code.

Therefore, when the target configuration files corresponding to the target fault codes need to be determined, a user can operate the target configuration files to send out a configuration file selection instruction, and the configuration files corresponding to the configuration file selection instruction are determined to be the target configuration files corresponding to the target fault codes, so that the method is simple, convenient and fast, and high in automatic operability.

In some embodiments, the determining a target profile corresponding to the target fault code comprises:

and inquiring and determining a target configuration file corresponding to the target fault code according to the corresponding relation between the stored fault code and the configuration file.

Therefore, the corresponding relation between the fault codes and the configuration files is stored, the target configuration files corresponding to the target fault codes can be directly inquired and obtained according to the corresponding relation, and a user does not need to search and obtain which configuration file corresponding to the target fault codes by himself, so that which configuration file corresponds to the target fault codes can be rapidly determined, and the fault diagnosis efficiency is further improved.

In some embodiments, before reading the target signal variable identification from the target configuration file, the method further includes:

sending a configuration file acquisition request to a configuration file storage device, wherein the configuration file acquisition request carries a file identifier of the target configuration file;

and receiving a file acquisition response returned by the configuration file storage equipment, wherein the file acquisition response carries the target configuration file.

Therefore, the content of the specific configuration of the configuration file can be stored in the configuration file storage device, and is invisible to the device for locating the failure cause, that is, the device knows which configuration file corresponds to the target failure code, but does not know the specific configuration content of the configuration file, and when the failure needs to be located, the specific content of the target configuration file is obtained from the configuration file storage device, so that on one hand, the device for locating the failure cause is prevented from storing too many configuration files, the storage space is saved, on the other hand, the specific content of the configuration file is also prevented from being completely disclosed, and a malicious third party directly obtains a security file of data from the battery to be tested based on the configuration file, thereby improving the data security.

In some embodiments, the file retrieval response further comprises: a failure condition of the target profile;

the method further comprises the following steps:

and when the failure condition is met, performing failure treatment on the target configuration file.

Therefore, when the configuration file is obtained from the configuration file storage device, the configuration file storage device also returns the corresponding failure condition when returning the configuration file, and when the failure condition is met, the target configuration file is subjected to failure processing, so that a malicious third party is prevented from directly obtaining a security file of data from the battery to be tested based on the configuration file, and the data security is improved.

In some embodiments, the file acquisition request is a file acquisition request after at least one of a digital signature operation and an encryption operation is performed;

the method further comprises the following steps:

and at least one of decryption processing and digital signature verification operation is carried out on the file acquisition response to obtain the target configuration file.

Therefore, the equipment for fault diagnosis and positioning and the configuration file storage equipment also carry out encryption processing and digital signature operation on the transmitted data, the security of the data in the transmission process can be ensured through the encryption operation, the identity of a sender sending the data can be verified through the digital signature operation, and the security is improved.

In some embodiments, the method further comprises:

and returning a data display page to the user terminal, wherein the signal data is displayed on the data display page.

Therefore, the data acquisition process in the battery fault diagnosis process can be executed on equipment such as a cloud platform, the processes of reading the target configuration file, reading the signal variable address and acquiring the signal data from the battery to be detected are invisible to a user, the finally obtained signal data only need to be displayed to the user, and the data safety is further improved.

In some embodiments, said reading a target signal variable identification from said target profile comprises:

and reading all signal variable identifications in the target configuration file as the target signal variable identifications.

Therefore, all the signal variable identifications configured in the target configuration file can be used as target signal variable identifications, that is, signal data corresponding to all the signal variable identifications configured in the target configuration file can be obtained. The efficiency can be further improved without further analysis and processing processes on the target configuration file.

In some embodiments, the reading all signal variable identifiers in the configuration file as the target signal variable identifier includes:

and when the target configuration file only corresponds to one fault code, reading all signal variable identifications in the target configuration file as the target signal variable identifications.

Therefore, based on the embodiment, when the target configuration file only corresponds to one fault code uniquely, that is, all the signal variable identifiers configured in the target configuration file are used for determining and positioning the specific fault reason of the same fault code, the signal data obtained according to the method is more targeted and more accurate, and the positioning efficiency of the fault problem can be improved.

and when the target configuration file corresponds to more than two fault codes, reading a signal variable identifier corresponding to the target fault code in the target configuration file as the target signal variable identifier according to the corresponding relation between the fault codes in the target configuration file and the signal variable identifiers.

Therefore, when the target configuration file corresponds to more than two fault codes, the corresponding relation between the fault codes and the signal variable identifications in the target configuration file can be further determined, only the signal variable identifications corresponding to the target fault codes are used as the target signal variable identifications, and therefore the obtained target signal variable identifications are all used for determining and positioning the specific fault reasons of the same fault code, so that the obtained signal data are more targeted and more accurate, the acquisition of other signal data which are not used for positioning the specific fault reasons of the fault codes is avoided, and the efficiency of fault diagnosis can be improved.

In some embodiments, the generating a data acquisition request and sending the data acquisition request to the battery to be tested includes:

when more than two signal variable addresses exist, sequentially generating data acquisition requests corresponding to the signal variable addresses;

and sending the data acquisition requests corresponding to the signal variable addresses to the battery to be tested in sequence.

Therefore, when more than two signal variable addresses exist, only one signal variable address is carried in the data acquisition request sent each time, namely, only the signal data corresponding to one signal variable address is acquired from the battery to be tested each time, the influence of the signal transmission rate between the data acquisition request and the battery to be tested on signal transmission delay can be avoided as much as possible, the signal data can be acquired from the battery to be tested as soon as possible, the success rate of acquiring the signal data from the battery to be tested is ensured, and the fault reason corresponding to the target fault code is favorably positioned as soon as possible.

In some embodiments, before the obtaining, from the calibration description file, a signal variable address corresponding to the target signal variable identifier based on the target signal variable identifier, the method further includes:

and loading the calibration description file.

Therefore, the calibration description file is loaded in advance before the signal variable address corresponding to the target signal variable identifier is obtained, and when the target signal variable identifier is obtained from the configuration file, the signal variable address corresponding to the target signal variable identifier can be obtained from the loaded calibration description file.

In some embodiments, before sending the data obtaining request to the battery to be tested, the method further includes:

and establishing communication connection with the battery to be tested.

Therefore, when the specific reason of the fault needs to be located and the signal data specifically used for locating the fault needs to be obtained from the battery to be tested, the communication connection with the battery to be tested is established again, and the data obtaining request is sent to the battery to be tested based on the communication connection, so that the on-demand connection with the battery to be tested is realized, and the communication transmission resources are saved.

In a second aspect, an embodiment of the present application provides a device for diagnosing a fault of a battery, where the device includes:

the fault code acquisition module is used for acquiring a target fault code of the battery to be tested;

the file determining module is used for determining a target configuration file corresponding to the target fault code;

the variable identification reading module is used for reading a target signal variable identification from the target configuration file;

the address acquisition module is used for acquiring a signal variable address corresponding to the target signal variable identifier from a calibration description file based on the target signal variable identifier;

and the data request module is used for generating a data acquisition request and sending the data acquisition request to the battery to be tested, wherein the data acquisition request carries the signal variable address, and the data acquisition request is used for indicating to acquire signal data corresponding to the signal variable address.

In a third aspect, the present application provides a computer arrangement comprising a processor and a memory, said memory storing a computer program, wherein said computer program, when executed by said processor, causes said processor to carry out the steps of the method as in any of the embodiments described above.

In a fourth aspect, the present application provides a computer readable storage medium having a computer program stored thereon, wherein the computer program, when executed by the processor, causes the processor to carry out the steps of the method as in any of the embodiments described above.

In a fifth aspect, the present application provides a computer program product comprising a computer program, wherein the computer program when executed by a processor implements the steps of the method as in any of the embodiments described above.

The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.

Drawings

FIG. 1 is a schematic diagram of a fault diagnosis approach;

FIG. 2 is a schematic diagram of an application environment for fault diagnosis of a battery according to some embodiments of the present application;

fig. 3 is a schematic diagram of an application environment of a method for diagnosing a fault of a battery according to another embodiment of the present application;

fig. 4 is a schematic diagram of an application environment of a method for diagnosing a fault of a battery according to another embodiment of the present application;

FIG. 5 is a schematic flow chart diagram of a method of fault diagnosis of a battery according to some embodiments of the present application;

fig. 6 is a schematic flow chart illustrating the positioning of the cause of the fault according to the fault diagnosis method for a battery of the present application according to some embodiments of the present application;

FIG. 7 is a schematic illustration of an interface for determining fault codes according to some embodiments of the present application;

FIG. 8 is a schematic illustration of an interface for determining a target profile according to some embodiments of the present application;

fig. 9 is a schematic flowchart illustrating a method for diagnosing a fault of a battery according to an embodiment of the present disclosure;

fig. 10 is a block diagram showing a configuration of a failure diagnosis apparatus for a battery according to some embodiments of the present application;

FIG. 11 is a block diagram of a computer device according to some embodiments of the present application;

FIG. 12 is a block diagram of a computer device according to further embodiments of the present application.

Detailed Description

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The following examples are merely used to more clearly illustrate the technical solutions of the present application, and therefore are only examples, and the protection scope of the present application is not limited thereby.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein may be combined with other embodiments.

In the description of the embodiments of the present application, the term "and/or" is only one kind of association relationship describing an associated object, and means that three relationships may exist, for example, a and/or B, and may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.

In the description of the embodiments of the present application, the term "plurality" refers to two or more (including two), and similarly, "plural sets" refers to two or more (including two), and "plural pieces" refers to two or more (including two).

In the description of the embodiments of the present application, the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", "axial", "radial", "circumferential", and the like, indicate the directions or positional relationships indicated in the drawings, and are only for convenience of description of the embodiments of the present application and for simplicity of description, but do not indicate or imply that the referred device or element must have a specific direction, be constructed and operated in a specific direction, and thus, should not be construed as limiting the embodiments of the present application.

In the description of the embodiments of the present application, unless otherwise explicitly stated or limited, the terms "mounted," "connected," "fixed," and the like are used in a broad sense, and for example, may be fixedly connected, detachably connected, or integrated; mechanical connection or electrical connection is also possible; either directly or indirectly through intervening media, either internally or in any other relationship. The specific meanings of the above terms in the embodiments of the present application can be understood by those of ordinary skill in the art according to specific situations.

At present, various faults may occur in the operation process of equipment or devices, and when the equipment or devices have faults, corresponding fault codes are generated. After-sale or maintenance personnel of the equipment or the device need to combine the fault code to locate a specific fault reason so as to combine the specific fault reason to clear the fault, so that the equipment or the device can recover normal operation, or determine whether the equipment or the device needs to be replaced. In the fault locating process, in most cases, the fault code can only determine the type of the fault, and the fault code cannot characterize the specific fault cause of the fault, so that it is usually necessary to further obtain the relevant signal data of the equipment or device to locate the specific fault cause.

Taking equipment or devices as batteries as examples, the batteries are not only applied to energy storage power supply systems such as hydraulic power, firepower, wind power and solar power stations, but also widely applied to electric vehicles such as electric bicycles, electric motorcycles, electric automobiles and the like, and a plurality of fields such as military equipment, aerospace and the like. With the ever-expanding application field of batteries, the market demand is also increasing.

In the field of battery technology, after a battery fails, a Battery Management System (BMS) is generally used to locate the specific cause of the battery failure. When locating the cause of a battery failure, a Battery Management System (BMS) usually employs a UDS (universal diagnostic services) diagnostic service, specifically, when there is a failure, first, it primarily determines what failure has occurred by reading a failure code, and if the specific cause cannot be located, then, it analyzes the specific cause by reading failure snapshot data. As shown in fig. 1, the read fault code is P21E0DD, the corresponding fault is a 21E0DDHVB communication fault, and a specific fault reason cannot be determined based on the fault code, so that the fault snapshot data needs to be further read to analyze the specific reason, and as shown in fig. 1, the snapshot data read in the conventional manner may include various data such as the highest cell voltage of F010, the lowest cell voltage of F011, and the average cell voltage of F012 … … within a certain time.

The inventor of the present application has noted that the snapshot data obtained in this way is large in data size and requires a large storage space. Moreover, if the content of the specifically required snapshot data is not considered in the development stage, in the subsequent maintenance and use process, when new data is required, the content of the snapshot needs to be redefined, and the processes of software development, testing and verification are carried out again, so that the problems in actual use are difficult to locate, the whole vehicle cannot be maintained, or the maintenance time is long.

Based on the above consideration, the inventors of the present application have conducted intensive studies to provide a method of diagnosing a failure of a battery. The corresponding configuration file is defined for each fault code of the battery, and the signal variable identification of the signal data required to be read for positioning the specific fault reason corresponding to the fault code is configured in the configuration file. Therefore, when a specific fault cause needs to be located, after a specific fault code (referred to as a target fault code in the embodiment of the application) of a battery to be tested is obtained, a target configuration file corresponding to the target fault code is determined, a target signal variable identifier of signal data for locating the specific fault cause of the target fault code is read from the target configuration file, a signal variable address of the target signal variable identifier is obtained from a calibration description file based on the read target signal variable identifier, and a data acquisition request carrying the signal variable address is further sent to the battery to be tested.

The method for diagnosing the fault of the battery provided by the embodiment of the application can be applied to the application environment shown in fig. 2. The application environment relates to a processing device, a signal description file storage device, a configuration file storage device, a battery to be tested and a communication device. In some embodiments, the battery to be tested may specifically refer to a battery management system or a battery management unit that performs monitoring management on the battery, and the battery to be tested is collectively described in the following embodiments. The battery to be tested can monitor and store the semaphore of the battery to be tested. Wherein two or more of these devices may also be integrated in different embodiments. For example, in some embodiments, the processing device and the signal description file storage device may be an integral arrangement. For another example, in some embodiments, the processing device and the profile storage device may be integrally configured, i.e., the processing device may store some or all of the profiles itself. For another example, in some embodiments, the configuration file storage device may be a separate local server, or a device such as a cloud platform, and when it is needed, and the processing device determines by itself or queries from the local server/cloud platform which the needed configuration file is, then based on the file identifier of the configuration file, requests from the local server/cloud platform to obtain the specific configuration file corresponding to the file identifier. For another example, in some embodiments, the processing device, the signal description file storage device, and the configuration file storage device may be integrated with the cloud platform or the server, that is, the processing device, the signal description file storage device, and the configuration file storage device may be part of the cloud platform or the server, and when data used for locating a fault needs to be obtained, the user may send a request to the cloud platform or the server through the user terminal, and the cloud platform or the server performs processing such as searching the configuration file, reading a target signal variable identifier in the configuration file, and obtaining a signal variable address from a calibration description file. The cloud platform can be implemented by an independent server or a server cluster composed of a plurality of servers.

In some embodiments, referring to fig. 3, the processing device and the battery to be tested may be physically connected through a device such as a gateway, for example, the gateway and the battery to be tested may be connected through a CAN line, and the processing device and the gateway may be connected through a data line such as a USB line.

The method for diagnosing the fault of the battery provided by the embodiment of the application can be applied to an application environment as shown in fig. 4. The application environment relates to a battery to be tested, communication equipment, a cloud platform and a user terminal. The cloud platform is used for storing configuration files and calibration description files, and the user terminal is communicated with the cloud platform. The communication device may be a wireless communication gateway, a gateway device such as a wireless communication gateway (e.g., a 4G communication gateway, a 5G communication gateway), etc. In some embodiments, the communication device may be a battery commissioning terminal with a wireless communication function, such as a battery commissioning terminal with a 4G communication function or a 5G communication function. The user terminal can send a fault location request to the cloud platform by accessing a page provided by the cloud platform, the cloud platform executes processing of searching a configuration file, reading a target signal variable identifier in the configuration file, obtaining a signal variable address from a calibration description file, obtaining signal data from a battery to be tested based on the signal variable address, and the like, and returns the obtained signal data to the user terminal for display, for example, in a webpage returned to the user terminal, an APP terminal page, and the like, the signal data are displayed, and the user can obtain a fault diagnosis result based on the signal data displayed by the user terminal. The user terminal can be but not limited to various desktop computers, notebook computers, smart phones, tablet computers, internet of things equipment and portable wearable equipment, and the internet of things equipment can be smart sound boxes, smart televisions, smart air conditioners, smart vehicle-mounted equipment and the like. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, and the like.

Referring to fig. 5, an embodiment of the present application provides a method for diagnosing a fault of a battery, which is described by taking the processing device as described above or the cloud platform as shown in fig. 4 as an example. The method includes steps S501 to S505.

Step S501: and acquiring a target fault code of the battery to be tested.

The target fault code is a fault code for locating a fault cause generating a specific fault. In some embodiments, the target fault code may be a fault code of a fault generated in real time during the operation of the battery to be tested. In some embodiments, the target fault code may also be a fault code of a fault generated in history, and the embodiments of the present application are not particularly limited.

Step S502: and determining a target configuration file corresponding to the target fault code.

The target configuration file is a pre-configured configuration file corresponding to the target trouble code. The configuration file is configured with a signal variable identifier, referred to as a target signal variable identifier in this embodiment, for locating the signal variable identifier that generates the fault code. Wherein, a signal variable identification uniquely corresponds to a semaphore of the battery to be tested. The specific file form of the configuration file may be, for example, a text file, an excel file, or a file in other forms, and the embodiment of the present application is not particularly limited.

Optionally, in some embodiments, in the target configuration file, description information of the signal content corresponding to the signal variable identifier may also be configured, where the description information describes a description of the signal content corresponding to the signal variable identifier.

Optionally, in some embodiments, the target configuration file corresponding to the target fault code may further be configured with the target fault code, that is, the configuration file may store the corresponding fault code and the signal variable identifier at the same time, and may also store fault description information corresponding to the signal variable identifier at the same time.

Step S503: and reading a target signal variable identification from the target configuration file.

And after a target configuration file corresponding to the target fault code is determined, reading a target signal variable identifier configured in the target configuration file from the target configuration file.

Step S504: and acquiring a signal variable address corresponding to the target signal variable identifier from a calibration description file based on the target signal variable identifier.

The calibration description file is a description file of an information reading and writing protocol, the information reading and writing protocol defines protocol contents for reading and writing access to variables and memory contents in the battery, and the description contents in the calibration description file include corresponding relations between variable identifiers and variable addresses. Therefore, after the target signal variable identifier is obtained, the signal variable address corresponding to the target signal variable identifier can be obtained from the calibration description file.

Optionally, in some embodiments, the calibration description file may be an elf (The Executable and linking Format) file, in other embodiments, the calibration description file may also be an A2L file (a structured ASCII text file), and in other embodiments, the calibration description file may also be a map file (a mapping file). In the following embodiments of the present application, the calibration description file is taken as an elf file for illustration.

Step S505: and generating a data acquisition request, and sending the data acquisition request to a battery to be tested, wherein the data acquisition request carries the signal variable address, and the data acquisition request is used for indicating to acquire signal data corresponding to the signal variable address.

The data obtaining request is a request for requesting the battery to be tested to obtain information data corresponding to the specified signal variable address, where the data obtaining request may be generated based on an information read-write protocol corresponding to the calibration description file when the data obtaining request is generated, and the embodiment of the present application is not particularly limited.

According to some embodiments of the application, optionally, the method further comprises the step of:

For the signal data monitored by the battery, for some data amount, based on the signal data returned by the battery, it can be known what information the signal data represents, and what specific fault categories the different values of the signal data represent. However, for some data volumes, the specific fault category cannot be directly known based on the signal data returned by the battery, and the specific fault category represented by the value of the signal data can be known only by combining the corresponding fault description information.

Therefore, the configuration file is also provided with fault description information corresponding to each signal variable identifier, and after signal data are obtained from the battery to be tested, the corresponding fault description information can be further obtained from the configuration file based on the signal data, so that the specific fault reason of the battery to be tested can be diagnosed and determined based on the fault description information and the numerical value of the specific signal data.

It should be understood that, in the configuration file, there is a corresponding relationship between the configured signal variable identifier and the fault description information, for example, a certain signal variable identifier corresponds to the fault description information, and specifically, what type of fault the signal variable identifier corresponds to under the condition of different values.

According to some embodiments of the present application, optionally, the determining the configuration file corresponding to the target fault code includes:

The configuration file selection instruction may be an instruction issued by a user operation. In some embodiments, a user interface may be provided, and the user interface may be operated by a user to issue the profile selection instruction. The specific user operation interface may be implemented in any possible manner as long as the user can select the configuration file selection instruction in the user operation interface. For example, by displaying a list of some or all of the profiles on the user operation interface, the user can select a corresponding profile from the list, and after the selection is determined, a profile selection instruction can be issued.

In some embodiments, for example, in the scenario shown in fig. 3 in which the processing device directly completes the method for diagnosing the fault of the battery, the user operation interface may be provided by the processing device. In other embodiments, for example, in the scenario shown in fig. 4 where the cloud platform completes the method for diagnosing the fault of the battery, the ui may be provided to the user terminal by the cloud platform, and the user operates the ui displayed on the user terminal to issue the configuration file selection instruction.

Therefore, when the target configuration file corresponding to the target fault code needs to be determined, a user can operate the target configuration file to send a configuration file selection instruction, and the configuration file corresponding to the configuration file selection instruction is determined to be the target configuration file corresponding to the target fault code, so that the method is simple, convenient and fast, and high in autonomous operability.

According to some embodiments of the present application, optionally, the determining a target configuration file corresponding to the target fault code includes:

Optionally, in some embodiments, after determining the configuration file corresponding to the target fault code, the signal variable identifier configured in the configuration file and the description information of the corresponding signal content may be further displayed, so that a user may verify and determine whether the signal variable identifier that needs to be obtained is accurate, whether the configuration file needs to be adjusted, and the like.

Optionally, in some embodiments, reading a target signal variable identifier from the target configuration file includes:

Therefore, all the signal variable identifications configured in the target configuration file can be used as target signal variable identifications, that is, signal data corresponding to all the signal variable identifications configured in the target configuration file can be obtained. Further analysis and processing processes of the target configuration file are not needed, and efficiency can be further improved.

According to some embodiments of the present application, optionally, the reading all signal variable identifiers in the configuration file as the target signal variable identifier includes:

Therefore, based on the embodiment, the configuration file can only correspond to one fault code, that is, all the signal variable identifiers configured in the configuration file are used for determining and positioning the specific fault reason of the same fault code, so that the obtained signal data is more targeted and more accurate, and the positioning efficiency of the fault problem can be improved.

According to some embodiments of the application, optionally, the reading the target signal variable identifier from the target configuration file includes:

The target configuration file corresponds to more than two fault codes, which means that signal variable identifiers corresponding to more than two fault codes are configured in the same configuration file. For example, in some embodiments, the number of signal variable identifiers used to locate a specific cause of some fault codes is not large, and the signal variable identifiers corresponding to these fault codes may be configured in the same configuration file, which may reduce the number of configuration files that need to be configured.

Therefore, when the target configuration file corresponds to more than two fault codes, the corresponding relation between the fault codes and the signal variable identifications in the target configuration file can be further determined, only the signal variable identifications corresponding to the target fault codes are used as the target signal variable identifications, and therefore the obtained target signal variable identifications are all used for determining and positioning the specific fault reasons of the same fault code, so that the obtained signal data are more targeted and more accurate, the acquisition of other signal data which are not used for positioning the specific fault reasons of the fault codes is avoided, and the positioning efficiency of fault problems can be improved.

According to some embodiments of the present application, optionally, the generating a data obtaining request and sending the data obtaining request to a battery to be tested includes:

That is, when more than two signal variable addresses exist, only one signal variable address is carried in the data acquisition request sent each time, that is, only signal data corresponding to one signal variable address is acquired from the battery to be tested each time, so that the influence of the signal transmission rate between the battery to be tested and the battery to be tested on the signal transmission delay can be avoided as much as possible, the signal data can be acquired from the battery to be tested as soon as possible, the success rate of acquiring the signal data from the battery to be tested is ensured, and the fault reason corresponding to the target fault code can be located as soon as possible.

According to some embodiments of the present application, optionally, before reading the target signal variable identifier from the target configuration file, the method further includes:

and receiving a file acquisition response returned by the configuration file storage device, wherein the file acquisition response carries the target configuration file.

The configuration file storage device may specifically refer to a device that stores a configuration file, such as a database, or may refer to a device that can communicate with a device that performs fault location (i.e., a device that executes the method according to the embodiment of the present application), and search for the configuration file from the database and return the configuration file to the processing device, such as a server or a cloud service platform.

Therefore, the content of the specific configuration of the configuration file can be stored in the configuration file storage device, and is invisible to the device for locating the failure cause, that is, the device knows which configuration file the target failure code corresponds to, but does not know the specific configuration content of the configuration file, and when the failure needs to be located, the specific content of the target configuration file is obtained from the configuration file storage device, so that on one hand, the excessive storage of the configuration file by the processing device for locating the failure cause is avoided, the storage space is saved, on the other hand, the specific content of the configuration file is also avoided being completely disclosed, and the security problem caused by the fact that a malicious third party directly obtains data from a device to be tested based on the configuration file is avoided, and the data security is improved.

According to some embodiments of the present application, optionally, the file obtaining response further includes: a failure condition of the target profile;

the method further comprises the following steps:

Therefore, when the configuration file is obtained from the configuration file storage device, the configuration file storage device also returns the corresponding failure condition when returning the configuration file, and when the failure condition is met, the target configuration file is subjected to failure processing, so that the safety problem caused by the fact that a malicious third party directly obtains data from the battery to be tested based on the configuration file is avoided, and the data safety is improved.

Wherein the failure condition can be set in combination with the actual technical need. For example, in some embodiments, the failure condition may be a time to failure. That is, the configuration file returned by the configuration file storage device is only valid within a certain time period, and after the configuration file is returned to the processing device for a certain time period, the self-destruction mechanism of the configuration file is automatically started, and the specific self-destruction mechanism of the file can be set in combination with the actual technical requirements, which is not specifically limited in the embodiment of the present application.

According to some embodiments of the present application, optionally, in some embodiments, the file obtaining request is a file obtaining request after performing at least one of a digital signature operation and an encryption operation;

the method further comprises the following steps:

In some embodiments, the file acquisition request sent by the processing device to the configuration file storage device may be a file acquisition request after the processing device performs a digital signature, and after receiving the file acquisition request, the configuration file storage device verifies the digital signature of the processing device, and after the digital signature verification passes, obtains a configuration file corresponding to the file acquisition request, so as to send the target configuration file to the processing device. Therefore, after the identity of the processing device is verified, the configuration file storage device sends the configuration file to the processing device, so that the safety is improved.

In some embodiments, when the configuration file storage device returns the target configuration file to the processing device, the processing device may perform digital signature processing on the target configuration file, and after receiving a file acquisition response returned by the configuration file storage device, the processing device performs parsing after the digital signature passes, so as to obtain the target configuration file. After the identity authentication of the configuration file storage device is passed, the configuration file is analyzed to check the source of the configuration file, and the safety is improved.

In the above embodiment, the specific manner of performing the digital signature processing and the digital verification processing may be performed in any possible manner, and the embodiment of the present application is not limited in particular.

According to some embodiments of the present application, optionally, when the configuration file is returned to the processing device, the configuration file storage device may encrypt the configuration file and then return the encrypted configuration file to the processing device. After the processing device obtains the configuration file after the encryption processing, the processing device decrypts the configuration file after the encryption processing to obtain a specific configuration file, so that the security in the transmission process of the configuration file is improved. The specific encryption manner may be performed in any possible manner, such as symmetric encryption, asymmetric encryption, and the like, and the embodiment of the present application is not particularly limited.

It should be understood that, in an actual technical implementation, when the upper computer sends the configuration file, the digital signature and the encryption process may be performed at the same time, and the embodiment of the present application is not particularly limited.

According to some embodiments of the present application, optionally, before the obtaining, based on the target signal variable identifier, a signal variable address corresponding to the target signal variable identifier from a calibration description file, the method further includes:

and loading the calibration description file.

The loading of the calibration description file refers to loading specific file contents of the calibration description file, for example, loading the file contents of the calibration description file into a memory.

Therefore, the calibration description file is loaded in advance before the signal variable address corresponding to the target signal variable identifier is obtained, and when the target signal variable identifier is obtained from the configuration file, the signal variable address corresponding to the target signal variable identifier can be obtained from the loaded calibration description file, so that the efficiency of obtaining the signal variable address is improved.

According to some embodiments of the present application, optionally, before sending the data obtaining request to the battery to be tested, the method further includes:

and establishing communication connection with the battery to be tested.

The communication connection with the battery to be tested can be established in different ways. Taking the application environment shown in fig. 3 as an example, the processing device may be connected to the gateway through a data line (e.g., a USB line), and the gateway may be connected to the battery to be tested through a CAN line, so as to establish a communication connection between the processing device and the battery to be tested. Taking the application environment shown in fig. 4 as an example, the processing device may be connected to the gateway through a 4G communication network, a 5G communication network, or other wireless connection methods. And the gateway is directly connected with the battery to be tested through the data line.

Therefore, when the specific reason of the fault needs to be located and the signal data specifically used for locating the fault needs to be obtained from the battery to be detected, the communication connection with the battery to be detected is established, the data obtaining request is sent to the battery to be detected based on the communication connection, the connection with the battery to be detected as required is achieved, communication transmission resources are saved, and the safety of the data of the battery to be detected can be guaranteed.

Based on the embodiments described above, the following description is given in conjunction with several specific examples thereof.

Taking fault location for real-time faults as an example, as shown in fig. 6, when a battery to be tested fails, the battery to be tested (for example, a battery management system BMU of the battery to be tested) monitors the fault through an existing fault monitoring policy, and sets a corresponding fault code according to the fault monitoring policy, where the fault code may be prompted through a certain policy to notify a user, for example, to display on a related instrument panel, or to send the fault code to a user terminal through wireless communication or short message.

The user or after the fault occurs, firstly establishes the communication connection with the battery to be tested.

Taking the application environment shown in fig. 3 as an example, in some embodiments, the battery to be tested and the processing device may be connected through a wire harness, for example, the battery to be tested and the gateway are connected through a CAN line, the gateway and the processing device are connected through a USB line or another wire harness, and the communication connection between the battery to be tested and the processing device is realized through the gateway. Taking the USB wire connection between the gateway and the processing device as an example, the gateway converts the USB data sent by the processing device into the CAN data, and then sends the CAN data to the battery to be tested. After receiving CAN data returned by the battery to be tested, the gateway converts the CAN data into USB data and then sends the USB data to the processing equipment.

Taking the application environment shown in fig. 4 as an example, the cloud platform may establish a wireless communication connection with the gateway, and the gateway is connected with the battery to be tested through the data line, so as to implement the connection between the cloud platform and the battery to be tested.

After the connection between the processing equipment/cloud platform and the battery to be tested is established, the processing equipment/cloud platform loads a calibration description file elf file, configures a communication identifier for communication between the processing equipment/cloud platform and the battery to be tested, starts communication connection between the processing equipment/cloud platform and the battery to be tested, and then executes subsequent processes.

In the fault diagnosis process of a specific battery, a generated fault code (referred to as a target fault code in the embodiment of the present application) is read first, and a target configuration file corresponding to the target fault code is determined according to the target fault code.

In some embodiments, a fault code profile may be configured, and a target profile corresponding to the target fault code may be looked up in the profile. Referring to FIG. 7, in the fault code profile fault code txt, based on the current target fault code 619, it is determined that the current generated fault is a current null fault. Further, referring to fig. 8, the corresponding target profile is selected as the current validity exception profile: txt, which may also be referred to as a current validity configuration table in some embodiments.

And then reading all target signal variable identifications from the target configuration file, acquiring signal variable addresses corresponding to the target signal variable identifications from the calibration description file, and then generating and sending data acquisition requests to the battery to be tested so as to acquire specific signal data corresponding to the signal variable addresses from the battery to be tested.

In some embodiments, when the processing device/cloud platform sends a data acquisition request to the battery to be tested, and when the battery to be tested returns a data acquisition response to the processing device/cloud platform, the setting may be performed in the following manner as shown in table 1:

specifically, taking the signal variable address as 0x60012D5E and the length as 2 bytes as an example, the data obtaining request generated by the processing device/cloud platform may be as follows:

message ID	Message DLC	Message parameters
				402	8	F4 02 00 00 5E 2D 01 60

Correspondingly, the data acquisition response returned by the battery to be tested, taking the signal data as 0x3E8 as an example, may specifically be as follows:

message ID	Message DLC	Message parameters
				403	3	FF E8 03

After obtaining signal data from the battery under test, fault location may be performed based on the signal data.

Taking the application environment shown in fig. 3 as an example, after the processing device obtains the signal data, the user may directly locate the specific fault based on the signal data obtained by the processing device. Taking the application environment shown in fig. 4 as an example, after the cloud platform obtains the signal data, the signal data is returned to the user terminal, so that the signal data is displayed on a page presented by the user terminal, and a specific fault is located based on the signal data.

If a specific fault can be located based on these signal data, a specific fault location process is completed. If the specific fault cause cannot be located based on the signal data, the configuration file corresponding to the fault code is adjusted, and then the data acquisition and fault location processes are executed again until the specific fault cause is located, so that configurable fault diagnosis and location are realized.

For example, as shown in fig. 8, a specific current value of signal data corresponding to a target signal variable identifier SABCSA _ currentasesenorermmashwab … obtained from a battery to be tested is 1025, and description information of the target signal variable identifier SABCSA _ currentasensernerermashwab … obtained from a corresponding target configuration file is: bit0 current messages are lost; bit1 current message RollingCounter fault … …. Wherein, the loss of the bit0 current message indicates that when the current value is the value corresponding to bit0, the current fault is determined to be the loss of the current message. In fig. 8, the specific current value of the signal data corresponding to the target signal variable identifier sabcssa _ currentasenserrermmasbra … is 1025, and the corresponding value is bit10, so that it can be determined that the cause of the current invalid fault is the CSU fault state message loss.

Taking fault location of a historical fault as an example, referring to fig. 9, when a system fails, a battery to be tested detects the fault through an existing fault monitoring policy, and sets a corresponding fault code according to the fault monitoring policy, the battery to be tested stores the fault code and corresponding fault data, for example, the fault code and the corresponding fault data are stored in an EEPROM (Electrically Erasable Programmable read only memory) or an NVM (non-volatile memory), and data stored when a part of faults and faults occur in some application examples are shown in table 1 below.

Subsequently, when a specific fault reason generated by a certain fault code needs to be located, a user establishes communication connection between the processing equipment/cloud platform, loads a calibration description file elf file, configures a communication identifier for communication between the processing equipment/cloud platform and a battery to be tested, starts communication connection between the processing equipment/cloud platform and the battery to be tested, and then executes a subsequent data acquisition process. Other specific implementation processes are the same as those in the above embodiments, and are not described herein again.

It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be rotated or alternated with other steps or at least a part of the steps or stages in other steps.

Based on the same inventive concept, the embodiment of the present application further provides a battery fault diagnosis device for implementing the battery fault diagnosis method according to the embodiment. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the method, so specific limitations in the embodiment of the fault diagnosis device for one or more batteries provided below can be referred to the limitations of the fault diagnosis method for the battery above, and details are not repeated here.

According to some embodiments of the present application, referring to fig. 10, there is provided a failure diagnosis apparatus of a battery, wherein the apparatus includes: the system comprises a fault code acquisition module 1001, a file determination module 1002, a variable identifier reading module 1003, an address acquisition module 1004 and a data request module 1005.

A fault code acquisition module 1001 configured to acquire a target fault code of a battery to be tested;

a file determining module 1002, configured to determine a target configuration file corresponding to the target fault code;

a variable identifier reading module 1003, configured to read a target signal variable identifier from the target configuration file;

an address obtaining module 1004, configured to obtain, based on the target signal variable identifier, a signal variable address corresponding to the target signal variable identifier from a calibration description file;

a data request module 1005, configured to generate a data acquisition request and send the data acquisition request to a battery to be tested, where the data acquisition request carries the signal variable address, and the data acquisition request is used to instruct to acquire signal data corresponding to the signal variable address.

According to some embodiments of the application, optionally, further comprising:

the data acquisition module is used for acquiring the signal data returned by the battery to be tested based on the data acquisition request; and acquiring the fault description information of the battery to be tested from the configuration file based on the signal data.

According to some embodiments of the present application, optionally, the file determining module 1002 is configured to receive a configuration file selection instruction, and determine a configuration file corresponding to the configuration file selection instruction as a target configuration file corresponding to the target fault code.

According to some embodiments of the present application, optionally, the file determining module 1002 is configured to query and determine a target configuration file corresponding to the target fault code according to a correspondence between the stored fault code and the configuration file.

Optionally, according to some embodiments of the present application, the variable identifier reading module 1003 is configured to read all signal variable identifiers in the target configuration file, and use the read signal variable identifiers as the target signal variable identifiers.

According to some embodiments of the present application, optionally, the variable identifier reading module 1003 is configured to, when the target configuration file uniquely corresponds to one fault code, read all signal variable identifiers in the target configuration file, and use the read signal variable identifiers as the target signal variable identifiers.

According to some embodiments of the present application, optionally, the variable identifier reading module 1003 is configured to, when the target configuration file corresponds to more than two fault codes, read, according to a corresponding relationship between a fault code in the target configuration file and a signal variable identifier, a signal variable identifier corresponding to the target fault code in the target configuration file, as the target signal variable identifier.

According to some embodiments of the present application, optionally, the data request module 1005 is configured to, when there are more than two signal variable addresses, sequentially generate a data acquisition request corresponding to each of the signal variable addresses; and sending the data acquisition requests corresponding to the signal variable addresses to the battery to be tested in sequence.

According to some embodiments of the present application, optionally, the apparatus further includes a file request module, configured to send a configuration file acquisition request to the configuration file storage device, where the configuration file acquisition request carries a file identifier of the target configuration file; and receiving a file acquisition response returned by the configuration file storage device, wherein the file acquisition response carries the target configuration file.

and the file request module is also used for carrying out failure processing on the target configuration file when the failure condition is met.

According to some embodiments of the present application, optionally, the file obtaining request is a file obtaining request after performing at least one of a digital signature operation and an encryption operation; and the file request module is used for carrying out at least one of decryption processing and digital signature verification operation on the file acquisition response to obtain the target configuration file.

According to some embodiments of the present application, optionally, the mobile terminal further includes a data sending module, configured to return a data display page to the user terminal, where the signal data is displayed on the data display page.

Each module in the above-described failure diagnosis apparatus for a battery may be wholly or partially implemented by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent of a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a terminal or a server.

Taking a computer device as an example, the internal structure diagram thereof can be as shown in fig. 11. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor is configured to provide computational and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a method of diagnosing a failure of a battery as referred to in the embodiments described above. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Taking a computer device as an example of a server, the internal structure diagram thereof can be as shown in fig. 12. The computer device includes a processor, a memory, an Input/Output interface (I/O for short), and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operating system and the computer program to run on the non-volatile storage medium. The database of the computer device is used for storing configuration files, calibration description files and the like. The input/output interface of the computer device is used for exchanging information between the processor and an external device. The communication interface of the computer device is used for connecting and communicating with an external terminal through a network. The computer program is executed by a processor to implement a method of diagnosing a fault of a battery.

In one embodiment, there is further provided a computer device including a memory and a processor, the memory storing therein a computer program, the processor implementing the steps of the battery fault diagnosis method of any one of the above embodiments when executing the computer program.

In one embodiment, there is provided a computer-readable storage medium storing a computer program which, when executed by a processor, implements the steps of the method for diagnosing a failure of a battery of any one of the above-described embodiments.

In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the steps of the method for diagnosing the fault of the battery according to any one of the above embodiments.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present disclosure, and the present disclosure should be construed as being covered by the claims and the specification. In particular, the technical features mentioned in the embodiments can be combined in any way as long as there is no structural conflict. The present application is not intended to be limited to the particular embodiments disclosed herein but is to cover all embodiments that may fall within the scope of the appended claims.

Claims

1. A method of diagnosing a failure of a battery, the method comprising:

acquiring a target fault code of a battery to be tested;

determining a target configuration file corresponding to the target fault code;

2. The method according to claim 1, characterized in that the method further comprises the step of:

3. The method of claim 1, wherein determining the configuration file corresponding to the target fault code comprises:

4. The method of claim 1, wherein determining the target configuration file corresponding to the target fault code comprises:

5. The method according to any one of claims 1 to 4, wherein before reading the target signal variable identification from the target configuration file, further comprising:

sending a configuration file acquisition request to configuration file storage equipment, wherein the configuration file acquisition request carries a file identifier of the target configuration file;

6. The method of claim 5, wherein the file acquisition response further comprises: an expiration condition of the target profile;

the method further comprises the following steps:

7. The method according to claim 6, wherein the file acquisition request is a file acquisition request after at least one of a digital signature operation and an encryption operation is performed;

the method further comprises the following steps:

8. The method of claim 1, further comprising:

9. A failure diagnosis apparatus of a battery, characterized in that the apparatus comprises:

10. A computer device comprising a processor and a memory, the memory storing a computer program, characterized in that the computer program, when executed by the processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 8.