Vehicle fault processing method and system, vehicle and storage medium

Abstract

The application discloses a vehicle fault processing method and system, a vehicle and a storage medium, wherein the method comprises the following steps: in response to a vehicle fault, acquiring a fault code; according to the fault code, reproducing the fault to obtain a fault scene, wherein the fault scene is a scene when the fault occurs; based on the fault scene, acquiring a connection state of a fault component, wherein the fault component is a component that fails in the fault scene; in response to the connection state not satisfying a preset condition, outputting a first prompt signal, and the first prompt signal is used for prompting a user that the connection of the fault component fails. The application solves the technical problem that in the prior art, the detection and processing of vehicle communication faults have the problems of low fault positioning and processing efficiency.

Description

Technical Field

[0001] This invention belongs to the field of vehicle technology, and more specifically, relates to a vehicle fault handling method, system, vehicle, and storage medium. Background Technology

[0002] With over 200 years of technological heritage, engineers of traditional energy vehicles have accumulated rich maintenance experience, providing a systematic and reliable approach to resolving real-world vehicle issues, resulting in high efficiency. However, with the rapid development and increasing market share of new energy vehicles, the methods for detecting and handling faults in these vehicles are crucial. Limited accumulated experience, the rapid development of new energy vehicles, and their high degree of electrification present significant challenges to the fault detection and repair of electric vehicles. Failure to improve the efficiency of fault localization and resolution for real-world electric vehicle faults will inevitably hinder the future promotion and application of electric vehicles.

[0003] In existing technologies, the detection and handling of vehicle faults suffer from low efficiency in fault location and processing. Summary of the Invention

[0004] This invention provides a vehicle fault handling method, system, vehicle, and storage medium to at least solve the technical problem of low fault location and processing efficiency in the detection and handling of vehicle communication faults in the prior art.

[0005] According to a first aspect of the present invention, a vehicle fault handling method is provided, applied to a vehicle, comprising: in response to a vehicle malfunction, acquiring a fault code; reproducing the fault based on the fault code to obtain a fault scenario, wherein the fault scenario is the scenario in which the fault occurs; acquiring the connection status of a faulty component based on the fault scenario, wherein the faulty component is the component that malfunctions in the fault scenario; and outputting a first prompt signal in response to the connection status not meeting a preset condition, the first prompt signal being used to prompt the user that the connection of the faulty component has failed.

[0006] Optionally, based on the fault code, reproducing the fault to obtain the fault scenario includes: determining the fault type based on the fault code; obtaining driver operation data, wherein the driver operation data is the driver's operation data before the vehicle malfunctions; and reproducing the fault to obtain the fault scenario based on the fault type and the driver operation data.

[0007] Optionally, the vehicle fault handling method also includes: deleting the fault code in response to the successful reproduction of the fault scenario.

[0008] Optionally, the vehicle fault handling method further includes: in response to the failure to reproduce the fault scenario, outputting a second prompt signal, wherein the second prompt signal is used to prompt the user to clean or reconnect the pins, connectors and wiring harnesses of the faulty component.

[0009] Optionally, the vehicle fault handling method further includes: in response to the connection status meeting preset conditions, outputting a third prompt signal, wherein the third prompt signal is used to prompt the user to repair or replace the faulty component.

[0010] Optionally, based on the fault scenario, obtaining the connection status of the faulty component includes: determining multiple pairs of interconnected pins under test based on the fault scenario; obtaining the resistance value between the interconnected pins under test for each pair of interconnected pins under test; and determining the connection status of the faulty component based on the resistance value and a preset critical resistance value.

[0011] Optionally, there can be multiple resistance values; determining the connection status of the faulty component based on the resistance values ​​and a preset critical resistance value includes: determining multiple comparison results based on multiple resistance values, wherein each resistance value is compared with its corresponding preset critical resistance value to obtain a comparison result; and determining the connection status of the faulty component based on multiple comparison results.

[0012] According to a second aspect of the present invention, a vehicle fault handling system is also provided, comprising:

[0013] The first acquisition module is used to acquire a fault code in response to a vehicle malfunction; the processing module is used to reproduce the malfunction based on the fault code to obtain a malfunction scenario, wherein the malfunction scenario is the scenario in which the malfunction occurs; the second acquisition module is used to acquire the connection status of the faulty component based on the malfunction scenario, wherein the faulty component is the part that malfunctions in the malfunction scenario; the output module is used to output a first prompt signal in response to the connection status not meeting a preset condition, wherein the first prompt signal is used to prompt the user that the connection of the faulty component has failed.

[0014] Optionally, the processing module is also used to: determine the fault type based on the fault code; obtain driver operation data, wherein the driver operation data is the driver's operation data before the vehicle malfunctions; and reproduce the fault scenario based on the fault type and the driver operation data.

[0015] Optionally, the processing module is also used to: delete the fault code in response to the successful reproduction of the fault scenario.

[0016] Optionally, the output module is also configured to: output a second prompt signal in response to a failure to reproduce the fault scenario, wherein the second prompt signal is used to prompt the user to clean or reconnect the pins, connectors and wiring harnesses of the faulty component.

[0017] Optionally, the output module is also used to: output a third prompt signal in response to the connection status meeting preset conditions, wherein the third prompt signal is used to prompt the user to repair or replace the faulty component.

[0018] Optionally, the second acquisition module is also used to: determine multiple pairs of interconnected pins under test based on the fault scenario; acquire the resistance value between the interconnected pins under test for each pair of interconnected pins under test; and determine the connection status of the faulty component based on the resistance value and a preset critical resistance value.

[0019] Optionally, there are multiple resistance values; the second acquisition module is also used to: determine multiple comparison results based on the multiple resistance values, wherein each resistance value is compared with its corresponding preset critical resistance value to obtain a comparison result; and determine the connection status of the faulty component based on the multiple comparison results.

[0020] According to a third aspect of the present invention, a vehicle is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the vehicle fault handling method described in any of the embodiments of the first aspect above.

[0021] According to a fourth aspect of the present invention, a non-volatile storage medium is also provided, wherein a computer program is stored in the non-volatile storage medium, and the computer program is configured to execute the vehicle fault handling method described in any of the embodiments of the first aspect when running on a computer or processor.

[0022] In this embodiment of the invention, in response to a vehicle malfunction, a fault code is obtained; based on the fault code, the malfunction is reproduced to obtain a fault scenario, wherein the fault scenario is the scene at which the malfunction occurs; based on the fault scenario, the connection status of the faulty component is obtained, wherein the faulty component is the part that malfunctioned in the fault scenario; in response to the connection status not meeting a preset condition, a first prompt signal is output, the first prompt signal being used to prompt the user that the connection of the faulty component has failed. This invention, by reproducing the vehicle malfunction and obtaining the connection status of the faulty component within the reproduced scenario, can efficiently and accurately locate the fault location, thereby solving the technical problem of low efficiency in fault location and processing in the detection and handling of vehicle communication faults in the prior art. Attached Figure Description

[0023] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0024] Figure 1 This is a flowchart of a vehicle fault handling method according to one embodiment of the present invention;

[0025] Figure 2 This is a schematic diagram of the communication model topology between the vehicle controller and the vehicle stability system controller in a vehicle according to one embodiment of the present invention;

[0026] Figure 3 This is a schematic diagram of the connection model topology between the vehicle controller and the low-voltage battery pack in a vehicle according to one embodiment of the present invention;

[0027] Figure 4 This is a structural block diagram of a vehicle fault handling system according to one embodiment of the present invention. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] According to an embodiment of the present invention, an embodiment of a vehicle fault handling method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system containing at least one set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0031] This method embodiment can also be executed in an electronic device including a memory and a processor, a similar control device, or in the cloud. Taking an electronic device as an example, the electronic device may include one or more processors and a memory for storing data. Optionally, the electronic device may also include a communication device for communication functions and a display device. Those skilled in the art will understand that the above structural description is merely illustrative and does not limit the structure of the electronic device. For example, the electronic device may include more or fewer components than described above, or have a different configuration than described above.

[0032] A processor may include one or more processing units. For example, a processor may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microcontroller unit (MCU), a field-programmable gate array (FPGA), a neural network processing unit (NPU), a tensor processing unit (TPU), or an artificial intelligence (AI) processor. Different processing units may be independent components or integrated into one or more processors. In some instances, electronic devices may also include one or more processors.

[0033] The memory can be used to store computer programs, such as the computer program corresponding to the vehicle fault handling method in this embodiment of the invention. The processor implements the vehicle fault handling method by running the computer program stored in the memory. The memory may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to electronic devices via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0034] The communication device is used to receive or send data via a network. Specific examples of the network mentioned above may include a wireless network provided by the mobile terminal's communication provider. In one example, the communication device includes a network interface controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the communication device may be a radio frequency (RF) module, used for wireless communication with the Internet. In some embodiments of this solution, the communication device is used to connect to mobile devices such as mobile phones and tablets, enabling the mobile device to send commands to the electronic device.

[0035] The display device can be a touchscreen liquid crystal display (LCD) or a touch display (also referred to as a "touchscreen" or "touch display screen"). The LCD allows a user to interact with the user interface of the electronic device. In some embodiments, the electronic device has a graphical user interface (GUI), which allows the user to interact with the GUI by touching a touch-sensitive surface with fingers and / or gestures. Executable instructions for performing these human-computer interaction functions are configured / stored in one or more processor-executable computer program products or readable storage media.

[0036] Figure 1 This is a flowchart of a vehicle fault handling method according to one embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0037] According to a first aspect of the present invention, a vehicle fault handling method is provided, applied to a vehicle, comprising:

[0038] Step S101: In response to a vehicle malfunction, obtain the fault code.

[0039] Specifically, when a vehicle malfunctions, it records the corresponding fault code. Therefore, the fault code can be retrieved directly from the vehicle's storage medium.

[0040] Step S102: Based on the fault code, reproduce the fault to obtain the fault scenario.

[0041] In step S102, the fault scenario is the scenario in which the fault occurred. When the fault disappears, it is inconvenient to troubleshoot and locate the fault. Therefore, based on the fault code, the fault that occurred in the vehicle before is reproduced to obtain the fault scenario corresponding to the fault code.

[0042] It should be noted that different faults correspond to specific fault codes.

[0043] Step S103: Based on the fault scenario, obtain the connection status of the faulty component.

[0044] In step S103, the faulty component is the part that malfunctions in the fault scenario. After reproducing the fault scenario, the connection status of the faulty component is obtained under the current fault scenario.

[0045] It should be noted that the connection status refers to the connection status between the various components in the faulty component.

[0046] Step S104: In response to the connection status not meeting the preset conditions, a first prompt signal is output.

[0047] In step S104, the first prompt signal is used to notify the user that the connection of the faulty component has failed. When the connection status is abnormal, it indicates that the connection status between at least two components in the faulty component is abnormal, and at this time, the first prompt signal is output to notify the user that the connection of the faulty component has failed.

[0048] It should be noted that the preset condition is that the connection status of all components in the faulty component is normal.

[0049] In some embodiments of the present invention, the first prompt signal is also used to indicate the connector or wiring harness in the faulty component that needs to be replaced or repaired, that is, to prompt the replacement or repair of the component with the abnormal connection.

[0050] In this embodiment of the invention, in response to a vehicle malfunction, a fault code is obtained; based on the fault code, the malfunction is reproduced to obtain a fault scenario, wherein the fault scenario is the scene at which the malfunction occurs; based on the fault scenario, the connection status of the faulty component is obtained, wherein the faulty component is the part that malfunctioned in the fault scenario; in response to the connection status not meeting a preset condition, a first prompt signal is output, the first prompt signal being used to prompt the user that the connection of the faulty component has failed. This invention, by reproducing the vehicle malfunction and obtaining the connection status of the faulty component within the reproduced scenario, can efficiently and accurately locate the fault location, thereby solving the technical problem of low efficiency in fault location and processing in the detection and handling of vehicle communication faults in the prior art.

[0051] Optionally, in step S102, reproducing the fault based on the fault code to obtain the fault scenario may include the following steps:

[0052] Step S1021: Determine the fault type based on the fault code.

[0053] Step S1022: Obtain driver operation data, wherein the driver operation data is the driver's operation data before the vehicle malfunctions.

[0054] Step S1023: Based on the fault type and driver operation data, reproduce the fault to obtain the fault scenario.

[0055] Understandably, when reproducing a fault, the first step is to determine the fault type based on the fault code. Then, the driver's operational data from a period prior to the vehicle malfunction is obtained. Finally, based on the fault type and the driver's operational data, the fault scenario is reproduced. Understandably, when the fault is successfully reproduced, the same fault code as described above will appear.

[0056] It should be noted that driver operation data is recorded and stored in the vehicle, and can be retrieved directly from the vehicle's storage devices.

[0057] Optionally, the vehicle fault handling method also includes: deleting the fault code in response to the successful reproduction of the fault scenario.

[0058] Specifically, after reproducing the fault scenario, the vehicle will store the fault code corresponding to the reproduced fault. This fault code will interfere with the subsequent vehicle maintenance. Therefore, the fault code needs to be deleted after the scenario is successfully reproduced.

[0059] Optionally, the vehicle fault handling method further includes: in response to the failure to reproduce the fault scenario, outputting a second prompt signal, wherein the second prompt signal is used to prompt the user to clean or reconnect the pins, connectors and wiring harnesses of the faulty component.

[0060] Specifically, when a fault scenario cannot be reproduced, the exact cause of the fault cannot be determined. Blindly attempting repairs or replacements in this situation could waste significant resources. Many electrical faults can only be detected when they occur. Therefore, if fault scenario reproduction fails, a second warning signal should be output, prompting the user to clean or reconnect the pins, connectors, and wiring harnesses of the faulty component.

[0061] It should be noted that when the fault scenario fails to be reproduced, the faulty component is identified through the fault code.

[0062] In some embodiments of the present invention, the second prompt signal is also used to prompt the user to clean and reconnect the battery electrodes.

[0063] Optionally, the vehicle fault handling method further includes: in response to the connection status meeting preset conditions, outputting a third prompt signal, wherein the third prompt signal is used to prompt the user to repair or replace the faulty component.

[0064] Specifically, when the connection status meets the preset conditions, it indicates that the connections of all components in the faulty component are normal. If the vehicle still malfunctions at this time, it is determined that the faulty component as a whole is malfunctioning. Therefore, a third prompt signal is output to prompt the user to repair or replace the faulty component.

[0065] Optionally, in step S103, obtaining the connection status of the faulty component based on the fault scenario may include the following steps:

[0066] Step S1031: Based on the fault scenario, determine multiple pairs of interconnected pins to be tested.

[0067] Step S1032: For each pair of interconnected pins under test, obtain the resistance value between the interconnected pins under test.

[0068] Step S1033: Determine the connection status of the faulty component based on the resistance value and the preset critical resistance value.

[0069] Reference Figure 2 For example, the fault scenario refers to a communication failure between the vehicle stability system controller and the vehicle controller. Figure 2 In the diagram, P1, P2, P3, P4, P5, and P6 are the communication pins for each controller. CAN_H refers to a high-level signal line, and CAN_L refers to a low-level signal line. When a fault occurs, the vehicle controller fails to receive messages from the vehicle stability system controller as expected. This communication failure may occur between the vehicle controller and the gateway, between the gateway and the vehicle stability system controller, or even within the vehicle controller, gateway, or vehicle stability system controller itself. Therefore, it is necessary to further determine the resistance values ​​between each pin. It should be noted that, in this example, the faulty components include the vehicle controller, gateway, and vehicle stability system controller. Refer to Table 1:

[0070] Table 1

[0071]

[0072]

[0073] Specifically, in Table 1, "Electricity" and "Ground" refer to the positive and negative terminals of the vehicle's low-voltage lead-acid battery, respectively. 1 ohm and 10 kiloohms are merely order-of-magnitude representations; any resistance value less than 1 ohm or greater than 10 kiloohms is acceptable. These two preset critical resistance values ​​are only for determining the connection relationship between the various test contacts. Less than 1 ohm indicates no open circuit between the two test contacts, and greater than 10 kiloohms indicates no short circuit between them. Only when each item from number 1 to 10 satisfies the corresponding logical relationship and resistance value can it be indicated that the connection status of the faulty component is normal; this is the condition that should be met when there is no fault.

[0074] Reference Figure 3 For example, the fault scenario pertains to a hardwired connection failure between the low-voltage battery pack and the vehicle controller. In this example, the faulty components include the vehicle controller, the hardwire, and the low-voltage battery pack. Refer to Table 2:

[0075] Table 2

[0076] 1 P39 - Low Voltage Management Relay ＜ 1Ω 2 P52 - Low Voltage Management Relay ＜ 1Ω 3 P1 - Vehicle body or battery negative terminal ＜ 1Ω 4 P2 - Vehicle body or battery negative terminal ＜ 1Ω 5 P26 - Vehicle body or battery negative terminal ＜ 1Ω 6 P54 - Vehicle body or battery negative terminal ＜ 1Ω

[0077] Specifically, the battery in the table refers to the vehicle's lead-acid low-voltage battery. In actual vehicles, the negative terminal of the battery is often short-circuited to the vehicle body. The low-voltage management relay in the table actually refers to the "low-voltage management relay power output terminal." This relay can power or de-power controllers such as the vehicle controller, and its output terminal is connected to the power input terminal of the low-voltage controller, including the vehicle controller. The preset critical resistance values ​​in the table are only order-of-magnitude representations; any value less than 1 ohm is sufficient to determine whether the pins are short-circuited. "P39 - Low-voltage management relay < "1 ohm" indicates that the resistance between pin P39 and the "low-voltage management relay power output terminal" is less than 1 ohm. In this case, it can be assumed that there is no open circuit between pin P39 and the "low-voltage management relay power output terminal," and they are short-circuited. This is a condition that should be met when there is no connection fault. "P1 - vehicle body or battery negative terminal < 1 ohm" indicates that the resistance between pin P1 and the battery negative terminal is less than 1 ohm. In this case, it can be approximately assumed that there is no open circuit between pin P1 and the battery negative terminal, and they are short-circuited. This is a condition that should be met when there is no fault. When all the logical relationships from 1 to 6 are met, the connection status of the faulty component is judged to be normal.

[0078] Optionally, in some embodiments of the present invention, there are multiple resistance values, each corresponding to a different pin. In step S1033, determining the connection state of the faulty component based on the resistance value and a preset critical resistance value may include the following steps:

[0079] Step S1033a: Based on multiple resistance values, determine multiple comparison results, wherein each resistance value is compared with its corresponding preset critical resistance value to obtain a comparison result.

[0080] Step S1033b: Determine the connection status of the faulty component based on multiple comparison results.

[0081] Specifically, referring to the description of step S1033 above, the multiple comparison results refer to the relationship between the resistance values ​​and critical resistance values ​​between the pins under test in Tables 1 and 2. For two different exemplary fault scenarios, when all the list items in Table 1 or Table 2 satisfy the logical relationship in the table, the connection status of the faulty component is determined to be normal; otherwise, the connection status of the faulty component is considered abnormal.

