Fault detection method and device, vehicle and storage medium

Abstract

The embodiment of the invention discloses a fault detection method and device, a vehicle and a storage medium. The method comprises the steps that when a vehicle door function of a vehicle fails, vehicle data of the vehicle in a preset time period are obtained, and the vehicle data comprise fault data and remote diagnosis information of all controllers; and based on the whole vehicle data and a diagnosis failure model, the reason for the function failure of the vehicle door of the vehicle is determined, and the diagnosis failure model is a model used for carrying out function failure analysis on the vehicle door driven by front and rear side door supporting rods, front and rear top cover supporting rods and a motor. According to the method, the failure reason can be accurately positioned when the function of the vehicle door fails, and the root of the problem can be quickly found no matter whether the vehicle has a fault code or an accidental fault or not.

Description

Technical Field

[0001] The present application belongs to the field of vehicle technology, and specifically relates to a fault detection method, device, vehicle and storage medium. Background Art

[0002] With the rapid development of automobile automation and intelligence, automobile products that pursue novel experiences have emerged in response to demand. Car doors are one of them. Car doors with multi-integrated systems are more complex to control than ordinary doors. The opening and closing of car doors requires a powerful central computing domain to coordinate with the regional controller and the door controller. The close connection of signals, when a related signal of any controller has a problem, will affect the normal opening and closing of the car door. The novelty of the car door meets the needs of users, but when it fails, the original single fault code troubleshooting mode can no longer fully meet the needs in the multi-system collaborative control architecture. Summary of the invention

[0003] In view of the above problems, the present application proposes a fault detection method, device, vehicle and storage medium to improve the above problems.

[0004] In a first aspect, an embodiment of the present application provides a fault detection method, the method comprising: when a vehicle has a door function failure, obtaining whole vehicle data of the vehicle in a preset time period, the whole vehicle data including fault data and remote diagnostic information of each controller; determining the cause of the door function failure of the vehicle based on the whole vehicle data and a diagnostic failure model, the diagnostic failure model being a model for performing functional failure analysis on doors driven by front and rear side door struts, front and rear roof struts and motors.

[0005] In a second aspect, an embodiment of the present application provides a fault detection device, which includes: an acquisition unit, which is used to acquire vehicle data of the vehicle in a preset time period when a door function failure occurs in the vehicle, the vehicle data including fault data and remote diagnosis information of each controller; a determination unit, which is used to determine the cause of the door function failure of the vehicle based on the vehicle data and a diagnostic failure model, the diagnostic failure model being a model for performing functional failure analysis on doors driven by front and rear side door struts, front and rear roof struts and motors.

[0006] In a third aspect, an embodiment of the present application provides a vehicle, comprising one or more processors and a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the above-mentioned method.

[0007] Fourthly, an embodiment of the present application provides a computer-readable storage medium, in which program code is stored, and when the program code runs, the above-mentioned method is executed.

[0008] An embodiment of the present application provides a fault detection method, device, vehicle and storage medium. First, when the vehicle has a door function failure, the vehicle's overall vehicle data in a preset time period is obtained. The overall vehicle data includes fault data and remote diagnostic information of each controller. Then, based on the overall vehicle data and the diagnostic failure model, the reason for the vehicle's door function failure is determined. The diagnostic failure model is a model used for functional failure analysis of doors driven by front and rear side door struts, front and rear roof struts, and motors. Through the above method, when the door function fails, the failure reason can be accurately located. Whether the vehicle has a fault code or whether it is an occasional fault, the root cause of the problem can be quickly found. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present application. For those skilled in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0010] Figure 1 Shows a flowchart of a fault detection method proposed in an embodiment of the present application;

[0011] Figure 2 Shows a structural block diagram of a door system architecture described in an embodiment of the present application;

[0012] Figure 3 Shows a schematic diagram of a door diagnostic failure model in an embodiment of the present application;

[0013] Figure 4 Shows a flowchart of a fault detection method proposed in another embodiment of the present application;

[0014] Figure 5 Shows a flowchart of a fault detection method proposed in another embodiment of the present application;

[0015] Figure 6 Shows a structural block diagram of a fault detection device proposed in an embodiment of the present application;

[0016] Figure 7 Shows a structural block diagram of a vehicle for executing the fault detection method according to the embodiment of the present application;

[0017] Figure 8A storage unit for storing or carrying program code for implementing a fault detection method according to an embodiment of the present application is shown. Detailed implementation manners

[0018] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the protection scope of the present application.

[0019] An embodiment of the present application provides a fault detection method, device, vehicle, and storage medium. When a door function of a vehicle fails, vehicle data of the vehicle in a preset period is obtained. The vehicle data includes fault data and remote diagnosis information of each controller. Then, based on the vehicle data and a diagnosis failure model, a cause of the door function failure of the vehicle is determined. The diagnosis failure model is a model for performing function failure analysis on doors driven by front and rear door struts, front and rear roof struts, and motors. Through the above method, when the door function fails, the cause of the failure can be accurately located. Whether the vehicle has a fault code or whether it is an occasional fault, the root cause of the problem can be quickly found.

[0020] The embodiments of the present application will be specifically described below with reference to the accompanying drawings.

[0021] Please refer to Figure 1 , a fault detection method provided by an embodiment of the present application, the method includes:

[0022] Step S110: When a door function of a vehicle fails, obtain vehicle data of the vehicle in a preset period. The vehicle data includes fault data and remote diagnosis information of each controller.

[0023] In the embodiment of the present application, the vehicle is a vehicle equipped with a gull-wing door system and a central domain controller. The gull-wing door system is carried in a central computing domain controller architecture. The architecture of the gull-wing door system can be as Figure 2 shown. Among them, the domain controller needs to have a certain amount of memory to store vehicle bus signals and be able to upload the stored data to the cloud server when needed. Through the cloud server, vehicle operation data can be downloaded. Furthermore, a vehicle equipped with a gull-wing door system must have a remote diagnosis function. Through remote diagnosis, diagnosis information of each controller of the vehicle can be read, including fault codes.

[0024] The preset time period can be understood as a fault time period, which can be a time period for obtaining vehicle data for analyzing the cause of the door function failure set in advance. For example, the preset time period can be a preset time period starting from the moment when it is determined that the vehicle has a door function failure and going back in time. Or, the preset time period can be a preset time period starting from the moment when it is determined that the vehicle has a door function failure and going back and forth in time. There is no specific limitation here, as long as the preset time period can obtain complete vehicle data that can be used to analyze the cause of the door function failure. Among them, the door function failure can be understood as the failure of the gull-wing door function of the vehicle, that is, the door can be a gull-wing door.

[0025] In the embodiment of the present application, the fault data is the vehicle fault data obtained during the preset time period, and this fault data can be understood as a bus characteristic signal, which includes bus signals related to the door during the preset time period; the remote diagnosis information is the vehicle's central cloud domain controller uploads the vehicle diagnosis information during the preset time period to the cloud server, and this diagnosis information includes the diagnosis information of each controller in the vehicle during the preset time period.

[0026] The door function failure refers to the door being unable to be opened or closed as expected during normal use, or abnormal phenomena such as false alarms or pinching hands occurring. Among them, unable to be opened or closed normally: When the door attempts to open or close, it may be unable to open or close smoothly due to sensor failures, lock problems, or door structure damage. False reporting of the door state: The central control screen shows that the door is not closed when the door is clearly closed, or the system reports that the door has been opened when the door has not actually been opened. The anti-pinch function fails: The door is usually equipped with an anti-pinch function to prevent pinching passengers during the door closing process. However, if the anti-pinch function fails, it may cause the door to pinch the hand or other parts of the passenger when the door is closed, creating a safety hazard.

[0027] When it is detected that the door is unable to be opened or closed as expected during normal use, or abnormal phenomena such as false alarms or pinching hands occur, obtain the vehicle data during the preset time period.

[0028] Step S120: Based on the vehicle data and the diagnostic failure model, determine the cause of the door function failure of the vehicle. The diagnostic failure model is a model for analyzing the function failure of a door driven by front and rear side door struts, front and rear roof struts, and a motor.

