Fault diagnosis method, device, equipment and storage medium

Abstract

The present application relates to the technical field of vehicle battery replacement, and in particular to a fault diagnosis method, device, equipment and storage medium. The present application sends a fault diagnosis request to a target battery replacement vehicle, determines the fault diagnosis mode of the target battery replacement vehicle according to the fault diagnosis response result fed back by the vehicle, so as to automatically select a fault diagnosis mode that is compatible with the vehicle configuration, avoid functional operation disorders caused by incompatibility, and obtain fault information of a corresponding type after determining the fault diagnosis mode of the target battery replacement vehicle, and then perform fault diagnosis according to the fault information and the fault diagnosis mode, so as to realize fault diagnosis after vehicle battery replacement, avoid the technical problem that the vehicle cannot be diagnosed for faults if the battery and the vehicle machine are incompatible after battery replacement in the prior art, and meet the use requirements of the vehicle after battery replacement.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle battery replacement, and in particular to a fault diagnosis method, device, equipment and storage medium. BACKGROUND

[0002] After the new energy vehicle is replaced, the production manufacturer of the battery and the vehicle host are incompatible, which causes part of the functions of the vehicle to be unable to normally operate, and affects the normal operation of the vehicle, especially the battery-related functions, for example: the battery management system after the battery replacement, the vehicle host cannot perform fault diagnosis on the incompatible battery management system.

[0003] The above content is only used to assist in understanding the technical solutions of the present application and does not represent the acknowledgement of the above content as prior art. SUMMARY

[0004] The main purpose of the present application is to provide a fault diagnosis method, device, equipment and storage medium, which aims to solve the technical problem that the vehicle in the prior art cannot realize fault diagnosis after battery replacement if the battery and the vehicle are incompatible.

[0005] To achieve the above purpose, the present application provides a fault diagnosis method, which comprises the following steps:

[0006] Sending a fault diagnosis request to a target battery replacement vehicle to obtain a fault diagnosis response result;

[0007] Determining a target fault diagnosis mode according to the fault diagnosis response result;

[0008] Obtaining fault information of a type corresponding to the target fault diagnosis mode;

[0009] Performing fault diagnosis on the target battery replacement vehicle according to the fault information and the target fault diagnosis mode.

[0010] Optionally, the target fault diagnosis mode is determined according to the fault diagnosis response result, comprising:

[0011] Determining a fault diagnosis mode supported by the target battery replacement vehicle according to the fault diagnosis response result;

[0012] Determining a priority corresponding to the fault diagnosis mode according to a preset priority mapping table;

[0013] Determining a target fault diagnosis mode according to the priority and the fault diagnosis mode.

[0014] Optionally, the fault diagnosis mode comprises a unified fault diagnosis mode and an application message fault diagnosis mode.

[0015] The step of determining the fault diagnosis mode supported by the target battery swapping vehicle based on the fault diagnosis response result includes:

[0016] When a fault diagnosis response is received from the battery management system of the target battery swapping vehicle within a preset time period, it is determined that the fault diagnosis mode supported by the target battery swapping vehicle is the unified fault diagnosis mode and the application message fault diagnosis mode.

[0017] If no fault diagnosis response is received from the battery management system within a preset time period, the fault diagnosis mode supported by the target battery swapping vehicle is determined to be the application message fault diagnosis model.

[0018] Optionally, sending a fault diagnosis request to the target battery swapping vehicle includes:

[0019] Determine the address information and corresponding addressing strategy of the target battery swapping vehicle;

[0020] Based on the addressing strategy and the address information, a fault diagnosis request is sent to the target battery swapping vehicle.

[0021] Optionally, the address information includes: first address information and second address information, and the addressing strategy includes: functional addressing and physical addressing, wherein the functional addressing corresponds to the first address information and the physical addressing corresponds to the second address information;

[0022] The step of sending a fault diagnosis request to the target battery swapping vehicle based on the addressing strategy and the address information includes:

[0023] Functional addressing is performed based on the first address information to broadcast a fault diagnosis request to the communication mainline in the target battery swapping vehicle.

[0024] Physical addressing is performed based on the second address information to send a fault diagnosis request to the battery management system in the target battery swapping vehicle.

[0025] Optionally, the fault information includes: fault diagnostic codes and snapshot information;