[0082] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to 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, in essence, 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 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.

[0083] This embodiment also provides a vehicle fault handling system for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" refers to a combination of software and / or hardware capable of performing a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0084] Figure 4 This is a structural block diagram of a vehicle fault handling system 200 according to one embodiment of the present invention, as shown below. Figure 4 As shown, taking a vehicle fault handling system 200 as an example, it includes: a first acquisition module 201, used to acquire a fault code in response to a vehicle fault; a processing module 202, used to reproduce the fault based on the fault code to obtain a fault scenario, wherein the fault scenario is the scenario when the fault occurs; a second acquisition module 203, used to acquire the connection status of a faulty component based on the fault scenario, wherein the faulty component is the part that malfunctions in the fault scenario; and an output module 204, used to output a first prompt signal in response to the connection status not meeting a preset condition, wherein the first prompt signal is used to prompt the user that the connection of the faulty component has failed.

[0085] Optionally, the processing module 202 is also used to: determine the fault type based on the fault code; obtain driver operation data, wherein the driver operation data is the driver's operation data before the vehicle malfunctions; and reproduce the fault scenario based on the fault type and the driver operation data.

[0086] Optionally, the processing module 202 is also used to: delete the fault code in response to the successful reproduction of the fault scenario.

[0087] Optionally, the output module 204 is further configured to: output a second prompt signal in response to a failure to reproduce the fault scenario, wherein the second prompt signal is used to prompt the user to clean or reconnect the pins, connectors and wiring harnesses of the faulty component.

[0088] Optionally, the output module 204 is also configured to: output a third prompt signal in response to the connection status meeting preset conditions, wherein the third prompt signal is used to prompt the user to repair or replace the faulty component.

[0089] Optionally, the second acquisition module 203 is further configured to: determine multiple pairs of interconnected pins to be tested based on the fault scenario; acquire the resistance value between the interconnected pins for each pair of interconnected pins to be tested; and determine the connection status of the faulty component based on the resistance value and a preset critical resistance value.

[0090] Optionally, there are multiple resistance values; the second acquisition module 203 is also used to: determine multiple comparison results based on the multiple resistance values, wherein each resistance value is compared with its corresponding preset critical resistance value to obtain a comparison result; and determine the connection status of the faulty component based on the multiple comparison results.

[0091] Embodiments of the present invention also provide a vehicle, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the vehicle fault handling method described in any of the above embodiments.

[0092] Optionally, in this embodiment, the processor in the vehicle can be configured to run a computer program to perform the following steps:

[0093] Step S101: In response to a vehicle malfunction, obtain the fault code.

[0094] Step S102: Based on the fault code, reproduce the fault to obtain the fault scenario.

[0095] Step S103: Based on the fault scenario, obtain the connection status of the faulty component.

[0096] Step S104: In response to the connection status not meeting the preset conditions, a first prompt signal is output.

[0097] The first prompt signal is used to alert the user that the connection of the faulty component has failed.

[0098] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0099] Embodiments of the present invention also provide a non-volatile storage medium storing a computer program, wherein the computer program is configured to execute the vehicle fault handling method described in any of the above embodiments when run on a computer or processor.

[0100] Optionally, in this embodiment, the computer program described above may be configured to store a computer program for performing the following steps:

[0101] Step S101: In response to a vehicle malfunction, obtain the fault code.

[0102] Step S102: Based on the fault code, reproduce the fault to obtain the fault scenario.

[0103] Step S103: Based on the fault scenario, obtain the connection status of the faulty component.

[0104] Step S104: In response to the connection status not meeting the preset conditions, a first prompt signal is output.

[0105] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0106] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0107] In the embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of modules can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through interfaces, or indirect couplings or communication connections between modules, and may be electrical or other forms.