[0029] In the embodiments of the present application, the diagnostic failure model is a diagnostic failure model designed based on the interaction objects of the vehicle door and its own control logic, and is obtained by combining and analyzing relevant bus signals and fault codes or diagnostic information of each associated controller. Since the control of the vehicle door requires a series of signal actions to complete the opening and closing actions, any abnormality in these signals may cause the vehicle door function to fail. Therefore, it is possible to analyze each signal that may cause the vehicle door function to fail, and then obtain all possible fault contents of the vehicle door, that is, obtain the diagnostic failure model. From this diagnostic failure model, all possible fault contents of the vehicle door can be seen, so as to locate the problem point when the vehicle door fails without fault codes. Specifically, the diagnostic failure model can be as follows Figure 3 shown. As can be seen from Figure 3 , the diagnostic failure model includes all fault contents that may cause the vehicle door function to fail. And in this diagnostic failure model, all fault causes that may cause the vehicle door function to fail are still arranged in ascending order of hierarchy. The lower the hierarchy, the more fault contents it includes. On the contrary, the higher the hierarchy, the fewer fault contents it includes. For example, in Figure 3 , the lower hierarchy can be multiple checkpoints (such as communication abnormality, vehicle environment impact, vehicle door associated system abnormality, vehicle door system abnormality, etc. in Figure 3 ), and the higher hierarchy can be specific fault causes (such as loss of communication with xxx, abnormal controller power supply, abnormal input signal, etc. in Figure 3 ).

[0030] In the embodiments of the present application, the diagnostic failure model can be understood as a database storing all fault contents that may cause the vehicle door function to fail. This diagnostic failure model can be stored in a diagnostic failure model device, and this diagnostic failure model device supports running in a cloud server, and can implement the function of retrieving the diagnostic failure model and vehicle data.

[0031] After obtaining the vehicle data for a preset period, the obtained vehicle data can be compared with all the fault contents stored in the vehicle door diagnostic failure model, so as to determine the specific cause or specific fault point of the vehicle door function failure.

[0032] Furthermore, the diagnostic failure model can also include repair suggestions corresponding to each fault cause. After the diagnostic failure model determines the specific cause of the vehicle door function failure of the vehicle, corresponding repair suggestions can also be given according to this specific cause.

[0033] Exemplarily, if the vehicle door is a gull-wing door, the inspection process for the abnormal signal of the gull-wing door top cover strut: A single gull-wing door is driven by two front and rear side door struts and two front and rear top cover struts. When any one of the top cover struts has a problem, the single door cannot be normally opened and closed.

[0034] Symptom: When the left rear gullwing door is opened sporadically, the door starts slowly, cannot fully unfold, and the instrument panel prompts a door opening failure event. Please check the left rear door. It returns to normal after closing the door and powering off.

[0035] In the above situation, the working steps of the diagnostic failure model can include an inspection process and a repair process. Among them, the inspection process includes: the diagnostic failure model scans the bus data during the vehicle operation at the time of the fault occurrence to obtain key signals, and confirms that the configuration codes related to the gullwing door on the vehicle are consistent with those in the model through diagnostic services; after receiving the opening command (door opening signal), the door starts to respond (there is no related fault in the associated system), drives the door to release according to the driving timing sequence of the electric release lock. After the electric release signal of the door acts, the side door secondary strut of the driving side opens at a certain angle (change of the side door strut signal), and the main roof strut starts to act (change of the roof strut signal). When the side door secondary strut and the main roof strut are halfway open, they stop. The Hall motor signal values of the side door strut and the roof strut are not within the normal range, the actual opening signal value is smaller than the target opening signal value, there is a door opening failure event in the bus signal, and at the same time, there is a fault code for the Hall signal fault of the front roof strut main strut.

[0036] The repair process includes: locking the problem in the abnormal Hall signal of the roof strut. According to the repair guide, check the Hall sensor line of the roof strut motor and find that the wire harness is damaged. After replacing the wire harness, the fault symptom disappears, the fault code for the abnormal Hall signal of the roof strut becomes a historical fault, and the gullwing door function returns to normal.

[0037] A fault detection method provided by the present application. When the vehicle has a door function failure, it obtains the vehicle's overall vehicle data during a preset period. The overall vehicle data includes fault data and remote diagnostic information of each controller, and then determines the cause of the vehicle's door function failure based on the overall vehicle data and the diagnostic failure model. Through the above method, when the door function fails, the cause of the failure can be accurately located. Whether the vehicle has a fault code or is an occasional fault, the root cause of the problem can be quickly found.

[0038] Please refer to Figure 4 , a fault detection method provided by an embodiment of the present application, the method includes:

[0039] Step S210: When the vehicle has a door function failure, obtain the vehicle's overall vehicle data during a preset period. The overall vehicle data includes fault data and remote diagnostic information of each controller.

[0040] Step S220: Based on the diagnostic failure model, determine whether there is first data in the overall vehicle data. The first data includes door-related fault codes or related signals.

[0041] In an embodiment of the present application, determining whether there is first data in the vehicle data based on a diagnostic failure model refers to determining whether the vehicle data includes door-related fault codes or related signals. Among them, the door-related fault codes refer to specific codes stored when a door fault is detected, which are used to help technicians quickly locate and solve problems. Different door-related fault codes can be used to represent different door faults. The door-related signals refer to signals transmitted through the door, where transmitting through the door can mean being sent or received by the door.

[0042] Whether there is first data in the vehicle data can refer to whether the vehicle data includes some or all of the door-related fault codes or related signals.

[0043] As a method, compare the vehicle information with all the fault contents stored in the diagnostic failure model that cause door function failure; if there is information in the vehicle information that is the same as the fault content, determine that there is first data in the vehicle data.

[0044] Among them, all the fault contents stored in the diagnostic failure model that cause door function failure can include all door-related fault codes or all related signals that cause door function failure.

[0045] When determining whether there is first data in the vehicle data based on the diagnostic failure model, the vehicle data can be compared with all the fault contents stored in the diagnostic failure model to determine whether there is first data in the vehicle data. Specifically, if there is a fault code in the vehicle data that is the same as the door-related fault code stored in the diagnostic failure model, and / or if there is a signal in the vehicle data that is the same as the related signal that causes door function failure stored in the diagnostic failure model, it can be determined that there is first data in the vehicle data; otherwise, it can be determined that there is no first data in the vehicle data.

[0046] Step S230: If it exists, based on the first data, determine the cause of the door function failure of the vehicle.

[0047] In an embodiment of the present application, when it is determined that there is first data in the vehicle data, the cause of the door function failure of the vehicle can be further determined based on the first data. Specifically, further compare the door-related fault codes or related signals included in the first data with all the fault contents stored in the diagnostic failure model to determine the cause of the door function failure of the vehicle, that is, further determine the faults represented by the door-related fault codes or related signals included in the first data.

[0048] A fault detection method provided by this application can accelerate the troubleshooting of door function failures, comprehensively examine the causes of door function failures, quickly solve faults, locate problems without manually analyzing and reproducing faults, saving manpower and material resources, and improving customer satisfaction at the same time.

[0049] Please refer to Figure 5 , a fault detection method provided by an embodiment of this application, the method includes:

[0050] Step S310: When a door function failure occurs in the vehicle, obtain the vehicle's overall vehicle data during a preset period, and the overall vehicle data includes fault data and remote diagnostic information of each controller.

[0051] Step S320: Based on the diagnostic failure model, determine whether there is first data in the overall vehicle data, and the first data includes door-related fault codes or related signals.

[0052] Step S330: If it exists, based on the diagnostic failure model, determine whether there is second data in the first data, and the second data includes fault codes or related signals with communication anomalies.

[0053] In an embodiment of this application, after determining that the overall vehicle data includes at least some door-related fault codes or related signals, further, it can be determined whether the at least some door-related fault codes or related signals include fault codes or related signals with communication anomalies. Specifically, the first data can be compared with all the fault codes or related signals with door communication anomalies stored in the diagnostic failure model. If there is a fault code in the first data that is the same as the fault code with door communication anomalies stored in the diagnostic failure model, and / or, if there is a signal in the first data that is the same as the related signal that causes door communication anomalies stored in the diagnostic failure model, then it can be determined that there is second data in the first data. Otherwise, it can be determined that there is no second data in the first data.

[0054] Step S340: If it exists, based on the second data, determine the cause of the door function failure of the vehicle.

[0055] In an embodiment of this application, if it is determined that there is second data in the first data, then the second data can be further compared with all the fault contents stored in the diagnostic failure model to determine the cause of the door function failure of the vehicle, that is, further determine the faults represented by the door-related fault codes or related signals included in the second data.

[0056] As a way, based on the diagnostic failure model, if it is determined that the second data is a communication loss signal or a fault code, it is determined that the reason for the failure of the vehicle door function is the communication loss of the door; based on the diagnostic failure model, if it is determined that the second data is a signal or a fault code indicating abnormal power supply to the controller, it is determined that the reason for the failure of the vehicle door function is the abnormal power supply to the controller of the door; based on the diagnostic failure model, if it is determined that the second data is an input / output abnormal signal, it is determined that the reason for the failure of the vehicle door function is the input / output abnormality of the door.

[0057] Specifically, first determine whether the second data is a signal or a fault code indicating communication loss with a certain module. If so, if it is determined that the second data is a communication loss signal or a fault code, it can be determined that the reason for the failure of the vehicle door function is the communication loss of the door, and it is recommended to check the communication line with a certain module or the working state of a certain module; if not, then further determine whether the second data is a signal or a fault code indicating abnormal power supply to the controller. If so, it can be determined that the reason for the failure of the vehicle door function is the abnormal power supply to the controller of the door, and it is recommended to check the door circuit; if not, then further determine whether the second data is an input / output abnormal signal. If so, it can be determined the reason for the failure of the vehicle door function; if not, it can be further determined whether the second data is a fault code or a related signal indicating other communication abnormalities, determine the specific reason for the failure of the vehicle door function, and give corresponding maintenance suggestions.

[0058] Step S350: If the second data does not exist, based on the diagnostic failure model, determine whether there is a third data in the first data, and the third data includes a fault code or a related signal of abnormal vehicle environmental conditions.

[0059] In the embodiment of the present application, when it is determined that the second data does not exist in the first data, it can be further determined whether there is a fault code or a related signal of abnormal vehicle environmental conditions in the first data. Specifically, specifically, the first data can be compared with all the fault codes or related signals of abnormal vehicle environment stored in the diagnostic failure model. If there is a fault code in the first data that is the same as the fault code of abnormal vehicle environment stored in the diagnostic failure model, and / or, if there is a signal in the first data that is the same as the related signal causing abnormal vehicle environment stored in the diagnostic failure model, it can be determined that there is a third data in the first data, otherwise, it can be determined that there is no third data in the first data.

[0060] Step S360: If it exists, based on the third data, determine the reason for the failure of the vehicle door function.

[0061] In an embodiment of the present application, when it is determined that the third data exists in the first data, the cause of the failure characterized by the fault code or related signal included in the third data can be further determined. Specifically, the cause of the failure characterized by the fault code or related signal included in the third data can be one of abnormal vehicle speed signal, abnormal collision signal, inability to start the door function due to non - satisfaction of door setting conditions, etc. Of course, it can also be other causes of failure, which are not specifically limited here. When it is determined that the cause of the failure of the vehicle's door function is the above - mentioned cause of failure, it can be recommended to check whether there is an abnormality in the corresponding controllers such as vehicle speed, collision event, door setting conditions, etc. If there is, retry after repairing and replacing the corresponding abnormal node.

[0062] Step S370: If the third data does not exist, based on the diagnostic failure model, determine whether the fourth data exists in the first data, where the fourth data includes a fault code or related signal of an abnormal door - associated system.

[0063] In an embodiment of the present application, when it is determined that the third data does not exist in the first data, it can be further determined whether there is a fault code or related signal of an abnormal door - associated system in the first data. Specifically, the first data can be compared with all the fault codes or related signals of the abnormal door - associated system stored in the diagnostic failure model. If there is a fault code in the first data that is the same as the fault code of the abnormal door - associated system stored in the diagnostic failure model, and / or if there is a signal in the first data that is the same as the related signal causing the abnormal door - associated system stored in the diagnostic failure model, it can be determined that the fourth data exists in the first data; otherwise, it can be determined that the fourth data does not exist in the first data.

[0064] Step S380: If it exists, based on the fourth data, determine the cause of the failure of the vehicle's door function.