[0026] The step of diagnosing the target battery swapping vehicle based on the fault information and the target fault diagnosis mode includes:

[0027] When the target fault diagnosis mode is the unified fault diagnosis mode, obtain the fault diagnosis codes and current snapshot information recorded by the battery management system;

[0028] Obtain the historical fault records of the target battery swapping vehicle;

[0029] The current snapshot information is matched with the preset fault database, and the target battery swapping vehicle at the current moment is diagnosed based on the matching result, the fault diagnosis code, and the historical fault records.

[0030] Optionally, the fault information may further include: application messages;

[0031] The step of diagnosing the target battery swapping vehicle based on the fault information and the target fault diagnosis mode includes:

[0032] When the target fault diagnosis mode is the application message fault diagnosis model, the current application message of the battery management system is obtained;

[0033] Extract the vehicle system parameters from the current application message;

[0034] The vehicle's parameters are matched with a preset fault database, and the target battery swapping vehicle at the current moment is diagnosed based on the matching results, the fault diagnosis code, and the historical fault records.

[0035] Furthermore, to achieve the above objectives, the present invention also proposes a fault diagnosis device, the fault diagnosis device comprising:

[0036] The request module is used to send a fault diagnosis request to the target battery swapping vehicle and obtain the fault diagnosis response result fed back by the target battery swapping vehicle.

[0037] The determination module is used to determine the target fault diagnosis mode based on the fault diagnosis response result;

[0038] The acquisition module is used to acquire fault information of the type corresponding to the target fault diagnosis mode;

[0039] The diagnostic module is used to perform fault diagnosis on the target battery swapping vehicle based on the fault information and the target fault diagnosis mode.

[0040] Furthermore, to achieve the above objectives, the present invention also proposes a fault diagnosis device, which includes a memory and a processor. The memory stores a fault diagnosis program that can run on the processor, and the fault diagnosis program is configured to implement the steps of the fault diagnosis method described above.

[0041] In addition, to achieve the above objectives, the present invention also proposes a storage medium storing a fault diagnosis program, which, when executed by a processor, implements the steps of the fault diagnosis method described above.

[0042] This invention discloses a fault diagnosis method, comprising: sending a fault diagnosis request to a target battery swapping vehicle and obtaining a fault diagnosis response result; determining a target fault diagnosis mode based on the fault diagnosis response result; acquiring fault information of the type corresponding to the target fault diagnosis mode; and performing fault diagnosis on the target battery swapping vehicle based on the fault information and the target fault diagnosis mode. Compared with the prior art, this invention determines the fault diagnosis mode of the target battery swapping vehicle by sending a fault diagnosis request to the target battery swapping vehicle and based on the fault diagnosis response result fed back by the vehicle. This achieves automatic selection of a fault diagnosis mode that matches the vehicle configuration, avoiding functional operation obstacles caused by incompatibility. Furthermore, after determining the fault diagnosis mode of the target battery swapping vehicle, acquiring the corresponding type of fault information and then performing fault diagnosis based on the fault information and the fault diagnosis mode enables fault diagnosis after battery swapping, avoiding the technical problem in the prior art where fault diagnosis cannot be achieved if the battery and vehicle system are incompatible after battery swapping, thus meeting the user's vehicle usage needs after battery swapping. Attached Figure Description

[0043] Figure 1 This is a schematic diagram of the structure of a fault diagnosis device for the hardware operating environment involved in the embodiments of the present invention;

[0044] Figure 2 This is a flowchart illustrating the first embodiment of the fault diagnosis method of the present invention;

[0045] Figure 3 This is a flowchart illustrating the second embodiment of the fault diagnosis method of the present invention;

[0046] Figure 4 This is a flowchart illustrating the third embodiment of the fault diagnosis method of the present invention;

[0047] Figure 5 This is a fault diagnosis timing diagram of an embodiment of the fault diagnosis method of the present invention;

[0048] Figure 6 This is a structural block diagram of the first embodiment of the fault diagnosis device of the present invention.

[0049] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0050] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0051] Reference Figure 1 , Figure 1 This is a schematic diagram of the fault diagnosis device structure of the hardware operating environment involved in the embodiment of the present invention.

[0052] like Figure 1 As shown, the fault diagnosis device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen and an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wireless-Fidelity (Wi-Fi) interface). The memory 1005 may be high-speed random access memory (RAM) or stable non-volatile memory (NVM), such as a disk storage device. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0053] Those skilled in the art will understand that Figure 1 The structure shown does not constitute a limitation on the fault diagnosis equipment and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0054] like Figure 1 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a network communication module, a user interface module, and a fault diagnosis program.

[0055] exist Figure 1 In the fault diagnosis device shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the fault diagnosis device of the present invention can be set in the fault diagnosis device, and the fault diagnosis device calls the fault diagnosis program stored in the memory 1005 through the processor 1001 and executes the fault diagnosis method provided in the embodiment of the present invention.

[0056] This invention provides a fault diagnosis method, referring to... Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of a fault diagnosis method according to the present invention.

[0057] In this embodiment, the fault diagnosis method includes the following steps:

[0058] Step S10: Send a fault diagnosis request to the target battery swapping vehicle and obtain the fault diagnosis response result.

[0059] It should be noted that the execution subject of the method in this embodiment can be a device with data processing, network communication and data transmission functions, such as a terminal device, cloud server or control computer, or other devices that can achieve the same or similar functions. This embodiment does not impose specific limitations on this. In this embodiment and the following embodiments, a terminal device will be used as an example for explanation.

[0060] It is worth noting that the target battery swapping vehicles refer to new energy vehicles that have had their energy storage battery packs replaced. As there is currently no industry standard for battery swapping technology, the fault diagnosis methods of BMS from different OEMs and suppliers vary, which may lead to inconsistencies in parameters, management systems, and models of battery packs produced by different battery manufacturers. Consequently, after the vehicle completes the battery swap, the vehicle's infotainment system cannot read the information from the battery management system, and therefore cannot perform fault diagnosis on the vehicle.

[0061] Understandably, fault diagnosis requests are used to detect whether the vehicle's infotainment system and battery management system (BMS) can communicate or transmit data normally. For example, if a fault diagnosis response is received after sending a fault diagnosis request to the target battery swapping vehicle, it indicates that the communication between the vehicle's infotainment system and the BMS is normal. If no fault diagnosis response is received after sending a fault diagnosis request to the target battery swapping vehicle, it indicates that the vehicle's infotainment system and the BMS are incompatible, and fault detection cannot be performed.

[0062] It should be noted that, in this embodiment, the fault diagnosis response results include: receiving a fault diagnosis response from the target battery swapping vehicle within a preset time, or receiving a fault diagnosis response from the target battery swapping vehicle outside the preset time, and not receiving a fault diagnosis response from the target battery swapping vehicle at all. In the first case, it will be considered that the vehicle's infotainment system and the battery management system can communicate normally and there is no incompatibility.

[0063] In practice, after the vehicle battery is swapped, the terminal device TBOX, in the ON position, sends a UDS diagnostic 19 service request to the BMS. If no fault response is received from the BMS within a certain period of time, the TBOX records that the BMS system corresponding to the current supplier does not support UDS diagnostics.

[0064] Step S20: Determine the target fault diagnosis mode based on the fault diagnosis response results.

[0065] It should be understood that different fault diagnosis response results will affect the fault diagnosis mode of the target battery swapping vehicle. In particular, different fault diagnosis response results can also be used to determine the fault diagnosis mode supported by the target battery swapping vehicle, and then determine the target fault diagnosis mode to be operated based on the priority of different fault diagnosis modes.

[0066] In this embodiment, the fault diagnosis modes include, but are not limited to, Unified Diagnostic Services (UDS) and application message fault diagnosis modes. The priority of different diagnosis modes can be referred to Table 1.

[0067]

[0068] In the specific implementation, under the unified fault diagnosis mode, there are multiple diagnostic services, each corresponding to a negative response code. For example, when the server is busy executing a requested diagnostic service and cannot execute the currently requested diagnostic service, it replies with this code 0x21; when the service identifier (Service ID) in the diagnostic request is not supported in the current session, it replies with 0x7F, etc. This embodiment does not impose specific restrictions on this.

[0069] Step S30: Obtain fault information corresponding to the type of the target fault diagnosis mode.

[0070] It should be noted that different fault diagnosis modes obtain different fault information, which includes, but is not limited to: fault diagnosis codes, snapshot information, and application messages.

[0071] Step S40: Perform fault diagnosis on the target battery swapping vehicle based on the fault information and the target fault diagnosis mode.

[0072] Understandably, the unified fault diagnosis mode has a higher priority than the application message fault diagnosis mode. When the target battery swapping vehicle is running the unified fault diagnosis mode, the fault diagnosis code (i.e., the negative response code) and snapshot information will be used to analyze whether the vehicle has a fault. When the target battery swapping vehicle is running the application message fault diagnosis mode, the application message will be used to analyze whether the vehicle has a fault.

[0073] This embodiment discloses a fault diagnosis method, which includes: sending a fault diagnosis request to a target battery swapping vehicle and obtaining a fault diagnosis response result; determining a target fault diagnosis mode based on the fault diagnosis response result; obtaining fault information of the type corresponding to the target fault diagnosis mode; and performing fault diagnosis on the target battery swapping vehicle based on the fault information and the target fault diagnosis mode. This embodiment achieves automatic selection of a fault diagnosis mode that matches the vehicle configuration by sending a fault diagnosis request to the target battery swapping vehicle and determining the fault diagnosis mode based on the vehicle's feedback fault diagnosis response result. This avoids functional operational obstacles caused by incompatibility. Furthermore, after determining the fault diagnosis mode of the target battery swapping vehicle, it obtains corresponding fault information and then performs fault diagnosis based on the fault information and the fault diagnosis mode, thus realizing fault diagnosis after battery swapping. This avoids the technical problem in existing technologies where, if the battery and vehicle system are incompatible after battery swapping, fault diagnosis cannot be achieved, thus meeting the user's vehicle usage needs after battery swapping.

[0074] refer to Figure 3 , Figure 3 This is a flowchart illustrating a second embodiment of a fault diagnosis method according to the present invention.

[0075] Based on the first embodiment described above, in this embodiment, step S20 includes:

[0076] Step S201: Determine the fault diagnosis mode supported by the target battery swapping vehicle based on the fault diagnosis response result.

[0077] It should be noted that, in this embodiment, the fault diagnosis response results include: receiving a fault diagnosis response from the target battery swapping vehicle within a preset time, or receiving a fault diagnosis response from the target battery swapping vehicle outside the preset time, and not receiving a fault diagnosis response from the target battery swapping vehicle at all. In the first case, it will be considered that the vehicle's infotainment system and the battery management system can communicate normally and there is no incompatibility. In the latter two cases, it will be determined that the vehicle's infotainment system and the battery management system are incompatible and cannot be diagnosed through the unified fault diagnosis mode.

[0078] Further, determining the fault diagnosis mode supported by the target battery swapping vehicle based on the fault diagnosis response result includes:

[0079] When a fault diagnosis response is received from the battery management system of the target battery swapping vehicle within a preset time period, it is determined that the fault diagnosis mode supported by the target battery swapping vehicle is the unified fault diagnosis mode and the application message fault diagnosis mode.

[0080] If no fault diagnosis response is received from the battery management system within a preset time period, the fault diagnosis mode supported by the target battery swapping vehicle is determined to be the application message fault diagnosis model.

[0081] The preset duration is either set by the user or automatically generated by the system. In this embodiment, it can be set to 150ms, but this embodiment does not impose any specific restrictions on it.

[0082] In practice, if the target battery swapping vehicle's battery management system supports UDS diagnostic mode, when the remote monitoring terminal TBOX receives a fault uploaded by the application message, it will consider that the priority of UDS diagnosis is higher than that of the application message's diagnostic mode and maintain the current UDS diagnostic mode. If the target battery swapping vehicle's battery management system does not support UDS diagnostic mode, the TBOX will use the application message's fault diagnosis mode to record the BMS's fault level and specific fault information in real time and upload it to the backend for easy fault query and tracing.

[0083] Step S202: Determine the priority corresponding to the fault diagnosis mode according to the preset priority mapping table.

[0084] It should be noted that the preset priority mapping table can be as shown in Table 1. In this embodiment, negative response codes and priorities for other fault diagnosis modes are also reserved to facilitate subsequent updates to the fault diagnosis technology.

[0085] Step S203: Determine the target fault diagnosis mode based on the priority and the fault diagnosis mode.

[0086] Understandably, the target fault diagnosis mode for the target battery swapping vehicle can be determined according to the priority relationship recorded in the preset priority mapping table. For example, if the target battery swapping vehicle can run the UDS fault diagnosis mode or the application message fault diagnosis mode, the UDS fault diagnosis mode will be used in a limited manner because the priority of the UDS diagnosis mode is higher than that of the application message fault diagnosis mode.

[0087] This embodiment determines the fault diagnosis modes supported by the battery management system by analyzing the fault diagnosis response results of the target battery swapping vehicle, determines the priority of each fault diagnosis mode by querying a preset priority mapping table, and finally determines the actual operating fault diagnosis mode. This avoids the problem of not being able to diagnose faults in battery swapping vehicles when the vehicle's infotainment system and battery management system are incompatible, thereby improving the reliability of fault diagnosis for battery swapping vehicles.

[0088] In this embodiment, step S10 includes:

[0089] Step S101: Determine the address information and corresponding addressing strategy of the target battery swapping vehicle.

[0090] It should be noted that the address information includes first address information and second address information, and the addressing strategy includes: functional addressing and physical addressing. The functional addressing corresponds to the first address information, and the physical addressing corresponds to the second address information.

[0091] In practical implementation, there are often many electronic control units on the vehicle bus. As a diagnostic device, it can communicate with all electronic control units together or communicate with a specific electronic control unit individually. Therefore, there are two addressing methods: functional addressing and physical addressing. Functional addressing can broadcast diagnostic requests and wait for diagnostic responses from electronic control units on the bus. Physical addressing, on the other hand, sends specific diagnostic requests and waits for fault diagnosis responses from specific electronic control units.

[0092] Further, the step of sending a fault diagnosis request to the target battery swapping vehicle based on the addressing strategy and the address information includes:

[0093] Functional addressing is performed based on the first address information to broadcast a fault diagnosis request to the communication mainline in the target battery swapping vehicle.

[0094] Physical addressing is performed based on the second address information to send a fault diagnosis request to the battery management system in the target battery swapping vehicle.

[0095] For example, if the first address information ID is 0x18DB33F1 and the second address information ID is 0x18DAD1F1, then functional addressing is performed based on 0x18DB33F1 to broadcast a fault diagnosis request to the communication mainline in the target battery swapping vehicle; physical addressing is performed based on 0x18DAD1F1 to send a fault diagnosis request to the battery management system in the target battery swapping vehicle.

[0096] Step S102: Send a fault diagnosis request to the target battery swapping vehicle based on the addressing strategy and the address information.

[0097] This embodiment uses different addressing methods to send fault diagnosis requests to the battery management system in the target battery swapping vehicle, so as to receive fault diagnosis responses in the future and execute different fault diagnosis strategies, thereby improving the reliability of fault diagnosis of the battery management system.

[0098] refer to Figure 4 , Figure 4 This is a flowchart illustrating a third embodiment of a fault diagnosis method according to the present invention.

[0099] Based on the second embodiment described above, in this embodiment, step S40 includes:

[0100] Step S401: When the target fault diagnosis mode is the unified fault diagnosis mode, obtain the fault diagnosis codes and current snapshot information recorded by the battery management system.

[0101] It should be noted that the fault diagnosis code refers to the negative response code in the UDS fault diagnosis mode. During product design, all possible faults are listed based on the product hardware, and a code is assigned to each specific fault. This code is the diagnostic fault code. For example, the fault code for low power supply voltage is defined as U2E0468. The diagnostic fault code can be understood as the fault's ID number. The fault code corresponds to the fault's occurrence conditions, recovery conditions, and fault content.

[0102] In the unified fault diagnosis mode, there are multiple diagnostic services, each corresponding to a negative response code. For example, when the server is busy executing a requested diagnostic service and cannot execute the currently requested diagnostic service, it replies with code 0x21; when the service identifier (Service ID) in the diagnostic request is not supported in the current session, it replies with 0x7F, etc. This embodiment does not impose specific restrictions on this.

