Vehicle communication fault diagnosis method and apparatus, and vehicle

Abstract

A vehicle communication fault diagnosis method and apparatus, and a vehicle. The diagnosis method comprises: acquiring fault information of a vehicle (S1); when it is determined that the fault information meets a preset identification condition, recording a fault state of a current target component and a fault code corresponding to the fault state (S2); on the basis of the fault state and the fault code, performing fault processing on the target component (S3); when it is determined that the fault state of the current target component is cleared, determining whether the current fault state meets a preset clearing condition, so as to obtain a determination result (S4); and, on the basis of the determination result, generating a fault response policy (S5). After the fault state is cleared, the cleared fault state is determined, so as to avoid clearing fault states that do not meet the preset clearing condition.

Description

Vehicle communication fault diagnosis method and device and vehicle TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle control, in particular to a vehicle communication fault diagnosis method, device and vehicle. The present application claims priority to the patent application filed on June 03, 2024 with the China National Intellectual Property Office and with application number 202410703704.9, and with the title of "Vehicle communication fault diagnosis method, device and vehicle". BACKGROUND

[0002] With the increasing development of CAN (Controller Area Network) bus technology, it is applied more and more widely in industrial control systems. In the automotive industry, CAN bus is more susceptible to electromagnetic interference from high-power devices such as motor systems and chargers, resulting in communication failures.

[0003] When the vehicle CAN network has a communication failure, to prevent the vehicle function from responding abnormally due to the inability of the electronic control units to normally exchange data through the CAN network, the fault processing module performs fault recovery for the corresponding communication failure. After fault recovery, due to improper fault handling method, fault phenomenon occurs frequently in a short period of time, thereby affecting the safe driving of the vehicle.

[0004] In view of the above problems, no effective solution has been proposed so far.

[0005] SUMMARY

[0006] The embodiments of the present application provide a vehicle communication fault diagnosis method, device and vehicle to at least solve the technical problem of frequent occurrence of fault phenomenon due to improper fault handling method.

[0007] According to an aspect of an embodiment of the present application, a vehicle communication fault diagnosis method is provided, comprising: obtaining fault information of a vehicle, the fault information at least including communication fault information of a target component of the vehicle; in a case where it is determined that the fault information meets a preset identification condition, recording a fault state of the current target component and a fault code corresponding to the fault state; performing fault handling on the target component based on the fault state and the fault code; in a case where it is determined that the fault state of the current target component is cleared, judging whether the current fault state meets a preset clearing condition to obtain a judgment result; generating a fault response strategy based on the judgment result, wherein the fault response strategy includes at least one of the following: a fault latching strategy and a fault clearing strategy, wherein the fault latching strategy includes maintaining the current fault state and maintaining the fault code corresponding to the current fault state, and the fault clearing strategy includes clearing the current fault state and saving the fault code corresponding to the current fault state as a historical fault code to a target position.

[0008] Optionally, in the case where it is determined that the fault information meets the preset identification condition, the fault state of the current target component and the fault corresponding to the fault state are recorded, including: determining whether the low-voltage power-on duration of the current target component is greater than a preset duration; if yes, recording the fault state of the current target component and the fault corresponding to the fault state.

[0009] Optionally, in the case where it is determined that the fault information meets the preset identification condition, the fault state of the current target component and the fault corresponding to the fault state are recorded, and further including: determining whether the low-voltage power-on duration of the current target component is greater than a preset duration; if yes, determining whether the current target component has completed initialization; if yes, recording the fault state of the current target component and the fault corresponding to the fault state.

[0010] Optionally, the fault response strategy is generated based on the determination result, including: in the case where it is determined that the current fault state is cleared, determining whether the current fault state meets a preset clearing condition; if no, generating a fault latching strategy in the fault response strategy.

[0011] Optionally, the determination of whether the current fault state meets the preset clearing condition includes: determining whether a hibernation flag bit of a first target component in the target components is triggered, wherein the first target component includes at least one of: a battery management system, a motor control unit; if yes, generating a fault latching strategy in the fault response strategy.

[0012] Optionally, the generation of the fault latching strategy in the fault response strategy includes: from the moment when the first target component enters hibernation, controlling the vehicle controller to latch the current fault state and to latch the fault code corresponding to the current fault state to the hibernation completion of the first target component.

[0013] Optionally, the determination of whether the current fault state meets the preset clearing condition includes: determining whether a low-voltage power-off flag bit of a second target component in the target components is triggered, wherein the second target component includes at least one of: an engine management system, a transmission control unit; if yes, generating a fault latching strategy in the fault response strategy.

[0014] Optionally, the generation of the fault latching strategy in the fault response strategy includes: from the moment when the second target component enters low-voltage power-off, controlling the vehicle controller to latch the current fault state and to latch the fault code corresponding to the current fault state to the shutdown completion of the second target component.

[0015] According to another aspect of the embodiments of the present application, a vehicle communication fault diagnosis apparatus is also provided, comprising: an acquisition module, configured to acquire fault information of a vehicle, wherein the fault information at least comprises communication fault information of a target component of the vehicle; a first judgment module, configured to record a fault state of the target component and a fault code corresponding to the fault state, in a case where it is determined that the fault information meets preset identification conditions; a fault processing module, configured to perform fault processing on the target component based on the fault state and the fault code; a second judgment module, configured to determine whether the current fault state meets preset clearing conditions and obtain a judgment result, in a case where it is determined that the current fault state is cleared; and a generation module, configured to generate a fault response strategy based on the judgment result, wherein the fault response strategy comprises at least one of a fault latching strategy and a fault clearing strategy, wherein the fault latching strategy comprises keeping the current fault state and keeping the fault code corresponding to the current fault state, and the fault clearing strategy comprises clearing the current fault state and saving the fault code corresponding to the current fault state as a historical fault code to a target position.

[0016] According to another aspect of the embodiments of the present application, a computer storage medium is also provided, comprising a stored program, wherein the program controls a device where the computer storage medium is located to perform the above-mentioned diagnosis method when the program is running.

[0017] According to another aspect of the embodiments of the present application, a computer program product is also provided, comprising a computer program, which, when executed by a processor, implements the steps of the above-mentioned diagnosis method.

[0018] According to another aspect of the embodiments of the present application, a vehicle is also provided, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the above-mentioned diagnosis method.

[0019] In the embodiments of the present application, it is determined whether the acquired fault information meets preset identification conditions, and in a case where it is determined that the preset identification conditions are met, the fault state of the current target component and the fault code are recorded, fault processing is performed on different fault states and fault codes to clear the fault of the current target component, after the fault state of the current target component is cleared, it is determined whether the cleared fault state meets preset clearing conditions and a judgment result is obtained, and the vehicle control unit generates a fault response strategy based on the judgment result to latch the fault state and the fault code which are mistakenly cleared. The above-mentioned diagnosis method performs judgment and identification on the fault information, so as to avoid the vehicle from being mistakenly operated due to the vehicle control unit recording invalid fault states, and after the fault state is cleared, the cleared fault state is determined, so as to avoid the fault state which does not meet the preset clearing conditions from being cleared, and thus the fault is not frequent. BRIEF DESCRIPTION OF DRAWINGS

[0020] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:

[0021] Fig. 1 is a hardware structure block diagram of a computer terminal (or mobile device) for implementing a diagnosis method of vehicle communication fault according to an embodiment of the present application;

[0022] Fig. 2 is a flow chart of the diagnosis method of vehicle communication fault according to an embodiment of the present application;

[0023] Fig. 3 is a structural schematic diagram of a hybrid system according to an embodiment of the present application;

[0024] Fig. 4 is a flow chart of the diagnosis method of hybrid vehicle communication fault according to an embodiment of the present application;

[0025] Fig. 5 is a structural block diagram of a diagnosis device of vehicle communication fault according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to make the personnel in the art better understand the scheme of the present application, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the 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. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] Embodiment 1

[0029] According to the embodiments of the present application, the diagnostic method for vehicle communication failure is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown.

[0030] FIG. 1 is a hardware structure block diagram of a computer terminal (or mobile device) for implementing the diagnostic method for vehicle communication failure according to the embodiments of the present application. As shown in FIG. 1, the computer terminal (or mobile device) can include one or more processors 102 (the processor can include but not limited to a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microprocessor (MCU), a programmable logic device (FPGA), a neural network processor (NPU), a tensor processor (TPU), an artificial intelligence (AI) type processor, etc.) and a memory 104 for storing data. In addition, it can also include a transmission device 106 for communication function, an input and output device 108, and a display 110. Those skilled in the art can understand that the structure shown in FIG. 1 is only schematic, which does not limit the structure of the above-mentioned computer terminal (or mobile device). For example, the computer terminal can also include more or less components than the above structure description, or have a different configuration from the above structure description.

[0031] The memory 104 can be used to store computer programs, for example, software programs of application software and modules, such as the computer program corresponding to the diagnostic method for vehicle communication failure in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implements the diagnostic method for vehicle communication failure described above. The memory 104 can include a high-speed random access memory, and can also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory 104 can further include a memory remotely arranged with respect to the processor 102, which can be connected to the mobile terminal through a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0032] The transmission device 106 is configured to receive or send data via a network. The network can include a wireless network provided by a communication provider of the mobile terminal. In one embodiment, the transmission device 106 includes a network interface controller (NIC) that is configured to connect to other network devices via a base station to communicate with the Internet. In one embodiment, the transmission device 106 can be a radio frequency (RF) module that is configured to communicate with the Internet via a wireless network.

[0033] The display 110 can be a touch screen liquid crystal display (LCD). The LCD can enable a user to interact with a user interface of the mobile terminal. In some embodiments, the mobile terminal has a graphical user interface (GUI) that a user can interact with via finger contacts and / or gestures on the touch-sensitive surface. The user interactions can include, for example, creating a webpage, drawing, text editing, composing an electronic mail message, playing a game, viewing a video, viewing a digital photo, and / or browsing the Internet, among other examples. Executable instructions for performing these user interactions are configured / stored in a computer program product or a readable storage medium that is executable by one or more processors.

[0034] FIG. 2 is a flowchart of a method for diagnosing a communication fault of a vehicle according to an embodiment of the present application. As shown in FIG. 2, the method includes the following steps:

[0035] Step S1: obtaining fault information of the vehicle, the fault information including at least communication fault information of a target component of the vehicle.

[0036] It can be understood that the target component of the vehicle is connected to the vehicle controller, and the vehicle controller receives the fault information fed back by the target component of the vehicle, wherein the target component of the vehicle includes but is not limited to an engine management system, a battery management system, a motor control unit, a transmission control unit, a chassis controller, a body controller, an airbag controller, an electronic gear shifter, etc. In addition, the fault information includes Checksum fault information, Livecounter fault information, Timeout fault information, Busoff fault information, etc. in addition to the communication fault information.

[0037] Step S2: recording a fault state of the target component and a fault code corresponding to the fault state when it is determined that the fault information meets a preset identification condition.

[0038] It can be understood that the fault state refers to an abnormal situation that occurs during the operation of the vehicle, and the fault state is generally displayed on the vehicle instrument or central control display screen to remind the driver. The fault code is a coding method for identifying and diagnosing the fault state, usually composed of a specific set of numbers or characters, and the fault code can help technicians quickly locate the fault cause and take corresponding maintenance measures.

[0039] Step S3: fault processing of the target component based on the fault state and the fault code.

[0040] It can be understood that according to the fault state, the fault phenomenon, the occurrence time, the occurrence frequency, etc. can be known. The fault code is usually generated by the diagnostic system of the vehicle and can be read through the OBD-II (On-Board Diagnostics) scanning tool. According to the fault code, it can be preliminarily judged that the fault may involve the system or component, and detailed inspection (including but not limited to visual inspection, electrical test, etc.) is carried out for the system or component indicated by the fault code. According to the inspection result, the fault cause is further diagnosed (involving detailed test on sensors, actuators, control modules, etc. of the vehicle), and after the fault cause is determined, corresponding maintenance or replacement is carried out.

[0041] Step S4: determining whether the current fault state meets the preset clearing condition to obtain a judgment result in a case where it is determined that the fault state of the current target component is cleared.

[0042] It can be understood that after the fault state of the current target component is cleared, the fault state will not be displayed on the vehicle instrument or central control display screen.

[0043] Step S5: generating a fault response strategy based on the judgment result, wherein the fault response strategy includes at least one of the following: a fault latching strategy and a fault clearing strategy, wherein the fault latching strategy includes maintaining the current fault state and the fault code corresponding to the current fault state, and the fault clearing strategy includes clearing the current fault state and saving the fault code corresponding to the current fault state as a historical fault code to a target position.

[0044] In the embodiments of the present application, it is determined whether the acquired fault information meets the preset identification condition, and in the case where it is determined that the preset identification condition is met, the fault state and the fault code of the current target component are recorded, fault processing is performed for different fault states and fault codes to clear the fault of the current target component, after the fault state of the current target component is cleared, it is determined whether the cleared fault state meets the preset clearing condition and a determination result is obtained, and the vehicle control unit generates a fault response strategy based on the determination result to latch the fault state and the fault code which are mistakenly cleared. The above-mentioned diagnosis method performs judgment and identification on the fault information to avoid the misoperation of the vehicle caused by the vehicle control unit recording invalid fault states, and after the fault state is cleared, the cleared fault state is determined to avoid the fault state which does not meet the preset clearing condition being cleared, thereby preventing frequent faults.

[0045] In an exemplary embodiment of the present application, the diagnosis method is described in detail by taking the hybrid power system of a hybrid vehicle as an example, wherein, as shown in FIG. 3, the hybrid power system comprises an engine 1, a disconnect clutch 2, a motor 3, a transmission 4, a power battery 5, an inverter 6, a wheel 7, a vehicle control unit 8, an auxiliary starter 9, an electric auxiliary oil pump 10, an engine management system 11, a motor control unit 12, a direct current voltage converter 13, a low-voltage storage battery 14, a transmission control unit 15, an energy management system 16 and a high-voltage relay 17.

[0046] The hybrid power system is composed of two power sources, the first power source is the engine 1, and the second power source is the motor 3. The engine 1 is connected with the motor 3 through the disconnect clutch 2. When the disconnect clutch 2 is in a disengaged state, the power battery 5 provides electric energy for the motor through the inverter 6, and the torque output by the motor 3 is transmitted to the wheel 7 through the transmission 4 to drive the vehicle to run. When the disconnect clutch 2 is engaged, the engine 1 and the motor 3 can simultaneously or individually output torque to drive the vehicle to run.

[0047] The engine 1 is controlled by the engine management system 11, the motor 3 is controlled by the motor control unit 12, the transmission 4 is controlled by the transmission control unit 15, and the power battery 5 is controlled by the battery management system 16. The vehicle control unit 8 can send control instructions to the engine management system 11, the motor control unit 12 and the transmission control unit 15 through the CAN bus to control the operation of each power assembly, and can also directly control the operation of the disconnect clutch 2, the auxiliary starter 9 and the electric auxiliary oil pump 10.

[0048] The high-voltage relay 17 can disconnect and combine the power battery 5 and the high-voltage system, and the direct current voltage converter 13 is used to convert the electric energy in the power battery 5 into 12V electric energy to charge the low-voltage storage battery 14.

[0049] Specifically, as shown in FIG. 4, the vehicle controller 8 acquires the fault state information of the engine management system 11, the motor control unit 12, the transmission control unit 15, and the energy management system 16 in real time; the vehicle controller 8 judges whether the fault state information meets the fault recognition condition, if yes, the vehicle controller 8 records the fault state, the fault code, and performs fault processing; continues to judge whether the fault state is cleared, if yes, continues to judge whether the fault state meets the fault clearing condition, if yes, clears the fault state, and changes the fault code to the historical fault; continues to judge whether the fault state is cleared, if yes, continues to judge whether the fault state meets the fault clearing condition, if no, keeps the fault state, and keeps the current fault code.

[0050] Further, in the step S2, in the case that it is determined that the fault information meets the preset recognition condition, the fault state of the current target component and the fault corresponding to the fault state are recorded, including the following steps:

[0051] In the step S21, it is judged whether the low-voltage power-on duration of the current target component is greater than a preset duration.

[0052] Taking the hybrid power system of the hybrid vehicle as an example, the target components include the engine management system, the motor control unit, the transmission control unit, and the battery management system, and the target components need to be powered on by low voltage before communication. The fault information acquired by the vehicle controller before the low-voltage power-on is completed is unreliable and invalid. The low-voltage power-on duration refers to the timing from the low-voltage power-on of the target component.

[0053] In the step S22, if yes, the fault state of the current target component and the fault corresponding to the fault state are recorded.

[0054] In the above steps, the low-voltage power-on duration of the target component is judged to ensure that the fault information recorded by the vehicle controller is valid and reliable.

[0055] Preferably, in the step S2, in the case that it is determined that the fault information meets the preset recognition condition, the fault state of the current target component and the fault corresponding to the fault state are recorded, including:

[0056] In the step S201, it is judged whether the low-voltage power-on duration of the current target component is greater than a preset duration.

[0057] Taking the hybrid power system of the hybrid vehicle as an example, the target components include the engine management system, the motor control unit, the transmission control unit, and the battery management system, and the target components need to be powered on by low voltage before communication. The fault information acquired by the vehicle controller before the low-voltage power-on is completed is unreliable and invalid.

[0058] Step S202: If yes, it is judged whether the current target component is completed initialization.

[0059] It should be noted that the general target component can complete its own initialization setting within a preset time period after low-voltage power-on, but it cannot be ruled out that the initialization setting of part of the target component has a lag phenomenon. After the target component completes the initialization, it can communicate with the vehicle controller, so the fault information obtained by the vehicle controller before the initialization is completed is unreliable and invalid.

[0060] Step S203: If yes, record the fault state of the current target component and the fault corresponding to the fault state.

[0061] In the above steps, the low-voltage power-on time of the target component and whether the initialization is completed are judged to ensure that the fault information recorded by the vehicle controller is effective and reliable.

[0062] Further, the fault response strategy is generated based on the judgment result in step S5, including the following steps:

[0063] Step S51: In the case where the current fault state is determined to be cleared, it is judged whether the current fault state meets the preset clearing condition.

[0064] Step S52: If no, the fault latching strategy in the fault response strategy is generated.

[0065] In the above steps, after the fault state is cleared, the cleared fault state is judged to avoid the fault state that does not meet the preset clearing condition being cleared, thereby causing frequent faults.

[0066] In an exemplary embodiment of the present application, in step S4, it is judged whether the current fault state meets the preset clearing condition, including the following judgment steps:

[0067] Step S41: It is judged whether the hibernation flag bit of a first target component in the target component is triggered, wherein the first target component includes at least one of the following: battery management system, motor control unit.

[0068] Taking the hybrid power system of the above hybrid vehicle as an example, the target component includes an engine management system, a motor control unit, a transmission control unit, and a battery management system, wherein the battery management system and the motor control unit are controllers supporting hibernation and wake-up. After the battery management system and the motor control unit hibernate, the fault state corresponding to the battery management system and the motor control unit will be cleared, but the fault corresponding to the battery management system and the motor control unit is not restored, and after the battery management system and the motor control unit are woken up, the corresponding fault will reappear, thereby causing frequent faults and affecting safe driving of the vehicle.

[0069] Step S42: If yes, a fault latching strategy in the fault response strategy is generated.

[0070] In the above steps, whether the hibernation flag of the first target component in the target components is triggered is determined to exclude the case that the fault caused by the hibernation of the controller is cleared.

[0071] Specifically, the generation of the fault latching strategy in the fault response strategy includes: controlling the vehicle controller to latch the current fault state and the fault code corresponding to the current fault state since the first target component enters the hibernation time until the hibernation of the first target component is completed. This is to ensure that the fault state of the first target component is latched in the corresponding vehicle instrument or central control during the hibernation of the first target component, and the corresponding fault code is latched in the fault list.

[0072] In an exemplary embodiment of the present application, the determination of whether the current fault state satisfies the preset clearing condition in step S4 includes the following determination steps:

[0073] Step S401: Whether the low-voltage power-down flag of the second target component in the target components is triggered is determined, wherein the second target component includes at least one of the engine management system and the transmission control unit.

[0074] Taking the hybrid power system of the hybrid vehicle as an example, the target components include the engine management system, the motor control unit, the transmission control unit, and the battery management system, wherein the engine management system and the transmission control unit are controllers that only support IGON power supply (power supply). After the low-voltage power-down of the engine management system and the transmission control unit, the fault state corresponding to the engine management system and the transmission control unit will be cleared, but the fault corresponding to the engine management system and the transmission control unit is not restored, and after the low-voltage power-up of the engine management system and the transmission control unit again, the corresponding fault will reappear, and thus the fault occurs frequently, affecting the safe driving of the vehicle.

[0075] Step S402: If yes, a fault latching strategy in the fault response strategy is generated.

[0076] In the above steps, whether the low-voltage power-down flag of the second target component in the target components is triggered is determined to exclude the case that the fault caused by the low-voltage power-down of the controller is cleared.

[0077] Specifically, the generation of the fault latching strategy in the fault response strategy includes: controlling the vehicle controller to latch the current fault state and the fault code corresponding to the current fault state since the second target component enters the low-voltage power-down time until the shutdown of the second target component is completed. This is to ensure that the fault state of the second target component is latched in the corresponding vehicle instrument or central control during the low-voltage power-down of the second target component, and the corresponding fault code is latched in the fault list.

[0078] Embodiment 2

[0079] The embodiment of the present application further provides a diagnosis device for vehicle communication fault, and Fig. 5 is a structural block diagram of the diagnosis device. As shown in Fig. 5, the device comprises an acquisition module, a first judgment module, a second judgment module, a fault processing module and a generation module.

[0080] The acquisition module is used for acquiring fault information of the vehicle, and the fault information at least comprises communication fault information of a target component of the vehicle.

[0081] The first judgment module is used for recording a fault state of the current target component and a fault code corresponding to the fault state in a case where it is determined that the fault information meets preset identification conditions.

[0082] The fault processing module is used for performing fault processing on the target component based on the fault state and the fault code.

[0083] The second judgment module is used for judging whether the current fault state meets preset clearing conditions and obtaining a judgment result in a case where it is determined that the current fault state is cleared.

[0084] The generation module is used for generating a fault response strategy based on the judgment result, wherein the fault response strategy comprises at least one of a fault latching strategy and a fault clearing strategy, the fault latching strategy comprises keeping the current fault state and keeping the fault code corresponding to the current fault state, and the fault clearing strategy comprises clearing the current fault state and saving the fault code corresponding to the current fault state as a historical fault code to a target position.

[0085] In the embodiment of the present application, it is judged whether the acquired fault information meets preset identification conditions, and in a case where it is determined that the preset identification conditions are met, the fault state of the current target component and the fault code are recorded. Different fault states and fault codes are subjected to fault processing to clear the fault of the current target component. After the fault state of the current target component is cleared, it is judged whether the cleared fault state meets preset clearing conditions and a judgment result is obtained. The vehicle control unit generates a fault response strategy based on the judgment result to latch the fault state and the fault code which are mistakenly cleared. The above diagnosis method judges and identifies the fault information to avoid the vehicle from being mistakenly operated due to the vehicle control unit recording invalid fault states. After the fault state is cleared, the cleared fault state is judged to avoid the fault state which does not meet the preset clearing conditions from being cleared, thereby avoiding frequent faults.

[0086] Embodiment 3

[0087] The embodiment of the present application further provides a computer storage medium, which comprises a stored program, wherein the computer storage medium controls a device where the computer storage medium is located to execute the diagnostic method in the above embodiment when the program is run.

[0088] In the embodiment, the computer storage medium can be configured to store a computer program for executing the following steps:

[0089] Step S1: obtaining fault information of a vehicle, the fault information at least comprising communication fault information of a target component of the vehicle.

[0090] Step S2: recording a fault state of the current target component and a fault code corresponding to the fault state when it is determined that the fault information meets preset identification conditions.

[0091] Step S3: performing fault processing on the target component based on the fault state and the fault code.

[0092] Step S4: judging whether the current fault state meets preset clearing conditions and obtaining a judgment result when it is determined that the fault state of the current target component is cleared.

[0093] Step S5: generating a fault response strategy based on the judgment result, wherein the fault response strategy comprises at least one of a fault latching strategy and a fault clearing strategy, the fault latching strategy comprises keeping the current fault state and keeping the fault code corresponding to the current fault state, and the fault clearing strategy comprises clearing the current fault state and saving the fault code corresponding to the current fault state as a historical fault code to a target position.

[0094] In the embodiment of the present application, it is judged whether the obtained fault information meets preset identification conditions, and the fault state of the current target component and the fault code are recorded when it is determined that the preset identification conditions are met. Different fault states and fault codes are processed to clear the fault of the current target component. After the fault state of the current target component is cleared, it is judged whether the cleared fault state meets preset clearing conditions and a judgment result is obtained. The vehicle control unit generates a fault response strategy based on the judgment result to latch the fault state and the fault code which are cleared by mistake. The diagnostic method described above judges and identifies the fault information to avoid the vehicle from being misoperated due to the vehicle control unit recording invalid fault states. After the fault state is cleared, the cleared fault state is judged to avoid the fault state which does not meet the preset clearing conditions from being cleared, thereby avoiding frequent faults.

[0095] Embodiment 4

[0096] The embodiment of the present application further provides a computer program product, wherein the computer program is executed by a processor to implement the steps of the diagnostic method in the above embodiment.

[0097] In the embodiment, the computer program product can be configured to execute the following steps by the computer program:

[0098] Step S1: obtaining fault information of the vehicle, the fault information at least including communication fault information of a target component of the vehicle.

[0099] Step S2: in a case where it is determined that the fault information meets preset identification conditions, recording a fault state of the current target component and a fault code corresponding to the fault state.

[0100] Step S3: performing fault processing on the target component based on the fault state and the fault code.

[0101] Step S4: in a case where it is determined that the fault state of the current target component is cleared, judging whether the current fault state meets preset clearing conditions and obtaining a judgment result.

[0102] Step S5: generating a fault response strategy based on the judgment result, wherein the fault response strategy includes at least one of a fault latching strategy and a fault clearing strategy, the fault latching strategy includes maintaining the current fault state and maintaining the fault code corresponding to the current fault state, and the fault clearing strategy includes clearing the current fault state and saving the fault code corresponding to the current fault state as a historical fault code to a target position.

[0103] In the embodiment of the application, it is judged whether the obtained fault information meets preset identification conditions, in a case where it is determined that the preset identification conditions are met, the fault state of the current target component and the fault code are recorded, fault processing is performed on different fault states and fault codes to clear the fault of the current target component, after the fault state of the current target component is cleared, it is judged whether the cleared fault state meets preset clearing conditions and a judgment result is obtained, and the vehicle control unit generates a fault response strategy based on the judgment result to latch the fault state and the fault code that are mistakenly cleared. The above-mentioned diagnosis method judges and identifies the fault information to avoid the vehicle from being mistakenly operated due to the vehicle control unit recording invalid fault states, and after the fault state is cleared, the cleared fault state is judged to avoid the fault state that does not meet the preset clearing conditions from being cleared, thereby avoiding frequent faults.

[0104] Embodiment 5

[0105] The embodiment of the application further provides a vehicle including a memory and a processor, the memory storing a computer program, and the processor being configured to run the computer program to execute the diagnosis method in the above-mentioned embodiments.

[0106] In the embodiment, the processor can be configured to execute the following steps by the computer program:

[0107] Step S1: obtaining fault information of the vehicle, the fault information at least including communication fault information of a target component of the vehicle.

[0108] Step S2: in a case where it is determined that the fault information meets preset identification conditions, recording a fault state of the current target component and a fault code corresponding to the fault state.

[0109] Step S3: performing fault processing on the target component based on the fault state and the fault code.

[0110] Step S4: in a case where it is determined that the fault state of the current target component is cleared, judging whether the current fault state meets preset clearing conditions and obtaining a judgment result.

[0111] Step S5: generating a fault response strategy based on the judgment result, wherein the fault response strategy includes at least one of a fault latching strategy and a fault clearing strategy, the fault latching strategy including maintaining the current fault state and maintaining the fault code corresponding to the current fault state, and the fault clearing strategy including clearing the current fault state and saving the fault code corresponding to the current fault state as a historical fault code to a target position.

[0112] In the embodiments of the present application, it is judged whether the obtained fault information meets preset identification conditions, and in a case where it is determined that the preset identification conditions are met, the fault state of the current target component and the fault code are recorded. For different fault states and fault codes, fault processing is performed to clear the fault of the current target component. After the fault state of the current target component is cleared, it is judged whether the cleared fault state meets preset clearing conditions and a judgment result is obtained. The vehicle control unit generates a fault response strategy based on the judgment result to latch the fault state and the fault code that are mistakenly cleared. The above-described diagnosis method judges and identifies the fault information to avoid the vehicle being mistakenly operated due to the vehicle control unit recording invalid fault states. After the fault state is cleared, the cleared fault state is judged to avoid the fault state that does not meet the preset clearing conditions being cleared, thereby causing frequent faults.

[0113] The above-mentioned serial numbers of the embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0114] In the above-described embodiments of the present application, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0115] In several embodiments provided in the present application, it should be understood that the disclosed technology can be implemented by other means. Among them, the above-mentioned device embodiments are only schematic, for example, the division of the units can be a logical function division, and actual implementation can have another division mode, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed each other can be indirect coupling or communication connection through some interface, unit or module, which can be electrical or other forms.

[0116] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or they can be distributed to multiple units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0117] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0118] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part of the prior art or the whole or part of the technical solutions can be embodied in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and various program codes that can be stored in the medium.

[0119] The above is only the preferred embodiment of the present application, and it should be pointed out that for ordinary skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, which should be considered as the protection scope of the present application.

Claims

1. A method of diagnosing a communication failure of a vehicle, characterized by, The method comprises the following steps: acquiring fault information of a vehicle, wherein the fault information at least comprises communication fault information of a target component of the vehicle; in a case where it is determined that the fault information meets preset identification conditions, recording a fault state of the target component at present and a fault code corresponding to the fault state; performing fault processing on the target component based on the fault state and the fault code; in a case where it is determined that the fault state of the target component at present is cleared, judging whether the fault state at present meets preset clearing conditions and obtaining a judgment result; generating a fault response strategy based on the judgment result, wherein the fault response strategy comprises at least one of a fault latching strategy and a fault clearing strategy, wherein the fault latching strategy comprises keeping the fault state at present and keeping the fault code corresponding to the fault state at present, and the fault clearing strategy comprises clearing the fault state at present and saving the fault code corresponding to the fault state at present as a historical fault code to a target position.

2. The diagnostic method according to claim 1, characterized in that, in a case where it is determined that the fault information meets preset identification conditions, recording the fault state of the target component at present and a fault corresponding to the fault state, comprising: judging whether a low-voltage power-on duration of the target component at present is greater than a preset duration; if yes, recording the fault state of the target component at present and the fault corresponding to the fault state.

3. The diagnostic method according to claim 1 or 2, characterized in that, in a case where it is determined that the fault information meets preset identification conditions, recording the fault state of the target component at present and a fault corresponding to the fault state, further comprising: judging whether a low-voltage power-on duration of the target component at present is greater than a preset duration; if yes, judging whether the target component at present is completed initialization; if yes, recording the fault state of the target component at present and the fault corresponding to the fault state.

4. The diagnostic method according to claim 1, characterized in that, generating a fault response strategy based on the judgment result, comprising: in a case where it is determined that the fault state at present is cleared, judging whether the fault state at present meets preset clearing conditions; if no, generating the fault latching strategy in the fault response strategy. judging whether the fault state at present meets preset clearing conditions, comprising:

5. The diagnostic method according to claim 4, characterized in that, judging whether a hibernation flag bit of a first target component in the target component is triggered, wherein the first target component comprises at least one of a battery management system and a motor control unit; if yes, generating the fault latching strategy in the fault response strategy. generating the fault latching strategy in the fault response strategy, comprising:

6. The diagnostic method according to claim 5, characterized in that, controlling a vehicle control unit to latch the fault state at present and the fault code corresponding to the fault state at present to the first target component from a hibernation time when the first target component enters hibernation to hibernation completion of the first target component. judging whether the fault state at present meets preset clearing conditions, comprising:

7. The diagnostic method according to claim 4, characterized in that, judging whether a low-voltage power-off flag bit of a second target component in the target component is triggered, wherein the second target component comprises at least one of an engine management system and a transmission control unit; if yes, generating the fault latching strategy in the fault response strategy. ​ 8. The diagnostic method according to claim 7, characterized in that, The fault latching strategy in the fault response strategy is generated, including: From the moment when the second target component is powered off under low voltage, the vehicle controller is controlled to latch the current fault state and the fault code corresponding to the current fault state to the second target component to complete the shutdown.

9. A diagnosis device for a communication failure of a vehicle, characterized by comprising: Including: An acquisition module is configured to acquire fault information of a vehicle, the fault information including at least communication fault information of a target component of the vehicle; A first judgment module is configured to, in a case where the fault information meets a preset identification condition, record a fault state of the target component and a fault code corresponding to the fault state; A fault processing module is configured to perform fault processing on the target component based on the fault state and the fault code; A second judgment module is configured to, in a case where the current fault state is cleared, judge whether the current fault state meets a preset clearing condition and obtain a judgment result; A generation module is configured to generate a fault response strategy based on the judgment result, wherein the fault response strategy includes at least one of a fault latching strategy and a fault clearing strategy, the fault latching strategy includes maintaining the current fault state and maintaining the fault code corresponding to the current fault state, and the fault clearing strategy includes clearing the current fault state and saving the fault code corresponding to the current fault state as a historical fault code to a target position. The computer storage medium includes a stored program, wherein the program controls the device where the computer storage medium is located to execute the diagnostic method of any one of claims 1-8 when the program is running.

10. A computer storage medium, characterized in that, The computer program is executed by the processor to implement the steps of the diagnostic method of any one of claims 1-8.

11. A computer program product comprising a computer program, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to execute the diagnostic method of any one of claims 1-8.

12. A vehicle comprising a memory and a processor, characterized in that The memory stores a computer program, and the processor is configured to run the computer program to execute the diagnostic method of any one of claims 1-8.

Images