[0108] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0109] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0110] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0111] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A vehicle fault handling method, characterized in that, Applied to vehicles, including: In response to a vehicle malfunction, obtain the fault code; Based on the fault code, the fault is reproduced to obtain the fault scenario, wherein the fault scenario is the scenario in which the fault occurred; In response to the fault scenario described, which targets a hard-wired connection fault between the low-voltage battery pack and the vehicle controller, multiple pairs of interconnected pins to be tested are identified. These pins include pin P39 - low-voltage management relay, pin P52 - low-voltage management relay, pin P1 - vehicle body or battery negative terminal, pin P2 - vehicle body or battery negative terminal, pin P26 - vehicle body or battery negative terminal, and pin P54 - vehicle body or battery negative terminal. For each pair of interconnected pins under test, obtain multiple resistance values ​​between the interconnected pins under test; Based on the multiple resistance values, multiple comparison results are determined, wherein each resistance value is compared with its corresponding preset critical resistance value to obtain a comparison result; Based on the multiple comparison results, the connection status of the faulty component is determined, wherein the faulty component is the part that fails in the fault scenario, and the faulty component includes the vehicle controller, hardwire, and low-voltage battery assembly; In response to the connection status not meeting the preset conditions, a first prompt signal is output, which is used to prompt the user that the connection of the faulty component has failed. In response to the connection status meeting the preset conditions, a third prompt signal is output, wherein the third prompt signal is used to prompt the user to repair or replace the faulty component.

2. The vehicle fault handling method according to claim 1, characterized in that, The step of reproducing the fault based on the fault code to obtain the fault scenario includes: Determine the fault type based on the fault code; Acquire driver operation data, wherein the driver operation data is the driver's operation data before the vehicle malfunction occurs; Based on the fault type and the driver's operation data, the fault is reproduced to obtain the fault scenario.

3. The vehicle fault handling method according to claim 2, characterized in that, Also includes: In response to the successful reproduction of the fault scenario, the fault code is deleted.

4. The vehicle fault handling method according to claim 1, characterized in that, Also includes: In response to the failure to reproduce the fault scenario, a second prompt signal is output, wherein the second prompt signal is used to prompt the user to clean or reconnect the pins, connectors and wiring harnesses of the faulty component.

5. A vehicle fault handling system, characterized in that, include: The first acquisition module is used to acquire fault codes in response to a vehicle malfunction. The processing module is used to reproduce the fault based on the fault code to obtain a fault scenario, wherein the fault scenario is the scenario in which the fault occurs; The second acquisition module is used to respond to the fault scenario, which involves a hardwire connection fault between the low-voltage battery pack and the vehicle controller, by identifying multiple pairs of interconnected pins to be tested. These pins include pin P39 (low-voltage management relay), pin P52 (low-voltage management relay), pin P1 (vehicle body or battery negative terminal), pin P2 (vehicle body or battery negative terminal), pin P26 (vehicle body or battery negative terminal), and pin P54 (vehicle body or battery negative terminal). For each pair of interconnected pins to be tested, multiple resistance values ​​are acquired between the interconnected pins. Based on these resistance values, multiple comparison results are determined, where each resistance value is compared with its corresponding preset critical resistance value to obtain a comparison result. Based on these comparison results, the connection status of the faulty component is determined. The faulty component is the part that malfunctions in the fault scenario, and the faulty component includes the vehicle controller, the hardwire, and the low-voltage battery pack. The output module is configured to output a first prompt signal in response to the connection status not meeting the preset conditions. The first prompt signal is used to prompt the user that the connection of the faulty component has failed. The system is also configured to output a third prompt signal in response to the connection state meeting the preset conditions, wherein the third prompt signal is used to prompt the user to repair or replace the faulty component.

6. A vehicle comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the vehicle fault handling method as described in any one of claims 1 to 4.

7. A non-volatile storage medium, characterized in that, The non-volatile storage medium stores a computer program, wherein the computer program is configured to execute the vehicle fault handling method as described in any one of claims 1 to 4 when run on a computer or processor.

Images