[0065] In an embodiment of the present application, when it is determined that the fourth data exists in the first data, the cause of the failure characterized by the fault code or related signal included in the fourth data can be further determined. Specifically, the cause of the failure characterized by the fault code or related signal included in the fourth data can be one of abnormal door lock, abnormal child lock, abnormal switch button, abnormal door opening warning, etc. Of course, it can also be other causes of failure, which are not specifically limited here. When it is determined that the cause of the failure of the vehicle's door function is the above - mentioned cause of failure, it can be recommended to check whether the door lock, child lock, switch button, and door opening warning status are normal. If not, retry after replacing the door lock, child lock, switch button, door opening warning, etc.

[0066] Step S390: If the fourth data does not exist, based on the diagnostic failure model, determine whether the fifth data exists in the first data, where the fifth data includes a fault code or related signal of an abnormal door system.

[0067] In an embodiment of the present application, when it is determined that the fourth data does not exist in the first data, it is possible to further determine whether there is a fault code or related signal indicating a door system abnormality in the first data. Specifically, the first data can be compared with all the fault codes or related signals indicating a door system abnormality stored in the diagnostic failure model. If there is a fault code in the first data that is the same as the fault code indicating a door system abnormality stored in the diagnostic failure model, and / or if there is a signal in the first data that is the same as the related signal indicating a door system abnormality stored in the diagnostic failure model, it can be determined that the fifth data exists in the first data; otherwise, it can be determined that the fifth data does not exist in the first data.

[0068] Step S391: If it exists, based on the fifth data, determine the cause of the door function failure of the vehicle.

[0069] In an embodiment of the present application, when it is determined that the fifth data exists in the first data, it is possible to further determine the fault cause characterized by the fault code or related signal included in the fifth data. Specifically, the fault cause characterized by the fault code or related signal included in the fifth data can be one of abnormal suction lock, abnormal electric release lock, abnormal stay bar, abnormal anti-pinch strip, etc. Of course, it can also be other fault causes, which are not specifically limited herein. When it is determined that the cause of the door function failure of the vehicle is the above-mentioned fault cause, it is recommended to check whether the states of the suction lock, electric release lock, stay bar, anti-pinch strip, etc. are normal. If not, replace the suction lock, electric release lock, stay bar, anti-pinch strip, etc. and then retry.

[0070] A fault detection method provided by the present application can speed up the troubleshooting of door function failure problems, comprehensively examine the causes of door function failure, quickly solve faults, locate problems without the need to reproduce faults through manual analysis, save manpower and material resources, and improve customer satisfaction at the same time.

[0071] Please refer to Figure 6 , a fault detection device 400 provided by an embodiment of the present application, the device 400 includes:

[0072] An acquisition unit 410, configured to acquire the vehicle's overall vehicle data during a preset period when a door function failure occurs in the vehicle, where the overall vehicle data includes fault data and remote diagnostic information of each controller.

[0073] A determination unit 420, configured to determine the cause of the door function failure of the vehicle based on the overall vehicle data and the diagnostic failure model, where the diagnostic failure model is a model for analyzing the function failure of a door driven by front and rear side door stay bars, front and rear roof stay bars, and motors.

[0074] As a way, the determining unit 420 is specifically configured to determine, based on the diagnostic failure model, whether there is first data in the vehicle data, where the first data includes a door-related fault code or related signal; if so, based on the first data, determine the cause of the door function failure of the vehicle.

[0075] Furthermore, the determining unit 420 is specifically configured to compare the vehicle information with all the fault contents stored in the diagnostic failure model that cause door function failure; if there is information in the vehicle information that is the same as the fault content, determine that there is first data in the vehicle data.

[0076] Furthermore, the determining unit 420 is specifically configured to determine, based on the diagnostic failure model, whether there is second data in the first data, where the second data includes a fault code or related signal of communication anomaly; if so, based on the second data, determine the cause of the door function failure of the vehicle.

[0077] Furthermore, the determining unit 420 is specifically configured to, based on the diagnostic failure model, if it is determined that the second data is a communication loss signal or fault code, determine that the cause of the door function failure of the vehicle is communication loss of the door; based on the diagnostic failure model, if it is determined that the second data is a signal or fault code of abnormal controller power supply, determine that the cause of the door function failure of the vehicle is abnormal controller power supply of the door; based on the diagnostic failure model, if it is determined that the second data is an input / output anomaly signal, determine that the cause of the door function failure of the vehicle is input / output anomaly of the door.

[0078] Furthermore, the determining unit 420 is specifically configured to determine, based on the diagnostic failure model, whether there is third data in the first data, where the third data includes a fault code or related signal of abnormal vehicle environmental conditions; if so, based on the third data, determine the cause of the door function failure of the vehicle.

[0079] Furthermore, the determining unit 420 is specifically configured to determine, based on the diagnostic failure model, whether there is fourth data in the first data, where the fourth data includes a fault code or related signal of abnormal door-associated systems; if so, based on the fourth data, determine the cause of the door function failure of the vehicle.

[0080] Furthermore, the determining unit 420 is specifically configured to determine, based on the diagnostic failure model, whether there is fifth data in the first data, where the fifth data includes a fault code or related signal of abnormal door systems; if so, based on the fifth data, determine the cause of the door function failure of the vehicle.

[0081] It should be noted that the device embodiments in this application correspond to the foregoing method embodiments. For the specific principles in the device embodiments, reference may be made to the content in the foregoing method embodiments, which will not be elaborated here.

[0082] Next, a vehicle provided by this application will be described in conjunction with Figure 7 a vehicle provided by this application.

[0083] Please refer to Figure 7 , based on the above-mentioned fault detection method and device, another vehicle 800 that can execute the foregoing fault detection method is further provided in an embodiment of this application. The vehicle 800 includes one or more (only one is shown in the figure) processors 802, a memory 804, a millimeter-wave radar 806, and a network module 806 that are coupled to each other. Among them, a program that can execute the content in the foregoing embodiments is stored in the memory 804, and the processor 802 can execute the program stored in the memory 804.

[0084] Among them, the processor 802 may include one or more processing cores. The processor 802 connects various parts within the entire vehicle 800 through various interfaces and lines, and executes various functions of the vehicle 800 and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 804, and by calling data stored in the memory 804. Optionally, the processor 802 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 802 may integrate a combination of one or several of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, application programs, etc.; the GPU is responsible for rendering and drawing display content; the modem is used to process wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 802 and may be implemented separately by a communication chip.

[0085] The memory 804 may include a Random Access Memory (RAM), or may also include a Read-Only Memory. The memory 804 can be used to store instructions, programs, codes, code sets, or instruction sets. The memory 804 may include a program storage area and a data storage area. Among them, the program storage area may store instructions for implementing the operating system, instructions for implementing at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the following various method embodiments, etc. The data storage area may also store data created during the use of the vehicle 800 (such as phone books, audio and video data, chat record data, etc.).

[0086] The network module 806 is used to receive and send electromagnetic waves, implement the mutual conversion between electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices, such as communicating with a vehicle. The network module 806 may include various existing circuit elements for performing these functions. For example, antennas, radio frequency transceivers, digital signal processors, encryption / decryption chips, subscriber identity module (SIM) cards, memories, and so on. The network module 806 can communicate with various networks such as the Internet, enterprise intranets, wireless networks, or communicate with other devices through a wireless network. The above-mentioned wireless network may include a cellular phone network, a wireless local area network, or a metropolitan area network. For example, the network module 806 can interact with a base station for information.

[0087] Please refer to Figure 8 , which shows a structural block diagram of a computer-readable storage medium provided by an embodiment of the present application. Program codes are stored in the computer-readable storage medium 900, and the program codes can be called by a processor to execute the methods described in the above method embodiments.

[0088] The computer-readable storage medium 900 may be an electronic memory such as a flash memory, an Electrically Erasable Programmable Read-Only Memory (EEPROM), an EPROM, a hard disk, or a ROM. Optionally, the computer-readable storage medium 900 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 900 has a storage space for program codes 910 for executing any method steps in the above methods. These program codes can be read out from one or more computer program products or written into these one or more computer program products. The program codes 910 can be compressed in an appropriate form, for example.

[0089] A fault detection method, device, vehicle, and storage medium provided by the present application. When a door function of the vehicle fails, vehicle data for a preset period is obtained. The vehicle data includes fault data and remote diagnostic information of each controller. Then, based on the vehicle data and a diagnostic failure model, which is a model for analyzing the functional failure of a door driven by front and rear side door struts, front and rear roof cover struts, and a motor, the cause of the door function failure of the vehicle is determined. Through the above method, the cause of the failure can be accurately located when the door function fails. Whether the vehicle has a fault code or whether it is an occasional fault, the root cause of the problem can be quickly found.

[0090] The embodiments of the present invention have been described above in conjunction with the accompanying drawings. However, the present invention is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present invention, those of ordinary skill in the art can also make many forms without departing from the spirit and scope protected by the claims of the present invention, and all of them belong to the protection scope of the present invention.

Claims

1. A fault detection method, characterized in that, The method includes: When the door function of the vehicle fails, obtaining the vehicle's overall vehicle data during a preset period, where the overall vehicle data includes fault data and remote diagnostic information of each controller; Based on the overall vehicle data and the diagnostic failure model, determining the cause of the door function failure of the vehicle, where the diagnostic failure model is a model for performing function failure analysis on doors driven by front and rear side door struts, front and rear roof struts, and motors.

2. The method according to claim 1, characterized in that, The determining the cause of the door function failure of the vehicle based on the overall vehicle data and the diagnostic failure model includes: Based on the diagnostic failure model, determining whether there is first data in the overall vehicle data, where the first data includes door-related fault codes or related signals; If it exists, based on the first data, determining the cause of the door function failure of the vehicle.

3. The method according to claim 2, characterized in that The determining whether there is first data in the overall vehicle data based on the diagnostic failure model includes: Comparing the overall vehicle information with all the fault contents stored in the diagnostic failure model that cause door function failure; If there is information in the overall vehicle information that is the same as the fault content, determining that there is first data in the overall vehicle data.

4. The method according to claim 2, wherein The determining the cause of the door function failure of the vehicle based on the first data includes: Based on the diagnostic failure model, determining whether there is second data in the first data, where the second data includes fault codes or related signals of communication anomalies; If it exists, based on the second data, determining the cause of the door function failure of the vehicle.

5. The method according to claim 4, wherein The determining the cause of the door function failure of the vehicle based on the second data includes: Based on the diagnostic failure model, if it is determined that the second data is a communication loss signal or fault code, determining that the cause of the door function failure of the vehicle is communication loss of the door; Based on the diagnostic failure model, if it is determined that the second data is a controller power supply anomaly signal or fault code, determining that the cause of the door function failure of the vehicle is controller power supply anomaly of the door; Based on the diagnostic failure model, if it is determined that the second data is an input / output anomaly signal, determining that the cause of the door function failure of the vehicle is input / output anomaly of the door.

6. The method according to claim 2, characterized in that, The determining the cause of the door function failure of the vehicle based on the first data includes: Based on the door diagnostic failure model, determining whether there is third data in the first data, where the third data includes fault codes or related signals of abnormal vehicle environmental conditions; If it exists, based on the third data, determining the cause of the door function failure of the vehicle.

7. The method according to claim 2, wherein The determining the cause of the door function failure of the vehicle based on the first data includes: Based on the door diagnostic failure model, determining whether there is fourth data in the first data, where the fourth data includes fault codes or related signals of abnormal door-related systems; If it exists, based on the fourth data, determining the cause of the door function failure of the vehicle.

8. The method according to claim 7, characterized in that, The performing over-temperature fault detection on the high-voltage connection system based on the temperature monitoring signal includes: Based on the diagnostic failure model, determine whether there is a fifth data in the first data, where the fifth data includes a fault code or related signal of the abnormal door system; If it exists, based on the fifth data, determine the cause of the door function failure of the vehicle.

9. A fault detection device, characterized in that, The device includes: An acquisition unit, configured to acquire the vehicle's overall vehicle data during a preset period when the vehicle has a door function failure, where the overall vehicle data includes fault data and remote diagnostic information of each controller; A determination unit, configured to determine the cause of the door function failure of the vehicle based on the overall vehicle data and the diagnostic failure model, where the diagnostic failure model is a model for performing function failure analysis on doors driven by front and rear door struts, front and rear roof struts, and motors.

10. A vehicle, characterized in that, It includes one or more processors and a memory; one or more programs are stored in the memory and are configured to be executed by the one or more processors to perform the method according to any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, Program code is stored in the computer-readable storage medium, where the method according to any one of claims 1-8 is executed when the program code is run by the processor.

Images