Vehicle fault reason determination method and device, equipment and storage medium

Abstract

The invention relates to a vehicle fault reason determination method and device, equipment and a storage medium, and relates to the technical field of automobiles. The method comprises the steps of obtaining fault data information of a target fault in response to a fault data recording instruction under the condition that the vehicle has the target fault; sending the fault data information of the target fault to a cloud server; and receiving the fault reason of the target fault sent by the cloud server, and displaying the fault reason on the vehicle. Therefore, when the vehicle has the fault with the undefined fault code, the fault data information of the fault is acquired in response to the fault data recording instruction, so that the fault reason of the fault is remotely analyzed based on the fault data information, and the problem that the fault data cannot be acquired when the vehicle fault with the undefined fault code is remotely diagnosed, and the fault data cannot be acquired is solved. And the vehicle fault can only be analyzed according to the fault data in the approximate time range.

Description

Technical Field

[0001] The present invention relates to the technical field of automobiles, and particularly relates to a method, device, equipment and storage medium for determining the cause of vehicle faults. Background Art

[0002] With the increasing degree of intelligent networking of new energy vehicles, when a vehicle breaks down, most of the vehicle's faults can be solved through remote diagnosis and over-the-air technology (OTA). Users do not need to perform offline maintenance, which greatly saves the user's time cost and improves the user's driving experience. Currently, when remotely determining the cause of a vehicle fault (i.e., remotely diagnosing a vehicle fault), the vehicle-end controller can report a diagnostic trouble code (DTC) to the telematics BOX (T-BOX). When the T-BOX receives the fault code, it intercepts the fault data (i.e., vehicle driving data) at the moment when the fault code is generated and uploads the fault data to the cloud. Further, after-sales personnel can download the fault data from the cloud and analyze the fault data to locate the cause of the vehicle fault and formulate measures to solve the fault.

[0003] However, in the above method, when remotely determining the cause of a vehicle fault, the fault code is predefined and cannot cover all vehicle faults. When a fault with an undefined fault code occurs, the fault code cannot be reported, and thus the fault occurrence time and the fault data at the fault occurrence time cannot be determined. Only the approximate time range when the fault occurs can be confirmed by communicating with the user, and the vehicle fault can be remotely diagnosed based on the fault data within the approximate time range. Therefore, the efficiency and accuracy of remotely determining the cause of a vehicle fault are relatively poor. Summary of the Invention

[0004] The purpose of the present invention is to provide a method, device, equipment and storage medium for determining the cause of vehicle faults, so as to solve the technical problem that when remotely determining the cause of a vehicle fault, it is impossible to obtain fault data when a vehicle fault with an undefined fault code occurs, and the vehicle fault can only be remotely diagnosed based on the fault data within the approximate time range. The technical solution of the present application is as follows:

[0005] According to a first aspect of the present application, there is provided a method for determining the cause of a vehicle fault, which is applied to a vehicle and includes: when the vehicle has a target fault, in response to a fault data recording instruction, obtaining the fault data information of the target fault, where the target fault is a fault with an undefined Diagnostic Trouble Code (DTC), and the fault data information is the parameter information during the operation of the vehicle; sending the fault data information of the target fault to a cloud server, where the cloud server is used to determine the cause of the target fault generated by the vehicle based on the fault data information; receiving the cause of the target fault sent by the cloud server and displaying it on the vehicle.

[0006] According to the above technical means, when the vehicle has a fault with an undefined fault code, the present application can, in response to a fault data recording instruction, obtain the fault data information of the fault, so as to analyze the cause of the fault based on the fault data information and send the cause of the fault to the vehicle for display. That is, when a fault with an undefined fault code occurs, the fault data information at the moment of the fault can be accurately obtained, and the exact cause of the fault can be analyzed based on the fault data information. Thus, it avoids the technical problem in the prior art that when a fault with an undefined fault code occurs, the fault data at the moment of the fault cannot be obtained, and the vehicle fault can only be remotely diagnosed based on the fault data within a rough time range, improving the efficiency and accuracy of remotely determining the cause of the vehicle fault.

[0007] In a possible implementation manner, the method further includes: in response to a fault data recording instruction, generating a target fault code and a target timestamp; sending the target fault code to the cloud server, where the target fault code is used for the cloud server to obtain the fault data information from the vehicle; obtaining the fault data information of the target fault, including: determining a target time period based on the target timestamp and obtaining the fault data information within the target time period.

[0008] According to the above technical means, the present application can, in response to a fault data recording instruction, generate a target fault code and a target timestamp, so as to determine a target time period based on the target timestamp and obtain the fault data information within the target time period. That is, it can record the exact moment when the fault occurs and obtain the fault data information within the time period corresponding to that moment, improving the accuracy of obtaining the fault data information. Obtaining the fault data information from the vehicle based on the target fault code for fault cause analysis improves the efficiency of analyzing the fault cause.

[0009] In a possible implementation manner, sending the fault data information of the target fault to the cloud server includes: receiving a fault data information acquisition instruction sent by the cloud server; based on the fault data information acquisition instruction, sending the fault data information of the target fault to the cloud server.

[0010] According to the above technical means, the present application can issue a fault data information acquisition instruction through the cloud server to obtain the fault data information of the fault, which facilitates the subsequent analysis of the fault data information by the cloud server and improves the efficiency of analyzing the cause of the fault.

[0011] In a possible implementation manner, the method further includes: obtaining target description information, where the target description information is used to indicate the vehicle state information when a target fault occurs; sending the target description information to the cloud server, and the target description information is used for the cloud server to determine the cause of the target fault generated by the vehicle.

[0012] According to the above technical means, the present application can obtain information describing the vehicle state when a fault occurs, which facilitates the subsequent analysis of the cause of the target fault generated by the vehicle based on the information describing the vehicle state, and improves the accuracy of analyzing the cause of the fault.

[0013] According to a second aspect of the present application, there is provided a method for determining the cause of a vehicle fault, which is applied to a cloud server and includes: receiving the fault data information of a target fault sent by the vehicle, where the target fault is a fault with an undefined diagnostic trouble code (DTC), and the fault data information is parameter information during vehicle operation; determining the cause of the target fault generated by the vehicle based on the fault data information; and sending the cause of the target fault to the vehicle.

[0014] According to the above technical means, the present application can determine the cause of the fault generated by the vehicle through the cloud server based on the fault data information of the fault with an undefined diagnostic trouble code sent by the vehicle. That is, when a fault with an undefined diagnostic trouble code occurs in the vehicle, remote diagnosis of the fault can be achieved through the cloud server.

[0015] In a possible implementation manner, the method further includes: receiving a target diagnostic trouble code sent by the vehicle; and sending a fault data information acquisition instruction to the vehicle based on the target diagnostic trouble code, where the fault data information acquisition instruction is used to obtain the fault data information.

[0016] According to the above technical means, the present application can receive the target diagnostic trouble code sent by the vehicle through the cloud server and send a fault data information acquisition instruction to the vehicle based on the target diagnostic trouble code to obtain the fault data information corresponding to the target diagnostic trouble code, so as to quickly obtain the corresponding fault data information according to the diagnostic trouble code, which facilitates the subsequent analysis of the fault data information and improves the efficiency of remote diagnosis of the fault.

[0017] In a possible implementation manner, the method further includes: receiving target description information sent by the vehicle, where the target description information is used to indicate the vehicle state information when a target fault occurs; determining the cause of the target fault generated by the vehicle based on the fault data information, including: determining the cause of the target fault generated by the vehicle based on the fault data information and the target description information.

[0018] According to the above technical means, the present application can obtain information describing the vehicle state when a failure occurs, facilitating subsequent analysis of the cause of the target failure of the vehicle based on the information describing the vehicle state and the failure data information, and improving the accuracy of analyzing the cause of the failure.

[0019] According to the third aspect provided by the present application, a vehicle failure cause determination device is provided, which is applied to a vehicle. The vehicle failure cause determination device includes a transmission module and a processing module; the transmission module is configured to, when a target failure occurs in the vehicle, in response to a failure data recording instruction, obtain the failure data information of the target failure, where the target failure is a failure for which the diagnostic trouble code (DTC) is not defined, and the failure data information is parameter information during vehicle operation; the transmission module is further configured to send the failure data information of the target failure to a cloud server, and the cloud server is configured to determine the cause of the target failure of the vehicle based on the failure data information; the transmission module is further configured to receive the cause of the target failure sent by the cloud server; the processing module is configured to display the cause of the target failure on the vehicle.

[0020] In a possible implementation manner, the vehicle failure cause determination device further includes a determination module; the processing module is further configured to, in response to a failure data recording instruction, generate a target failure code and a target timestamp; the transmission module is further configured to send the target failure code to the cloud server, and the target failure code is used for the cloud server to obtain the failure data information from the vehicle; the determination module is configured to determine a target time period based on the target timestamp; the transmission module is further configured to obtain the failure data information within the target time period.

[0021] In a possible implementation manner, the transmission module is further configured to receive a failure data information acquisition instruction sent by the cloud server; the transmission module is further configured to, based on the failure data information acquisition instruction, send the failure data information of the target failure to the cloud server.

[0022] In a possible implementation manner, the transmission module is further configured to obtain target description information, where the target description information is used to indicate the vehicle state information when the target failure occurs; the transmission module is further configured to send the target description information to the cloud server, and the target description information is used for the cloud server to determine the cause of the target failure of the vehicle.

[0023] According to a fourth aspect provided by the present application, a vehicle fault cause determination device is provided, which is applied to a cloud server. The vehicle fault cause determination device includes a transmission module and a determination module; the transmission module is configured to receive fault data information of a target fault sent by the vehicle, the target fault is a fault for which the diagnostic trouble code (DTC) is undefined, and the fault data information is parameter information during vehicle operation; the determination module is configured to determine the fault cause of the vehicle generating the target fault based on the fault data information; the transmission module is further configured to send the fault cause of the target fault to the vehicle.

[0024] In a possible implementation manner, the transmission module is further configured to receive a target fault code sent by the vehicle; the transmission module is further configured to send a fault data information acquisition instruction to the vehicle based on the target fault code, and the fault data information acquisition instruction is used to acquire the fault data information.

[0025] In a possible implementation manner, the transmission module is further configured to receive target description information sent by the vehicle, and the target description information is used to indicate the vehicle state information when the target fault occurs; the determination module is further configured to determine the fault cause of the vehicle generating the target fault based on the fault data information and the target description information.

[0026] According to a fifth aspect provided by the present application, an electronic device is provided, including: a processor; a memory for storing instructions executable by the processor; wherein, the processor is configured to execute the instructions to implement the method according to the first aspect or the second aspect and any possible implementation manner thereof.

[0027] According to a sixth aspect provided by the present application, a computer-readable storage medium is provided. When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is enabled to execute the method according to the first aspect or the second aspect and any possible implementation manner thereof.

[0028] According to a seventh aspect provided by the present application, a vehicle is provided, including: a vehicle fault cause determination device for implementing the method according to the first aspect or the second aspect and any possible implementation manner thereof.

[0029] According to an eighth aspect provided by the present application, a computer program product is provided. The computer program product includes computer instructions, and when the computer instructions run on the electronic device, the electronic device is enabled to execute the method according to the first aspect or the second aspect and any possible implementation manner thereof.

[0030] Therefore, the above technical features of the present application have the following beneficial effects:

[0031] (1) When a vehicle has a fault with an undefined fault code, in response to a fault data recording instruction, the fault data information of the fault can be obtained to analyze the cause of the fault based on the fault data information and send the cause of the fault to the vehicle for display. That is, when a fault with an undefined fault code occurs, the fault data information at the moment of the fault can be accurately obtained to analyze the exact cause of the fault according to the fault data information. Thus, it avoids the technical problem in the prior art that when a fault with an undefined fault code occurs, the fault data at the moment of the fault cannot be obtained, and the vehicle fault can only be remotely diagnosed based on the fault data within a general time range, improving the efficiency and accuracy of remotely determining the cause of the vehicle fault.

[0032] (2) In response to a fault data recording instruction, a target fault code and a target timestamp can be generated to determine a target time period based on the target timestamp and obtain the fault data information within the target time period. That is, the exact moment when the fault occurs can be recorded, and the fault data information within the corresponding time period of that moment can be obtained, improving the accuracy of obtaining the fault data information. Analyzing the cause of the fault based on the target fault code by obtaining the fault data information from the vehicle improves the efficiency of analyzing the cause of the fault.

[0033] (3) A fault data information acquisition instruction can be sent down by the cloud server to obtain the fault data information of the fault, facilitating subsequent analysis of the fault data information by the cloud server and improving the efficiency of analyzing the cause of the fault.

[0034] (4) Information describing the vehicle state can be obtained when a fault occurs, facilitating subsequent analysis of the cause of the target fault of the vehicle based on the information describing the vehicle state and improving the accuracy of analyzing the cause of the fault.

[0035] (5) According to the fault data information of the fault with an undefined fault code sent by the vehicle, the cause of the fault of the vehicle can be determined by the cloud server. That is, when a vehicle has a fault with an undefined fault code, remote diagnosis of the fault can be realized through the cloud server.

[0036] (6) The cloud server can receive the target fault code sent by the vehicle and send a fault data information acquisition instruction to the vehicle based on the target fault code to obtain the fault data information corresponding to the target fault code, realizing rapid acquisition of the corresponding fault data information according to the fault code, facilitating subsequent analysis of the fault data information, and improving the efficiency of remotely diagnosing the fault.

[0037] (7) Information describing the vehicle state can be obtained when a fault occurs, facilitating subsequent analysis of the cause of the target fault of the vehicle based on the information describing the vehicle state and the fault data information, and improving the accuracy of analyzing the cause of the fault.

[0038] It should be noted that for the technical effects brought by any one of the third to eighth aspects, reference can be made to the technical effects brought by the corresponding implementation manners in the first or second aspect, which will not be elaborated herein.

[0039] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and should not limit this application. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with this application, and are used together with the specification to explain the principles of this application, and do not constitute an improper limitation to this application.

[0041] Figure 1 is a schematic structural diagram of a vehicle fault cause determination system shown according to an exemplary embodiment;

[0042] Figure 2 is a flowchart of a vehicle fault cause determination method shown according to an exemplary embodiment;

[0043] Figure 3 is a schematic diagram of a steering wheel button shown according to an exemplary embodiment;

[0044] Figure 4 is a flowchart of another vehicle fault cause determination method shown according to an exemplary embodiment;

[0045] Figure 5 is a flowchart of another vehicle fault cause determination method shown according to an exemplary embodiment;

[0046] Figure 6 is a flowchart of another vehicle fault cause determination method shown according to an exemplary embodiment;

[0047] Figure 7 is a flowchart of another vehicle fault cause determination method shown according to an exemplary embodiment;

[0048] Figure 8 is a flowchart of another vehicle fault cause determination method shown according to an exemplary embodiment;

[0049] Figure 9 is a flowchart of another vehicle fault cause determination method shown according to an exemplary embodiment;

[0050] Figure 10 is a schematic flowchart of remote diagnosis using a user-defined fault code shown according to an exemplary embodiment;

[0051] Figure 11It is a block diagram of a vehicle fault cause determination device shown according to an exemplary embodiment;

[0052] Figure 12 It is a block diagram of another vehicle fault cause determination device shown according to an exemplary embodiment;

[0053] Figure 13 It is a block diagram of an electronic device shown according to an exemplary embodiment. Detailed implementation manners

[0054] The following will describe the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific implementation manners. Various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for explaining the present invention, rather than for limiting the protection scope of the present invention.

[0055] It should be noted that the diagrams provided in the following embodiments only illustrate the basic concept of the present invention in a schematic manner. Therefore, only the components related to the present invention are shown in the diagrams, rather than being drawn according to the number, shape, and size of the components in actual implementation. The type, quantity, and ratio of each component in actual implementation can be arbitrarily changed, and the component layout type may also be more complex.

[0056] As the intelligent networking level of new energy vehicles is getting higher and higher, when a vehicle breaks down, most of the vehicle's faults can be solved through remote diagnosis and OTA. Users do not need to perform offline maintenance, which greatly saves the user's time cost and improves the user's vehicle use experience. Currently, when remotely diagnosing vehicle faults, the DTC can be reported from the vehicle end controller to the T-BOX. Further, when the T-BOX receives the DTC, the fault data at the moment when the fault code is generated is intercepted and uploaded to the cloud. Then, after-sales personnel can download the fault data from the cloud and analyze the fault data to locate the fault cause of the vehicle and formulate measures to solve the fault.

[0057] However, in the above method, the DTC is predefined by vehicle manufacturers when formulating vehicle diagnosis schemes. However, the predefined DTC cannot cover all possible faults of the vehicle and cannot cover the experience problems of users' vehicle use. Therefore, when users feedback vehicle faults for which fault codes are not defined, the fault codes cannot be reported, and thus it is impossible to accurately locate the occurrence time of the fault and obtain the fault data at the moment when the fault occurs. It is only possible to communicate with the user to confirm the approximate time range when the fault occurs, and remotely diagnose the vehicle fault based on the fault data within the approximate time range.

[0058] Moreover, if the time interval between the moment when the user reports the fault and the moment when the fault occurs is too long, the fault data at the time of the fault occurrence in the T-BOX will be overwritten. At this time, only the relatively sparse fault data defined by national standards, enterprise standards, etc. can be used to analyze the vehicle fault. If the national and enterprise standard data do not support the analysis of the cause of the vehicle fault, then only by communicating with the user to confirm the operation behavior at the time of the fault occurrence and trying to reproduce the fault can the vehicle fault be diagnosed. In summary, how to set a strategy to obtain the precise time point when the user reports the fault and upload the fault data at this time point to the cloud for after-sales personnel to analyze is an urgent problem to be solved.

[0059] In view of the above technical problems, the embodiments of the present disclosure provide a method for determining the cause of a vehicle fault. The idea is that when a vehicle fault not covered by traditional fault codes occurs, a user-defined fault code is generated by a user's manual trigger, the precise time point when the fault problem occurs and the fault data segment at this time point are obtained, the fault data of the user-defined fault code is recorded, and the recorded fault data is uploaded to a cloud server for after-sales personnel to perform fault analysis.

[0060] For ease of understanding, the following specifically introduces the method for determining the cause of a vehicle fault provided in this application with reference to the accompanying drawings.

[0061] A method for determining the cause of a vehicle fault provided in an embodiment of this application can be applied to a system for determining the cause of a vehicle fault. Figure 1 It is a schematic structural diagram of a system for determining the cause of a vehicle fault shown according to an exemplary embodiment. As Figure 1 shown, the vehicle fault cause determination system 10 includes: a vehicle 11 and a cloud server 12. The vehicle 11 specifically includes: a steering wheel custom button 111, a vehicle head unit 112, and a telematics control unit 113.

[0062] Among them, the vehicle 11 is used to obtain the fault data information of the target fault in response to a fault data recording instruction, send the fault data information of the target fault to the cloud server 12, and display the cause of the target fault sent by the cloud server 12; the cloud server 12 is used to determine the cause of the target fault generated by the vehicle 11 based on the fault data information sent by the vehicle 11 and send the cause of the target fault to the vehicle 11, so as to determine the cause of the vehicle fault based on the vehicle 11 and the cloud server 12.

[0063] The custom steering wheel button 111 is used to generate a fault data recording instruction; the head unit (HU) 112 is used to set the custom steering wheel button 111 as a manual trigger condition, and in response to the fault data recording instruction generated by the custom steering wheel button 111, obtain the fault data information of the target fault from the telematics unit 113 and send the fault data information of the target fault to the cloud server 12; the telematics unit 113 is used to store the fault data information of the target fault.

[0064] Figure 2 FIG. is a flowchart of a method for determining the cause of a vehicle fault shown according to an exemplary embodiment, which is applied to a vehicle, such as Figure 2 shown, and the method for determining the cause of the vehicle fault includes the following steps:

[0065] S201. In the case where a target fault occurs in the vehicle, in response to the fault data recording instruction.

[0066] S202. Obtain the fault data information of the target fault through the vehicle.

[0067] Wherein, the target fault is a fault for which the diagnostic trouble code (DTC) is not defined, and the fault data information is parameter information during vehicle operation.

[0068] Optionally, the user can preset on the head unit that the trigger condition for recording the fault data corresponding to the fault for which the fault code is not defined is the custom steering wheel button.

[0069] Exemplarily, the target fault can be insufficient driving power or a certain vehicle function cannot be used. The trigger condition for recording the fault data can be voice keyword matching of the vehicle, the custom steering wheel button, or gesture recognition. Figure 3 FIG. is a schematic diagram of a steering wheel button shown according to an exemplary embodiment, such as Figure 3 shown, when the trigger condition for recording the fault data is the custom steering wheel button, the short press of button 1 in the steering wheel buttons can be used as the trigger condition for recording the fault data.

[0070] During vehicle use, when the user discovers that a target fault has occurred in the vehicle (that is, the user feels that the vehicle is abnormal), the user can short press button 1 on the steering wheel to trigger button 1 on the steering wheel to generate a fault data recording instruction, and the head unit responds to the fault data recording instruction to obtain the fault data information of the target fault. Then, the fault data information of the target fault is stored in the T-BOX.

[0071] Exemplarily, the parameter information during vehicle operation can include: driving distance, driving speed, state-of-charge (SOC), and remaining fuel.

[0072] S203. Send the fault data information of the target fault to the cloud server through the vehicle.

[0073] Among them, the cloud server is used to determine the cause of the target fault generated by the vehicle based on the fault data information.

[0074] Optionally, when the after-sales personnel need to download the fault data information of the target fault, the fault data information of the target fault can be sent to the cloud server through the in-vehicle unit.

[0075] S204. Receive the cause of the target fault sent by the cloud server through the vehicle and display it on the vehicle.

[0076] Optionally, after the upload of the fault data information of the target fault is completed, the after-sales personnel can download the fault data information of the target fault through the cloud server, analyze the fault data information, fill in the cause of the target fault and the corresponding solution measures. Further, the cause of the target fault and the corresponding solution measures are sent to the in-vehicle unit through the cloud server by invoking the push interface and displayed on the in-vehicle unit.

[0077] Optionally, the push interface can be invoked through the cloud server, and the cause of the target fault and the corresponding solution measures are sent to the user's mobile APP through the message push of the mobile application (APP). Further, the user can view the cause of the fault and the corresponding solution measures on the mobile APP.

[0078] Figure 4 It is a flowchart of another method for determining the cause of a vehicle fault shown according to an exemplary embodiment. As Figure 4 shown, the method further includes steps S301 - S302, and the method in the above step S202 specifically includes step S303:

[0079] S301. In response to the fault data recording instruction, generate a target fault code and a target timestamp through the vehicle.

[0080] Optionally, when responding to the fault data recording instruction through the in-vehicle unit, a target fault code (i.e., UD_DTC) and a target timestamp (i.e., TS) can be generated through the in-vehicle unit.

[0081] S302. Send the target fault code to the cloud server through the vehicle.

[0082] Among them, the target fault code is used for the cloud server to obtain the fault data information from the vehicle.

[0083] Optionally, after the vehicle computer generates the target fault code and the target timestamp, a pop-up window can be popped up by the vehicle computer. The user can fill in the vehicle status information (i.e., the target description information, DESC) when the target fault occurs in the pop-up window popped up by the vehicle computer, and select the time length for intercepting the fault data segment (i.e., the length of the target time period, TIME_INTERVAL).

[0084] Further, when the user clicks the "OK" button after filling in, it triggers the vehicle computer to call the interface of the cloud server. Through the interface of the cloud server, the vehicle identification number (VIN), UD_DTC, TS, TIME_INTERVAL, and DESC of the vehicle are uploaded to the cloud server, and a record of the user-defined fault code of the vehicle is generated by the cloud server based on VIN, UD_DTC, TS, TIME_INTERVAL, and DESC.

[0085] S303. Based on the target timestamp, determine the target time period through the vehicle, and obtain the fault data information within the target time period.

[0086] Optionally, based on the controller area network (CAN), the vehicle computer forwards the UD_DTC, TS, and TIME_INTERVAL of the vehicle to the T-BOX. Further, through the T-BOX, the fault data before and after TS and within the TIME_INTERVAL is intercepted from the historical fault data, and a separate fault data segment (i.e., the fault data information) is generated and named UD_DTC, and stored in the T-BOX.

[0087] Figure 5 It is a flowchart of another method for determining the cause of vehicle faults shown in an exemplary embodiment, as Figure 5 shown. The method in the above step S203 specifically includes the following steps:

[0088] S401. Receive a fault data information acquisition instruction sent by the cloud server through the vehicle.

[0089] Optionally, when the assigned after-sales personnel view the record of the user-defined fault code of the vehicle through the cloud server, they can apply to download the fault data information of the fault code on the page of the cloud server. At this time, the cloud server can send a fault data information acquisition instruction carrying the VIN and UD_DTC of the vehicle to the T-BOX.

[0090] S402. Based on the fault data information acquisition instruction, send the fault data information of the target fault to the cloud server through the vehicle.

[0091] Optionally, after the T-BOX receives the fault data information acquisition instruction carrying the VIN and UD_DTC of the vehicle, based on the VIN and UD_DTC of the vehicle, it acquires the fault data information of the target fault named after UD_DTC, and sends the fault data information of the target fault to the cloud server.

[0092] It should be noted that the fault data information acquisition instruction sent by the cloud server needs to support the T-BOX wake-up function. Specifically, after the fault data information acquisition instruction is sent to the T-BOX, first judge the communication status of the T-BOX. If the current T-BOX is in the sleep state, control to wake up the T-BOX and upload the fault data information. After the fault data information is uploaded, control the T-BOX to enter the sleep state again; if the current T-BOX is in the wake-up state, the fault data information can be directly uploaded.

[0093] Figure 6 is a flowchart of another method for determining the cause of a vehicle fault shown according to an exemplary embodiment, as Figure 6 shown, before the above step S202, the method further includes the following steps:

[0094] S501. Obtain target description information through the vehicle.

[0095] Among them, the target description information is used to indicate the vehicle status information when the target fault occurs.

[0096] Optionally, the user can briefly fill in the vehicle status information when the target fault occurs in the pop-up window on the in-vehicle computer.

[0097] S502. Send the target description information to the cloud server through the vehicle.

[0098] Among them, the target description information is used by the cloud server to determine the cause of the target fault of the vehicle.

[0099] Optionally, by calling the interface of the cloud server through the in-vehicle computer, the target description information is sent to the cloud server.

[0100] Figure 7 is a flowchart of another method for determining the cause of a vehicle fault shown according to an exemplary embodiment, applied to the cloud server, as Figure 7 shown, the method includes the following steps:

[0101] S601. Receive the fault data information of the target fault sent by the vehicle through the cloud server.

[0102] Among them, the target fault is a fault with an undefined fault code DTC, and the fault data information is the parameter information during vehicle operation.

[0103] Optionally, receive the fault data information of the target fault obtained from the T-BOX through the cloud server.

[0104] S602. Based on the fault data information, determine the fault cause of the vehicle generating the target fault through the cloud server.

[0105] Optionally, after-sales personnel can download the fault data information and analyze the fault cause of the target fault and the corresponding solutions. Further, fill in the fault cause of the target fault and the corresponding solutions on the page of the cloud server, and update the record of the user-defined fault code of the vehicle in the cloud server based on the fault cause of the target fault and the corresponding solutions through the cloud server.

[0106] S603. Send the fault cause of the target fault to the vehicle through the cloud server.

[0107] Optionally, send the fault cause of the target fault and the corresponding solutions to the in-vehicle unit through the cloud server and display them on the in-vehicle unit.

[0108] Figure 8 is a flowchart of another method for determining the vehicle fault cause shown according to an exemplary embodiment. As Figure 8 shown, before the above step S601, the method further includes the following steps:

[0109] S701. Receive the target fault code sent by the vehicle through the cloud server.

[0110] Optionally, the target fault code sent by the in-vehicle unit through the interface of the cloud server can be received through the cloud server.

[0111] S702. Based on the target fault code, send a fault data information acquisition instruction to the vehicle through the cloud server.

[0112] Among them, the fault data information acquisition instruction is used to acquire the fault data information.

[0113] Optionally, based on the target fault code, a fault data information acquisition instruction can be sent to the T-BOX through the cloud server.

[0114] Figure 9 is a flowchart of another method for determining the vehicle fault cause shown according to an exemplary embodiment. As Figure 9 shown, before the above step S601, the method further includes step S801, and the method in the above step S602 specifically includes step S802:

[0115] S801. Receive the target description information sent by the vehicle through the cloud server.

[0116] Among them, the target description information is used to indicate the vehicle state information when a target fault occurs.

[0117] Optionally, the target description information sent by the vehicle head unit through the interface for retrieving the cloud server is received through the cloud server.

[0118] S802. Based on the fault data information and the target description information, determine the fault cause of the vehicle generating the target fault through the cloud server.

[0119] Optionally, the after-sales personnel can analyze the fault data information and the target description information, determine the fault cause of the vehicle generating the target fault and formulate corresponding solutions, and fill in the fault cause of generating the target fault and formulate corresponding solutions on the page of the cloud server.

[0120] Figure 10 It is a schematic flowchart of remote diagnosis using a user-defined fault code shown according to an exemplary embodiment, as Figure 10 shown. The user sets a preset button on the steering wheel as the trigger condition for recording fault data. When the user discovers that the vehicle has a fault, press the preset button to trigger the recording of fault data. Further, a user-defined fault code and a trigger timestamp are generated by the vehicle head unit, and a pop-up window appears. The user fills in the description information of the vehicle fault, selects the length of the fault data to be intercepted in the pop-up window, and retrieves the cloud server interface through the vehicle head unit to upload the vehicle identification code, user-defined fault code, trigger timestamp, description information of the vehicle fault, and the length of the intercepted fault data to the cloud server, and a record of the user-defined fault code is generated on the cloud server. Then, the user-defined fault code, trigger timestamp, and the length of the intercepted fault data are forwarded to the remote information processor through the vehicle head unit, and the fault data is intercepted through the remote information processor.

[0121] After the assigned after-sales personnel view the record of the user-defined fault code, the after-sales personnel can apply to download the fault data and issue a fault data upload instruction to the remote information processor. Further, the fault data named with the user-defined fault code can be uploaded to the cloud server through the remote information processor. After the cloud server receives the fault data, the after-sales personnel download the fault data and analyze it, and fill in the fault cause and the corresponding solution. Then, the fault cause and the corresponding solution are received through the cloud server, and the record of this user-defined fault code is updated, and the fault cause and the corresponding solution are pushed to the user's mobile APP. In this way, the user can view the fault feedback result on the mobile APP.

[0122] The embodiment of the present application provides a method for determining the cause of vehicle faults. Without increasing the hardware cost of the vehicle, the present application can generate user-defined fault codes for vehicle fault problems not covered by traditional fault codes. Specifically, the accurate time point when the fault problem is found and the fault data segment at this time point can be obtained by means of manual triggering by the user, the fault data of the user-defined fault code can be recorded, and the recorded fault data can be uploaded to the cloud server for after-sales personnel to conduct fault analysis. The present application can effectively reduce the cost and working hours of remote diagnosis and improve the efficiency of remote diagnosis for problems without fault code reporting.

[0123] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. To implement the above functions, the vehicle fault cause determination device or electronic device includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0124] The embodiment of the present application can, according to the above method, exemplarily divide the functional modules of the vehicle fault cause determination device or electronic device. For example, the vehicle fault cause determination device or electronic device may include each functional module corresponding to each functional division, or two or more functions may be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiment of the present application is illustrative, only a logical function division, and there may be other division methods in actual implementation.

[0125] Figure 11 is a block diagram of a vehicle fault cause determination device shown according to an exemplary embodiment. Refer to Figure 11 As shown in the figure, the vehicle fault cause determination device 110 includes: a transmission module 1101 and a processing module 1102.

[0126] The transmission module 1101 is configured to, when a target fault occurs in the vehicle, in response to a fault data recording instruction, obtain the fault data information of the target fault, where the target fault is a fault for which the fault code DTC is not defined, and the fault data information is the parameter information during vehicle operation.

[0127] The transmission module 1101 is further configured to send the fault data information of the target fault to the cloud server, and the cloud server is configured to determine the cause of the target fault generated by the vehicle based on the fault data information.

[0128] The transmission module 1101 is further configured to receive the cause of the target fault sent by the cloud server.

[0129] The processing module 1102 is configured to display the cause of the target fault on the vehicle.

[0130] In a possible implementation manner, the vehicle fault cause determination device further includes a determination module 1103; the processing module 1102 is further configured to generate a target fault code and a target timestamp in response to a fault data recording instruction; the transmission module 1101 is further configured to send the target fault code to the cloud server, and the target fault code is used for the cloud server to obtain fault data information from the vehicle; the determination module 1103 is configured to determine a target time period based on the target timestamp; the transmission module 1101 is further configured to obtain the fault data information within the target time period.

[0131] In a possible implementation manner, the transmission module 1101 is further configured to receive a fault data information acquisition instruction sent by the cloud server; the transmission module 1101 is further configured to send the fault data information of the target fault to the cloud server based on the fault data information acquisition instruction.

[0132] In a possible implementation manner, the transmission module 1101 is further configured to obtain target description information, where the target description information is used to indicate the vehicle state information when the target fault occurs; the transmission module 1101 is further configured to send the target description information to the cloud server, and the target description information is used for the cloud server to determine the cause of the target fault generated by the vehicle.

[0133] Figure 12 is a block diagram of another vehicle fault cause determination device shown according to an exemplary embodiment. Refer to Figure 12 , the vehicle fault cause determination device 120 includes: a transmission module 1201 and a determination module 1202.

[0134] The transmission module 1201 is configured to receive the fault data information of the target fault sent by the vehicle, where the target fault is a fault with an undefined fault code DTC, and the fault data information is parameter information during vehicle operation.

[0135] The determination module 1202 is configured to determine the cause of the target fault generated by the vehicle based on the fault data information.

[0136] The transmission module 1201 is further configured to send the cause of the target fault to the vehicle.

[0137] In a possible implementation, the transmission module 1201 is further configured to receive a target fault code sent by a vehicle; the transmission module 1201 is further configured to send a fault data information acquisition instruction to the vehicle based on the target fault code, and the fault data information acquisition instruction is used to acquire fault data information.

[0138] In a possible implementation, the transmission module 1201 is further configured to receive target description information sent by the vehicle, and the target description information is used to indicate the vehicle state information when a target fault occurs; the determination module 1202 is further configured to determine the fault cause of the vehicle generating the target fault based on the fault data information and the target description information.

[0139] Regarding the device in the above embodiments, the specific manners in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated herein.

[0140] Figure 13 is a block diagram of an electronic device shown according to an exemplary embodiment. As Figure 13 shown, the electronic device 130 includes but is not limited to: a processor 1301 and a memory 1302.

[0141] Among them, the above-mentioned memory 1302 is used to store executable instructions of the above-mentioned processor 1301. It can be understood that the above-mentioned processor 1301 is configured to execute instructions to implement the vehicle fault cause determination method in the above embodiments.

[0142] It should be noted that those skilled in the art can understand that Figure 13 the structure of the electronic device shown in Figure 13 does not constitute a limitation on the electronic device, and the electronic device may include more or fewer components than

[0143] shown, or combine some components, or arrange different components.

[0144] The memory 1302 can be used to store software programs and various data. The memory 1302 mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required by at least one functional module (such as an acquisition unit, a determination unit, a processing unit, etc.). In addition, the memory 1302 can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0145] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as the memory 1302 including instructions. The above instructions can be executed by the processor 1301 of the electronic device 130 to implement the vehicle fault cause determination method in the above embodiment.

[0146] In actual implementation, Figure 11 the functions of the transmission module 1101, the processing module 1102, and the determination module 1103 in Figure 13 can all be implemented by the processor 1301 in Figure 12 calling the computer program stored in the memory 1302, and Figure 13 the functions of the transmission module 1201 and the determination module 1202 in

[0147] can all be implemented by the processor 1301 in

[0148] calling the computer program stored in the memory 1302. The specific execution process can refer to the description of the vehicle fault cause determination method part in the above embodiment, which will not be elaborated here.

[0147] Optionally, the computer-readable storage medium can be a non-transitory computer-readable storage medium. For example, the non-transitory computer-readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0148] In an exemplary embodiment, a vehicle including a vehicle fault cause determination device is also provided. The vehicle can complete the vehicle fault cause determination method in the above embodiment through the vehicle fault cause determination device.

[0149] In an exemplary embodiment, an embodiment of the present application also provides a computer program product including one or more instructions. The one or more instructions can be executed by the processor 1301 of the electronic device to complete the vehicle fault cause determination method in the above embodiment.

[0150] It should be noted that when one or more instructions in the above-mentioned computer-readable storage medium or the computer program product are executed by the processor of the electronic device, the various processes of the above-mentioned vehicle fault cause determination method embodiment are implemented, and the same technical effects as those of the above-mentioned vehicle fault cause determination method can be achieved. To avoid repetition, details are not described herein again.

[0151] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of description, only the above division of each functional module is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0152] In several embodiments provided in the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of modules or units is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical or other form.

[0153] The unit described as a separated component may or may not be physically separated, and the component displayed as a unit may be a physical unit or multiple physical units, that is, it may be located in one place, or may be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0154] In addition, in each embodiment of the present application, each functional unit can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0155] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions for causing a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods of the embodiments of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical discs that can store program codes.

[0156] The above are only the specific implementation manners of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for determining the cause of a vehicle fault, characterized in that, Applied to a vehicle, a method includes: In the case of a target fault occurring in the vehicle, in response to a fault data recording instruction, obtain fault data information of the target fault, where the target fault is a fault with an undefined diagnostic trouble code (DTC), and the fault data information is parameter information during vehicle operation; Send the fault data information of the target fault to a cloud server, where the cloud server is used to determine the fault cause of the vehicle generating the target fault based on the fault data information; Receive the fault cause of the target fault sent by the cloud server and display it on the vehicle.

2. The method according to claim 1, wherein The method further includes: In response to the fault data recording instruction, generate a target fault code and a target timestamp; Send the target fault code to the cloud server, where the target fault code is used for the cloud server to obtain the fault data information from the vehicle; The obtaining of the fault data information of the target fault includes: Based on the target timestamp, determine a target time period and obtain the fault data information within the target time period.

3. The method according to claim 1 or 2, wherein The sending of the fault data information of the target fault to the cloud server includes: Receive a fault data information obtaining instruction sent by the cloud server; Based on the fault data information obtaining instruction, send the fault data information of the target fault to the cloud server.

4. The method according to claim 1 or 2, characterized in that The method further includes: Obtain target description information, where the target description information is used to indicate vehicle status information when the target fault occurs; Send the target description information to the cloud server, where the target description information is used for the cloud server to determine the fault cause of the vehicle generating the target fault.

5. A method for determining the cause of a vehicle fault, characterized in that, Applied to a cloud server, a method includes: Receive fault data information of a target fault sent by a vehicle, where the target fault is a fault with an undefined DTC, and the fault data information is parameter information during vehicle operation; Based on the fault data information, determine the fault cause of the vehicle generating the target fault; Send the fault cause of the target fault to the vehicle.

6. The method according to claim 5, wherein The method further includes: Receive a target fault code sent by the vehicle; Based on the target fault code, send a fault data information obtaining instruction to the vehicle, where the fault data information obtaining instruction is used to obtain the fault data information.

7. The method according to claim 5 or 6, characterized in that, The method further includes: Receive target description information sent by the vehicle, where the target description information is used to indicate vehicle status information when the target fault occurs; The determining of the fault cause of the vehicle generating the target fault based on the fault data information includes: Based on the fault data information and the target description information, determine the fault cause of the vehicle generating the target fault.

8. A vehicle fault cause determination device, characterized in that, Applied to a vehicle, the vehicle fault cause determination device includes a transmission module and a processing module; The transmission module is used to, in the case of a target fault occurring in the vehicle, in response to a fault data recording instruction, obtain fault data information of the target fault, where the target fault is a fault with an undefined DTC, and the fault data information is parameter information during vehicle operation; The transmission module is further configured to send the fault data information of the target fault to a cloud server, and the cloud server is configured to determine the cause of the target fault generated by the vehicle based on the fault data information; The transmission module is further configured to receive the cause of the target fault sent by the cloud server; The processing module is configured to display the cause of the target fault on the vehicle.

9. A vehicle fault cause determination device, characterized in that, Applied to a cloud server, the vehicle fault cause determination device includes a transmission module and a determination module; The transmission module is configured to receive the fault data information of a target fault sent by a vehicle, where the target fault is a fault with an undefined diagnostic trouble code (DTC), and the fault data information is parameter information during vehicle operation; The determination module is configured to determine the cause of the target fault generated by the vehicle based on the fault data information; The transmission module is further configured to send the cause of the target fault to the vehicle.

10. An electronic device, characterized in that, Comprising: A processor; A memory for storing executable instructions of the processor; Wherein, the processor is configured to execute the instructions to implement the method according to any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that, When the computer-executable instructions stored in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is capable of executing the method according to any one of claims 1 to 7.

12. A vehicle, characterized in that, The vehicle includes the vehicle fault cause determination device according to claim 8 or 9, and the vehicle is configured to implement the method according to any one of claims 1 to 7.

Images