[0103] It is understood that snapshot information is a specific data record associated with the fault diagnostic code and stored in a preset storage space. Snapshot information is often used to store vehicle status information and environmental status information at the time of the fault, such as: current ignition time, mileage, vehicle mode, vehicle speed and outside temperature, etc. This embodiment does not impose specific limitations on this.

[0104] In addition, a diagnostic code supports one or more snapshot data, each snapshot data is represented by a snapshot record identifier and each snapshot contains one or a set of specified data.

[0105] Step S402: Obtain the historical fault records of the target battery swapping vehicle.

[0106] Step S403: Match the current snapshot information with the preset fault database, and perform fault diagnosis on the target battery swapping vehicle at the current moment based on the matching result, the fault diagnosis code, and the historical fault records.

[0107] It should be understood that matching the current snapshot information with the preset fault database can involve matching information such as the current ignition time, mileage, vehicle mode, vehicle speed, and outside temperature with records of past faults to detect whether there is a high probability of a fault occurring.

[0108] In specific implementation, in order to improve the accuracy of fault diagnosis, the matching results, the fault diagnosis code and the historical fault records can be combined to perform fault diagnosis on the target battery swapping vehicle at the current moment. This embodiment does not impose specific restrictions on this.

[0109] Based on the second embodiment described above, in this embodiment, step S40 further includes:

[0110] Step S401: When the target fault diagnosis mode is the application message fault diagnosis model, obtain the current application message of the battery management system;

[0111] Step S402: Extract the vehicle system parameters from the current application message;

[0112] Step S403: Match the vehicle parameters with the preset fault database, and perform fault diagnosis on the target battery swapping vehicle at the current moment based on the matching results.

[0113] It should be noted that since the application messages are all actual operating parameters, they cannot be directly diagnosed by the battery management system. Therefore, it is necessary to send the current application messages to the terminal device for fault analysis. The means of implementation can be parameter matching or training a neural network model, or other methods that can achieve fault diagnosis. This embodiment does not impose specific restrictions on this.

[0114] The vehicle system parameters can include battery output power, running time, voltage value, and vehicle power requirements, etc. This embodiment does not impose specific restrictions on these parameters.

[0115] In the specific implementation, refer to Figure 5 , Figure 5 This is a fault diagnosis timing diagram for this embodiment. In this embodiment, a diagnosis request is first sent to the battery swapping vehicle, and the diagnosis response result fed back by the battery management system of the battery swapping vehicle is detected, so as to determine which fault diagnosis mode to use for fault diagnosis.

[0116] This embodiment improves the reliability of fault diagnosis by performing corresponding fault diagnosis operations for different fault diagnosis modes. When the target fault diagnosis mode is a unified fault diagnosis mode, fault diagnosis is performed based on snapshot information, historical fault records, and fault diagnosis codes. When the target fault diagnosis mode is an application message fault diagnosis model, fault diagnosis is performed based on the vehicle's application messages.

[0117] Furthermore, embodiments of the present invention also propose a storage medium storing a fault diagnosis program, wherein the fault diagnosis program, when executed by a processor, implements the steps of the fault diagnosis method described above.

[0118] Since this storage medium adopts all the technical solutions of all the above embodiments, it has at least all the beneficial effects brought about by the technical solutions of the above embodiments, which will not be repeated here.

[0119] Reference Figure 6 , Figure 6 This is a structural block diagram of the first embodiment of the fault diagnosis device of the present invention.

[0120] like Figure 6 As shown, the fault diagnosis device proposed in this embodiment of the invention includes:

[0121] The request module 10 is used to send a fault diagnosis request to the target battery swapping vehicle and obtain the fault diagnosis response result fed back by the target battery swapping vehicle.

[0122] The determination module 20 is used to determine the target fault diagnosis mode based on the fault diagnosis response result.

[0123] The acquisition module 30 is used to acquire fault information of the type corresponding to the target fault diagnosis mode.

[0124] The diagnostic module 40 is used to perform fault diagnosis on the target battery swapping vehicle based on the fault information and the target fault diagnosis mode.

[0125] In one embodiment, the determining module 20 is further configured to determine the fault diagnosis mode supported by the target battery swapping vehicle based on the fault diagnosis response result; determine the priority corresponding to the fault diagnosis mode based on a preset priority mapping table; and determine the target fault diagnosis mode based on the priority and the fault diagnosis mode.

[0126] In one embodiment, the determining module 20 is further configured to, when receiving a fault diagnosis response from the battery management system in the target battery swapping vehicle within a preset time period, determine that the fault diagnosis mode supported by the target battery swapping vehicle is a unified fault diagnosis mode and an application message fault diagnosis mode; and when not receiving a fault diagnosis response from the battery management system within the preset time period, determine that the fault diagnosis mode supported by the target battery swapping vehicle is an application message fault diagnosis model.

[0127] In one embodiment, the request module 10 is further configured to determine the address information and corresponding addressing strategy of the target battery swapping vehicle; and send a fault diagnosis request to the target battery swapping vehicle based on the addressing strategy and the address information.

[0128] In one embodiment, the request module 10 is further configured to perform functional addressing based on the first address information to broadcast a fault diagnosis request to the communication mainline in the target battery swapping vehicle; and to perform physical addressing based on the second address information to send a fault diagnosis request to the battery management system in the target battery swapping vehicle.

[0129] In one embodiment, the diagnostic module 40 is further configured to, when the target fault diagnosis mode is a unified fault diagnosis mode, obtain the fault diagnosis code and current snapshot information recorded by the battery management system; obtain the historical fault records of the target battery swapping vehicle; perform parameter matching between the current snapshot information and a preset fault database; and perform fault diagnosis on the target battery swapping vehicle at the current moment based on the matching result, the fault diagnosis code, and the historical fault records.

[0130] In one embodiment, the diagnostic module 40 is further configured to: obtain the current application message of the battery management system when the target fault diagnosis mode is the application message fault diagnosis model; extract the vehicle parameters in the current application message; match the vehicle parameters with a preset fault database; and perform fault diagnosis on the target battery swapping vehicle at the current moment based on the matching result, the fault diagnosis code, and the historical fault records.

[0131] This embodiment discloses a fault diagnosis method, which includes: sending a fault diagnosis request to a target battery swapping vehicle and obtaining a fault diagnosis response result; determining a target fault diagnosis mode based on the fault diagnosis response result; obtaining fault information of the type corresponding to the target fault diagnosis mode; and performing fault diagnosis on the target battery swapping vehicle based on the fault information and the target fault diagnosis mode. This embodiment achieves automatic selection of a fault diagnosis mode that matches the vehicle configuration by sending a fault diagnosis request to the target battery swapping vehicle and determining the fault diagnosis mode based on the vehicle's feedback fault diagnosis response result. This avoids functional operational obstacles caused by incompatibility. Furthermore, after determining the fault diagnosis mode of the target battery swapping vehicle, it obtains corresponding fault information and then performs fault diagnosis based on the fault information and the fault diagnosis mode, thus realizing fault diagnosis after battery swapping. This avoids the technical problem in existing technologies where, if the battery and vehicle system are incompatible after battery swapping, fault diagnosis cannot be achieved, thus meeting the user's vehicle usage needs after battery swapping.

[0132] It should be understood that the above are merely illustrative examples and do not constitute any limitation on the technical solutions of the present invention. In specific applications, those skilled in the art can make settings as needed, and the present invention does not impose any restrictions on this.

[0133] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of this invention. In practical applications, those skilled in the art can select some or all of the workflow to achieve the purpose of this embodiment according to actual needs, and no restrictions are imposed here.

[0134] In addition, for technical details not described in detail in this embodiment, please refer to the fault diagnosis method provided in any embodiment of the present invention, which will not be repeated here.

[0135] Furthermore, it should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0136] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0137] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory (ROM) / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0138] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A fault diagnosis method, characterized in that, The fault diagnosis method includes: Send a fault diagnosis request to the target battery swapping vehicle and obtain the fault diagnosis response result; The target fault diagnosis mode is determined based on the fault diagnosis response results. Obtain fault information corresponding to the type of the target fault diagnosis mode; The target battery swapping vehicle is diagnosed based on the fault information and the target fault diagnosis mode. Determining the target fault diagnosis mode based on the fault diagnosis response results includes: The fault diagnosis mode supported by the target battery swapping vehicle is determined based on the fault diagnosis response results. The fault diagnosis modes include: unified fault diagnosis mode and application message fault diagnosis mode. The step of determining the fault diagnosis mode supported by the target battery swapping vehicle based on the fault diagnosis response result includes: When a fault diagnosis response is received from the battery management system of the target battery swapping vehicle within a preset time period, it is determined that the fault diagnosis mode supported by the target battery swapping vehicle is the unified fault diagnosis mode and the application message fault diagnosis mode. If no fault diagnosis response is received from the battery management system within a preset time period, the fault diagnosis mode supported by the target battery swapping vehicle is determined to be the application message fault diagnosis model.

2. The fault diagnosis method as described in claim 1, characterized in that, The fault diagnosis method further includes: The priority corresponding to the fault diagnosis mode is determined according to a preset priority mapping table; The target fault diagnosis mode is determined based on the priority and the fault diagnosis mode.

3. The fault diagnosis method as described in claim 1, characterized in that, Sending a fault diagnosis request to the target battery swapping vehicle includes: Determine the address information and corresponding addressing strategy of the target battery swapping vehicle; Based on the addressing strategy and the address information, a fault diagnosis request is sent to the target battery swapping vehicle.

4. The fault diagnosis method as described in claim 3, characterized in that, The address information includes: first address information and second address information; the addressing strategy includes: functional addressing and physical addressing; the functional addressing corresponds to the first address information; and the physical addressing corresponds to the second address information. The step of sending a fault diagnosis request to the target battery swapping vehicle based on the addressing strategy and the address information includes: Functional addressing is performed based on the first address information to broadcast a fault diagnosis request to the communication mainline in the target battery swapping vehicle. Physical addressing is performed based on the second address information to send a fault diagnosis request to the battery management system in the target battery swapping vehicle.

5. The fault diagnosis method according to any one of claims 1-4, characterized in that, The fault information includes: fault diagnostic codes and snapshot information; The step of diagnosing the target battery swapping vehicle based on the fault information and the target fault diagnosis mode includes: When the target fault diagnosis mode is the unified fault diagnosis mode, obtain the fault diagnosis codes and current snapshot information recorded by the battery management system; Obtain the historical fault records of the target battery swapping vehicle; The current snapshot information is matched with the preset fault database, and the target battery swapping vehicle at the current moment is diagnosed based on the matching result, the fault diagnosis code, and the historical fault records.

6. The fault diagnosis method as described in claim 5, characterized in that, The fault information also includes: application messages; The step of diagnosing the target battery swapping vehicle based on the fault information and the target fault diagnosis mode includes: When the target fault diagnosis mode is the application message fault diagnosis model, the current application message of the battery management system is obtained; Extract the vehicle system parameters from the current application message; The vehicle's parameters are matched with a preset fault database, and the target battery swapping vehicle at the current moment is diagnosed based on the matching results, the fault diagnosis code, and the historical fault records.

7. A fault diagnosis device, characterized in that, The fault diagnosis device includes: The request module is used to send a fault diagnosis request to the target battery swapping vehicle and obtain the fault diagnosis response result fed back by the target battery swapping vehicle. The determination module is used to determine the target fault diagnosis mode based on the fault diagnosis response result; The acquisition module is used to acquire fault information of the type corresponding to the target fault diagnosis mode; The diagnostic module is used to perform fault diagnosis on the target battery swapping vehicle based on the fault information and the target fault diagnosis mode. The determining module is further configured to determine the fault diagnosis mode supported by the target battery swapping vehicle based on the fault diagnosis response result; The fault diagnosis modes include: unified fault diagnosis mode and application message fault diagnosis mode. The determining module is further configured to, when receiving a fault diagnosis response from the battery management system of the target battery swapping vehicle within a preset time period, determine that the fault diagnosis mode supported by the target battery swapping vehicle is a unified fault diagnosis mode and an application message fault diagnosis mode; and when not receiving a fault diagnosis response from the battery management system within a preset time period, determine that the fault diagnosis mode supported by the target battery swapping vehicle is an application message fault diagnosis model.

8. A fault diagnosis device, characterized in that, The fault diagnosis device includes a memory and a processor. The memory stores a fault diagnosis program that can run on the processor. The fault diagnosis program is configured to implement the fault diagnosis method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that, The storage medium stores a fault diagnosis program, which, when executed by a processor, implements the fault diagnosis method as described in any one of claims 1 to 6.

Images