CN116736834A - Fault analysis method, controller and vehicle - Google Patents
Fault analysis method, controller and vehicle Download PDFInfo
- Publication number
- CN116736834A CN116736834A CN202310868561.2A CN202310868561A CN116736834A CN 116736834 A CN116736834 A CN 116736834A CN 202310868561 A CN202310868561 A CN 202310868561A CN 116736834 A CN116736834 A CN 116736834A
- Authority
- CN
- China
- Prior art keywords
- fault
- vehicle
- user
- information
- analysis
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004458 analytical method Methods 0.000 title claims abstract description 68
- 238000000034 method Methods 0.000 claims abstract description 46
- 238000012795 verification Methods 0.000 claims abstract description 38
- 230000008569 process Effects 0.000 claims abstract description 28
- 230000004044 response Effects 0.000 claims abstract description 8
- 230000003213 activating effect Effects 0.000 claims abstract description 6
- 238000012423 maintenance Methods 0.000 claims description 35
- 230000003993 interaction Effects 0.000 claims description 22
- 230000008439 repair process Effects 0.000 claims description 12
- 230000036541 health Effects 0.000 claims description 9
- 230000000875 corresponding effect Effects 0.000 description 15
- 238000004092 self-diagnosis Methods 0.000 description 7
- 239000007788 liquid Substances 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000003745 diagnosis Methods 0.000 description 3
- 239000000446 fuel Substances 0.000 description 3
- 208000024891 symptom Diseases 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000002347 injection Methods 0.000 description 2
- 239000007924 injection Substances 0.000 description 2
- 230000007257 malfunction Effects 0.000 description 2
- 238000013021 overheating Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000005299 abrasion Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005286 illumination Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000000243 solution Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
- G05B23/0262—Confirmation of fault detection, e.g. extra checks to confirm that a failure has indeed occurred
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24065—Real time diagnostics
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
Abstract
The application discloses a fault analysis method, a controller and a vehicle, so as to provide a user with vehicle fault analysis service. The method comprises the following steps: responding to a vehicle fault analysis request, reading a fault code of a vehicle, analyzing according to the fault code to obtain fault information of the vehicle, and outputting the fault information; the fault information comprises fault content and at least one possible cause of the fault; and in response to the fact that one possible reason is selected by the user, activating a fault verification process corresponding to the selected possible reason, guiding the user to operate the vehicle to perform fault verification by the fault verification process, and updating the fault information according to a verification result.
Description
Technical Field
The present application relates to the field of vehicle fault diagnosis technologies, and in particular, to a fault analysis method, a controller, and a vehicle.
Background
Fault type indicator lights on the dashboard of automobiles typically include engine fault lights, ESP (Electronic Stability Program, body electronic stability system) fault lights, ABS (Antilock Brake System, anti-lock braking system) fault lights, and the like. When the fault type indicator lights are turned on, it indicates that the related electronic control system on the vehicle has failed, but for users not familiar with automobile knowledge, it cannot clearly know the fault information of the vehicle, such as the fault content and possible cause of the fault, etc., according to the turned-on fault type indicator lights and the concrete symptoms of the vehicle, and further cannot determine how the treatment should be performed.
Disclosure of Invention
In view of this, the present application provides a failure analysis method, a controller, and a vehicle to realize providing a user with a vehicle failure analysis service.
A fault analysis method comprising:
responding to a vehicle fault analysis request, reading a fault code of a vehicle, analyzing according to the fault code to obtain fault information of the vehicle, and outputting the fault information; the fault information comprises fault content and at least one possible cause of the fault;
and in response to the fact that one possible reason is selected by the user, activating a fault verification process corresponding to the selected possible reason, guiding the user to operate the vehicle to perform fault verification by the fault verification process, and updating the fault information according to a verification result.
Optionally, the responding to the vehicle fault analysis request includes: responding to a vehicle fault analysis request received by the vehicle-mounted man-machine interaction equipment;
the outputting the fault information includes: outputting the fault information through the vehicle-mounted man-machine interaction equipment;
said responding to one of said possible reasons being selected by the user comprises: one of the possible reasons is selected by a user in response to being displayed on the in-vehicle human-machine interaction device.
Optionally, according to whether the user is supported to select, the states of the possible reasons are divided into a selectable state and an unselected state; the possible reasons for matching the faulty verification process are in a selectable state, and the possible reasons for not matching the faulty verification process are in a non-selectable state.
Optionally, after obtaining the fault content and the possible cause of the fault according to the fault code analysis, the method further comprises:
judging whether a plurality of electronic control systems exist on the vehicle or not, if so, judging that the same possible reason is one of the real reasons for causing the faults of the plurality of electronic control systems, and adding the judging result into the fault information.
Optionally, the fault information further includes a vehicle health index and a repair recommendation.
Optionally, the repair advice includes: and giving suggested maintenance modes according to the current vehicle health index, wherein the maintenance modes at least comprise two maintenance modes of store maintenance and parking waiting for rescue.
Optionally, when the suggested maintenance mode is the store-arriving maintenance, the maintenance suggestion further includes: outputting an optimal maintenance point, estimated maintenance cost and estimated maintenance time through the vehicle-mounted human-computer interaction equipment;
after the fault information of the vehicle is obtained according to the fault code analysis, the method further comprises the following steps: and pushing the fault information to the optimal maintenance point.
Optionally, the fault information further includes: the name of the fault class indicator that is illuminated due to the current fault.
A fault analysis controller comprising a processor and a memory, the memory having stored thereon a program which when executed by the processor implements any of the fault analysis methods as disclosed above.
A vehicle, comprising: such as the fault analysis controller disclosed above.
According to the technical scheme, the fault code of the vehicle is read, and the popular and easily understood vehicle fault information is automatically analyzed based on the fault code, so that even a non-professional person can clearly know the current fault content of the vehicle, the possible cause of the fault and the like. In addition, in order to facilitate the user to further lock the real cause of the fault, improve the fault checking efficiency and more accurately determine the severity of the fault of the vehicle, the application also supports the user to operate the vehicle to verify whether some possible causes of the fault are the real causes of the fault.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a fault analysis method disclosed in an embodiment of the present application;
FIG. 2 is a schematic diagram of a communication mode of a fault analysis controller according to an embodiment of the present application;
FIG. 3 is a flow chart of another fault analysis method according to an embodiment of the present application;
FIG. 4 is a flow chart of another fault analysis method according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a fault analysis controller according to an embodiment of the present application.
Detailed Description
For purposes of reference and clarity, technical terms, abbreviations or abbreviations used hereinafter are summarized as follows:
EECS: engine Electrical Control System, an engine electronic control system;
IBC: integrated Brake Control, an integrated brake control system;
and (3) ECU: electronic Control Unit, an electronic control unit;
ESP: electronic Stability Program, a body electronic stability system;
EPB: electrical Park Brak, electronic parking brake system;
ABS: antilock Brake System, braking an antilock system;
HUT: head Unit, multimedia host.
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Referring to fig. 1, an embodiment of the present application discloses a fault analysis method, including:
step S01: responding to a vehicle fault analysis request, reading a fault code of a vehicle, analyzing according to the fault code to obtain fault information of the vehicle, and outputting the fault information; the fault information comprises fault content and at least one possible cause of the fault; after that, the process advances to step S02.
In particular, automobiles have many electronic control systems, such as EECS systems, IBC systems, self-adjusting seating systems, anti-theft systems, entertainment systems, and the like. The electronic control system of the automobile is generally composed of three parts in terms of hardware structure: sensors, ECU and actuators. When the automobile runs, each sensor in the automobile electronic control system continuously detects the working condition information of the automobile running and transmits the information to the ECU in real time, when the ECU receives the information, corresponding decision making and processing are carried out according to a control program which is written in advance in the ECU, a control signal is output to a corresponding actuator, and the actuator executes corresponding actions after receiving the control signal, so that the preset function is realized. For example, an ECU in the EECS system controls the air-fuel ratio and ignition timing of the fuel injection engine by an actuator, and controls auxiliary functions such as engine start, idle speed, limit speed, exhaust gas recirculation, cylinder closing operation, secondary air injection, intake charge, knocking, generator output voltage, electric fuel pump, and system self-diagnosis.
The ECU in the electronic control system of the automobile generally has a fault self-diagnosis function, specifically: the ECU judges whether the electric components such as a sensor, the ECU, an actuator and the like in the automobile electronic control system run or not according to signals transmitted in the automobile electronic control system, and the running faults of the electric components are stored in a memory in the ECU in the form of fault codes. The fault codes can be read by a maintenance technician by using a diagnostic instrument so as to be displayed, each fault code has specific fault content, and the content of the fault codes can basically prompt the maintenance technician with a basic diagnosis idea.
In most cases, the failure type indicator light illumination is an external indication of the presence of a fault code. Fault type indicator lights on the dashboard of automobiles typically include engine fault lights, ESP fault lights, ABS fault lights, active turn lights, and the like. When the fault type indicator lights are lighted, the fault type indicator lights which correspond to the electronic control systems of the automobile are lighted, which indicates that the related electronic control systems on the automobile have faults, but the types of faults which can occur to the electronic control systems of the automobile are very large, and any fault occurrence can lead to the lighting of the fault type indicator lights which correspond to the electronic control systems of the automobile. For users who are not familiar with automobile knowledge, the current fault information (such as fault content, possible reasons for causing faults and the like) of the automobile cannot be clearly known according to the specific symptoms of the lighted fault type indicator lamp and the automobile, and further, how to process the fault information cannot be determined (such as whether the automobile can continue driving or can only be stopped for waiting for rescue, and the fault of non-main parts basically has no influence on the normal operation of the automobile and can be continued).
For example, taking IBC systems as an example, the types of faults that may occur are five major categories 1) to 5):
1) ESP/IBC hardware failure, specifically includes: ECU failure, valve relay failure, return pump failure, front left outlet valve failure, front right outlet valve failure, rear left outlet valve failure, rear right outlet valve failure, front left inlet valve failure, rear right inlet valve failure, rear left inlet valve failure, rear right inlet valve failure, high pressure valve failure, loop valve failure, EPB circuit failure.
For hardware failures, maintenance technicians are typically required to deal with, and to immediately enter the 4S store to replace new hardware, possible causes of the failure are system overheating, damage due to overcurrent, and fuse damage or poor contact, which can cause the ABS and ESP fault lamps to light.
2) The power failure specifically includes: the sensor is powered by short circuit, short circuit to ground, open circuit, ECU over voltage, under voltage.
For power failure, whether the voltage is within the standard value range of 9V-16V is checked, and the high-power electric appliance on the vehicle is turned on and off to observe whether the voltage fluctuation is within the normal working range.
3) The input/output faults specifically include: the signals of the left front wheel speed sensor, the right front wheel speed sensor, the left rear wheel speed sensor and the right rear wheel speed sensor are short-circuited to a power supply, short-circuited to ground and broken, loose in connection and broken, and the EPB key circuit is wrong.
Possible causes of wheel speed signal failure are: the wire harness of the wheel speed sensor is bent, the plugging is loose and broken; the gear ring lacks teeth, foreign matters exist on the gear ring, and the gear ring is eccentric; the air gap between the sensor and the gear ring is too large; the wheel speed sensor body fails; wheel speed failure can cause ABS and ESP, engine failure lamps to light.
4) The CAN network fault specifically comprises the following steps: bus failure, network node signal loss, error, damage (longitudinal sensor error, lateral sensor error, yaw rate sensor error, steering wheel angle signal error), network node verification error;
for network signal faults, line connection needs to be checked, and power supply is poor due to hardware faults.
5) The system fault specifically comprises: the system has the advantages of functional failure, abnormal control of the ABS/ESP, error reliability of a brake signal and overheating of a brake pad.
Possible causes of system failure are: the wheel speed signal is inaccurate when the vehicle is driven continuously or the brake is used continuously for a long time. This failure causes the ABS and ESP fault lamps to illuminate.
As can be seen from the above examples of the types of faults that may occur to the IBC system, the types of faults that may occur to the electronic control system of the automobile are very many, and a fault of a device in one electronic control system may cause the lighting of fault indication lamps corresponding to other electronic control systems, so it is generally difficult for a user (mainly a driver) to clearly determine fault information of the vehicle, such as fault content and possible causes of the fault, simply by the lighting of the fault indication lamps and the concrete symptoms of the vehicle.
In order to enable a user to know the fault information of the vehicle relatively clearly when the vehicle faults occur, the fault code recorded when each ECU of the vehicle performs fault self-diagnosis is read, and popular and easily understood vehicle fault information is automatically analyzed based on the fault code, so that even a non-professional person can know the current fault content of the vehicle and possible reasons for causing the fault clearly. Taking an example that an active steering lamp and an ESP lamp are turned on after a certain vehicle performs fault self-diagnosis, and a fault code '00778' is recorded (the fault code '00778' indicates that a steering angle sensor is damaged, the turning angle sensor damage can cause the turning on of the active steering lamp and possibly be accompanied by the turning on of the ESP lamp), the following fault information is obtained by analyzing the fault code '00778', and the fault information is fed back to a user: the fault content is damage of the steering angle sensor; possible causes of the fault are that the steering angle sensor is not installed at the correct position, the chassis is positioned inaccurately, and the steering gear vibrates too much due to abrasion.
Step S02: and in response to the fact that one possible reason is selected by the user, activating a fault verification process corresponding to the selected possible reason, guiding the user to operate the vehicle to perform fault verification by the fault verification process, and updating the fault information according to a verification result.
Specifically, when a certain fault occurs, the possible reasons for the fault may be multiple, so that the user can conveniently further lock the real reasons for the fault, the user can operate the vehicle to verify whether certain possible reasons are real reasons, and the verification result is displayed, so that the driver can conveniently and accurately determine the fault severity of the vehicle, and the information can also be pushed to a maintenance technician in advance before the vehicle is maintained, so that the maintenance technician can more quickly lock the fault point and further quickly maintain the vehicle.
For example, assuming that the vehicle failure analysis request is received through a vehicle-mounted man-machine interaction device, failure information of a vehicle is output through the vehicle-mounted man-machine interaction device, and a user selects one possible cause on the vehicle-mounted man-machine interaction device, at this time: when the fault content corresponding to the fault code indicates that the left front liquid outlet valve has a fault, in order to verify whether the left front liquid outlet valve has a fault or a fault caused by the surrounding environment, a user can click a corresponding fault verification button on the vehicle-mounted man-machine interaction device, activate a preset left front liquid outlet valve fault verification process, display a test environment on the vehicle-mounted man-machine interaction device, enable the vehicle to enter an IBC diagnosis expansion session, send a liquid outlet valve closing instruction, then instruct the user to control the vehicle to run in a straight line and control the vehicle speed to be 5km/h, then instruct the user to step on a brake pedal, then the vehicle can automatically judge whether the left front liquid outlet valve has a fault according to the wheel speed, and a verification result is displayed through the vehicle-mounted man-machine interaction device so as to be convenient for the user to check.
The fault content corresponding to the fault code and possible reasons for causing the fault are pre-established and stored in the database, and the fault verification flow and the like are directly called from the database when in use. The fault analysis method is controlled and executed by a controller, particularly a fault analysis controller, the fault analysis controller is communicated with a vehicle fault self-diagnosis system controller, vehicle-mounted man-machine interaction equipment and the like, and the fault analysis method is executed when a vehicle fault analysis request is received. The fault analysis controller and the vehicle fault self-diagnosis system controller can generally adopt a vehicle remote controller, the database is a local database of the fault analysis controller, and the fault analysis controller is communicated with the vehicle fault self-diagnosis system controller, the vehicle-mounted man-machine interaction device and the like through a wireless network, as shown in fig. 2.
In order to avoid distraction of a driver in checking the outputted fault information during the driving of the vehicle, the embodiment of the application recommends that the fault analysis method is executed after the power-on and before the driving of the vehicle, namely, the fault analysis request of the vehicle is preferably issued to the controller after the power-on and before the driving of the vehicle. The vehicle fault analysis request can be automatically sent according to a preset program or manually triggered by a user through the vehicle-mounted man-machine interaction device (for example, the user presses a vehicle fault analysis button on the vehicle-mounted man-machine interaction device to send the vehicle fault analysis request), and the vehicle fault analysis request is recommended to the user, so that the user can automatically select whether to start the function service.
In addition, for possible reasons for causing the fault, not all possible reasons need to preset corresponding fault verification processes, and the method can be determined according to actual conditions, and only the corresponding fault verification processes are usually preset for hardware faults. Correspondingly, according to whether the user is supported to select, the states of the possible reasons are divided into a selectable state and an unselected state; the possible reasons for matching the faulty verification process are in a selectable state, and the possible reasons for not matching the faulty verification process are in a non-selectable state. For example, a possible reason for a selectable state is under-underlined with a web page link, while a possible reason for a non-selectable state is under-underlined with no web page link.
Optionally, based on any one of the embodiments disclosed above, after obtaining the fault content and the possible cause of the fault according to the fault code analysis, the method further includes: judging whether a plurality of electronic control systems exist on the vehicle or not, if so, judging that the same possible reason is one of the real reasons for causing the faults of the plurality of electronic control systems, and adding the judging result into the fault information. The corresponding fault analysis method is shown in fig. 3, and includes:
step S11: responding to a vehicle fault analysis request, reading a fault code of a vehicle, analyzing according to the fault code to obtain fault information of the vehicle, and outputting the fault information; the fault information comprises fault content and at least one possible cause of the fault; and then proceeds to step S12.
Step S12: judging whether a plurality of electronic control systems exist on the vehicle for the same possible reason, if so, entering step S13; if not, the process proceeds to step S14.
Step S13: and determining that the same one of the possible causes is one of the actual causes that cause the plurality of electronic control system failures, and adding the determination result to the failure information, and then proceeding to step S15.
Step S14: it is determined that the same one of the possible causes is not one of the actual causes that cause the malfunction of the plurality of electronic control systems, and the determination result is added to the malfunction information, after which the flow proceeds to step S15.
Step S15: and in response to the fact that one possible reason is selected by the user, activating a fault verification process corresponding to the selected possible reason, guiding the user to operate the vehicle to perform fault verification by the fault verification process, and updating the fault information according to a verification result.
For example, to facilitate the user to further lock the real cause of the fault, more than 3 electronic control systems can be compared to verify whether the same possible cause of the fault exists, such as voltage undervoltage or voltage, and whether the fault is a power problem can be checked by comparing, and the specific analysis is as follows: when a certain electronic control system has a certain fault, the possible reasons for the fault are many, and the determination method is designed by manually checking and testing to determine which one or more of the possible reasons are the 'real reasons' for the fault: if a possible cause of the fault exists in a plurality of electronic control systems at the same time, it is stated that the possible cause is a vehicle-level fault cause (such as power supply undervoltage/overvoltage for supplying power to all electronic control systems, and each electronic control system has a fault caused by the power supply undervoltage/overvoltage cause) which causes the fault, and it belongs to a "real cause" for causing the fault, otherwise, the possible cause can be excluded from belonging to a "real cause" for causing the fault; finally, the judging result of whether one possible cause of the current judgment belongs to the 'real cause' of the fault is output, so that the user can further lock the real cause of the fault conveniently.
Optionally, based on any embodiment disclosed above, the fault information further includes: the name of the fault type indicator lamp that is lit due to the current fault (i.e., the fault type indicator lamp that is in the lit state at the present stage among all the fault type indicator lamps mounted on the vehicle). By the method, a user can clearly know why the currently-lighted fault type indicator lights on the vehicle are lighted, and confusion or panic cannot be caused by suddenly lighting certain fault type indicator lights.
Optionally, based on any of the embodiments disclosed above, the fault information further includes a vehicle health index and a repair recommendation. The vehicle health index refers to a relative data that can reflect the health condition of the vehicle after the comprehensive calculation of all the faults of the vehicle, for example, the fault analysis method shown in fig. 4 includes:
step S21: responding to a vehicle fault analysis request, reading a fault code of a vehicle, analyzing according to the fault code to obtain fault information of the vehicle, and outputting the fault information; the fault information comprises fault content, possible reasons for causing faults, names of fault type indicator lights which are lightened due to the current faults, vehicle health indexes and maintenance suggestions; after that, the process advances to step S22.
Step S22: and in response to the fact that one possible reason is selected by the user, activating a fault verification process corresponding to the selected possible reason, guiding the user to operate the vehicle to perform fault verification by the fault verification process, and updating the fault information according to a verification result.
The service recommendation may include: and giving suggested maintenance modes according to the current vehicle health index, wherein the maintenance modes at least comprise two maintenance modes of store maintenance and parking waiting for rescue. If the vehicle is still driving, suggesting a store repair; if the vehicle is extremely serious in fault and is not allowed to continue driving, the vehicle is stopped for rescue.
Wherein when the suggested repair mode is the store-arriving repair, the repair suggestion may further include: outputting an optimal maintenance point, estimated maintenance cost and estimated maintenance time through the vehicle-mounted human-computer interaction equipment;
after the fault information of the vehicle is obtained according to the fault code analysis, the method further comprises the following steps: and pushing the fault information to the optimal maintenance point.
By performing the fault analysis based on the fault code of the vehicle, the driver is not confused with a plurality of serious fault type indicator lamps, and the possible practical reasons are caused by the loosening of a small part, so that the psychological expectation is also provided for maintenance and repair cost.
Optionally, based on any embodiment disclosed above, the fault information is displayed in a classified summary and classified display, so that the fault information is convenient for a user to check. For example, the first stage only displays the faulty electronic control system, and the second stage displays fault information inside the different electronic control system and possible causes of the fault.
Optionally, based on any embodiment disclosed above, the vehicle-mounted human-computer interaction device includes a HUT, and is not limited. In addition, the vehicle-mounted man-machine interaction device can be replaced by an intelligent device which is carried by a user and is pre-bound with the vehicle, such as a smart phone, a smart watch and the like, and the vehicle-mounted man-machine interaction device is not limited.
Corresponding to the above method embodiment, the embodiment of the present application also discloses a fault analysis controller, as shown in fig. 5, including a processor and a memory, where the memory stores a program, and when the program is executed by the processor, the program implements any of the fault analysis methods disclosed above.
Optionally, the fault analysis controller is a vehicle remote controller.
In addition, the embodiment of the application also discloses a vehicle, which comprises the following components: such as the fault analysis controller disclosed above.
In the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, and identical and similar parts between the embodiments are all enough to refer to each other. For the fault analysis controller and the vehicle disclosed in the embodiments, the description is relatively simple because the fault analysis controller and the vehicle correspond to the methods disclosed in the embodiments, and the relevant points are only referred to in the description of the method section.
The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar different objects and not necessarily for describing a particular sequential or chronological order. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the embodiments of the application. Thus, the present embodiments are not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method of fault analysis, comprising:
responding to a vehicle fault analysis request, reading a fault code of a vehicle, analyzing according to the fault code to obtain fault information of the vehicle, and outputting the fault information; the fault information comprises fault content and at least one possible cause of the fault;
and in response to the fact that one possible reason is selected by the user, activating a fault verification process corresponding to the selected possible reason, guiding the user to operate the vehicle to perform fault verification by the fault verification process, and updating the fault information according to a verification result.
2. The method of claim 1, wherein said responding to a vehicle failure analysis request comprises: responding to a vehicle fault analysis request received by the vehicle-mounted man-machine interaction equipment;
the outputting the fault information includes: outputting the fault information through the vehicle-mounted man-machine interaction equipment;
said responding to one of said possible reasons being selected by the user comprises: one of the possible reasons is selected by a user in response to being displayed on the in-vehicle human-machine interaction device.
3. The fault analysis method according to claim 1 or 2, wherein the states of the possible causes are classified into a selectable state and a non-selectable state according to whether or not the selection by the user is supported; the possible reasons for matching the faulty verification process are in a selectable state, and the possible reasons for not matching the faulty verification process are in a non-selectable state.
4. The fault analysis method according to claim 1 or 2, wherein after obtaining the fault content and the possible cause of the fault according to the fault code analysis, the fault analysis method further comprises:
judging whether a plurality of electronic control systems exist on the vehicle or not, if so, judging that the same possible reason is one of the real reasons for causing the faults of the plurality of electronic control systems, and adding the judging result into the fault information.
5. The fault analysis method according to claim 1 or 2, wherein the fault information further includes a vehicle health index and a repair advice.
6. The fault analysis method of claim 5, wherein the repair advice comprises: and giving suggested maintenance modes according to the current vehicle health index, wherein the maintenance modes at least comprise two maintenance modes of store maintenance and parking waiting for rescue.
7. The method of claim 6, wherein when the suggested maintenance is the arrival repair, the repair suggestion further includes: outputting an optimal maintenance point, estimated maintenance cost and estimated maintenance time through the vehicle-mounted human-computer interaction equipment;
after the fault information of the vehicle is obtained according to the fault code analysis, the method further comprises the following steps: and pushing the fault information to the optimal maintenance point.
8. The fault analysis method according to claim 1 or 2, wherein the fault information further includes: the name of the fault class indicator that is illuminated due to the current fault.
9. A fault analysis controller comprising a processor and a memory, the memory having stored thereon a program which when executed by the processor implements the fault analysis method of any of claims 1 to 8.
10. A vehicle, characterized by comprising: the fault analysis controller of claim 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310868561.2A CN116736834A (en) | 2023-07-14 | 2023-07-14 | Fault analysis method, controller and vehicle |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310868561.2A CN116736834A (en) | 2023-07-14 | 2023-07-14 | Fault analysis method, controller and vehicle |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116736834A true CN116736834A (en) | 2023-09-12 |
Family
ID=87918634
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310868561.2A Pending CN116736834A (en) | 2023-07-14 | 2023-07-14 | Fault analysis method, controller and vehicle |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116736834A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117647924A (en) * | 2023-12-29 | 2024-03-05 | 上海同驭汽车科技有限公司 | Fault-tolerant control method and system for fault signals |
| CN117647924B (en) * | 2023-12-29 | 2024-11-19 | 上海同驭汽车科技有限公司 | Fault-tolerant control method and system for fault signals |
-
2023
- 2023-07-14 CN CN202310868561.2A patent/CN116736834A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117647924A (en) * | 2023-12-29 | 2024-03-05 | 上海同驭汽车科技有限公司 | Fault-tolerant control method and system for fault signals |
| CN117647924B (en) * | 2023-12-29 | 2024-11-19 | 上海同驭汽车科技有限公司 | Fault-tolerant control method and system for fault signals |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP3568540B2 (en) | Diagnostic device for testing automotive subsystems | |
| CN102262404B (en) | End-of-line configuration system and configuration method for finished vehicle | |
| US5003477A (en) | Diagnosis system for a motor vehicle | |
| EP0286648B2 (en) | System for diagnosing anomalies or breakdowns in a plurality of types of electronic control systems installed in motor vehicles | |
| JP6310332B2 (en) | Vehicle diagnostic machine and vehicle diagnostic method | |
| CN102393733B (en) | Failure diagnosis method, fault diagnosis instrument and system thereof, new energy automobile | |
| JPH0481138B2 (en) | ||
| US4623974A (en) | Method and apparatus for self-monitoring of microcomputer-controlled network devices in particular in motor vehicles | |
| EP2799834A1 (en) | Vehicle diagnostic system, vehicle diagnostic method, and vehicle | |
| EP2799833A1 (en) | Vehicle diagnostic system, vehicle diagnostic method, and external diagnostic device | |
| US7231285B2 (en) | Data recording apparatus and data recording method | |
| ITMI20002295A1 (en) | METHOD AND SYSTEM FOR DIAGNOSTICING A VEHICLE'S FAULTS | |
| CN109164789A (en) | A kind of in-vehicle multi-media system for information of vehicles diagnosis | |
| US6442458B2 (en) | Method and apparatus for diagnosing a vehicle | |
| CN111267756B (en) | Vehicle speed limit control method, vehicle and medium | |
| JP6310331B2 (en) | Data collection apparatus and data collection method for vehicle diagnosis | |
| CN116736834A (en) | Fault analysis method, controller and vehicle | |
| KR100762096B1 (en) | A fuel efficiency measurement and trouble diagnostic apparatus for vehicle and the method thereof | |
| KR20130008702A (en) | Apparatus for monitoring vehicles | |
| CN115701398A (en) | Control method and device for collecting brake signals, redundancy setting system and vehicle | |
| US20040093136A1 (en) | Control unit for a vehicle | |
| JP2002106408A (en) | Electronic controller for vehicle | |
| US20200347759A1 (en) | Apparatus and method for controlling cluster of vehicle | |
| JPH11184762A (en) | Device for diagnosing backup ram system of controller for automobile | |
| CN109204135A (en) | A kind of dynamic steering lamp system and its control method and its method for diagnosing faults |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |