WO2019205858A1 - 车辆诊断方法、装置及设备 - Google Patents

车辆诊断方法、装置及设备 Download PDF

Info

Publication number
WO2019205858A1
WO2019205858A1 PCT/CN2019/079556 CN2019079556W WO2019205858A1 WO 2019205858 A1 WO2019205858 A1 WO 2019205858A1 CN 2019079556 W CN2019079556 W CN 2019079556W WO 2019205858 A1 WO2019205858 A1 WO 2019205858A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
vehicle
symptom information
target
information
Prior art date
Application number
PCT/CN2019/079556
Other languages
English (en)
French (fr)
Inventor
阳岳喜
于超超
Original Assignee
深圳市道通科技股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 深圳市道通科技股份有限公司 filed Critical 深圳市道通科技股份有限公司
Publication of WO2019205858A1 publication Critical patent/WO2019205858A1/zh

Links

Images

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/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
    • G05B23/0224—Process history based detection method, e.g. whereby history implies the availability of large amounts of data
    • G05B23/0227—Qualitative history assessment, whereby the type of data acted upon, e.g. waveforms, images or patterns, is not relevant, e.g. rule based assessment; if-then decisions
    • 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/0275—Fault isolation and identification, e.g. classify fault; estimate cause or root of failure
    • G05B23/0278—Qualitative, e.g. if-then rules; Fuzzy logic; Lookup tables; Symptomatic search; FMEA

Definitions

  • the present application relates to the field of automobile fault diagnosis technology, and in particular, to a vehicle diagnosis method, device and device.
  • the diagnostic process of vehicle diagnostic instruments on the market is generally: first determine the vehicle model, then perform fault code scanning, data stream reading, etc. Finally, manually determine the fault problem by manually analyzing the fault code and data flow output by the diagnostic instrument. .
  • the existing vehicle diagnostic instrument requires a large number of fault code scans and data stream communication for the vehicle, and the diagnostic efficiency is low, and the obtained diagnosis result is difficult to accurately locate the fault problem, so the experience and ability of the maintenance personnel. Have higher requirements.
  • Embodiments of the present invention provide a vehicle diagnosis method, apparatus, and device to simplify a vehicle diagnosis process and improve reliability of a vehicle diagnosis result.
  • an embodiment of the present invention provides a vehicle diagnosis method, including:
  • a solution corresponding to the target failure problem is determined.
  • the method further includes:
  • Determining a target failure problem according to the fault symptom information of the vehicle including:
  • a target failure problem is determined based on the vehicle information of the vehicle and the fault symptom information.
  • the acquiring vehicle information of the vehicle includes:
  • Vehicle information of the vehicle is acquired from an electronic control unit ECU of the vehicle.
  • the acquiring fault symptom information of the vehicle includes:
  • the acquiring fault symptom information related to the fault description information according to the fault description information includes:
  • the method further includes:
  • the fault symptom information selected by the user from the at least two fault symptom information is used as the fault symptom information of the vehicle.
  • the acquiring fault symptom information of the vehicle includes:
  • the fault symptom information selected by the user from the historical fault symptom information and/or the common fault symptom information is used as the fault symptom information of the vehicle.
  • the determining the target fault problem according to the fault symptom information of the vehicle includes:
  • the target failure problem is determined from a failure problem related to the failure symptom information of the vehicle.
  • the determining a target fault problem from the fault problem related to the fault symptom information of the vehicle includes:
  • the target fault problem is determined according to the degree of matching between the fault phenomenon occurring in the vehicle and the fault phenomenon included in the fault problem.
  • the method before the determining the target fault problem according to the matching degree of the fault phenomenon and the fault symptom information, the method further includes:
  • a fault phenomenon occurring in the vehicle is determined according to a selection operation of the user for the fault phenomenon.
  • the method before the determining the target fault problem according to the matching degree of the fault phenomenon and the fault symptom information, the method further includes:
  • a fault phenomenon occurring in the vehicle is determined according to the fault data.
  • the determining a target fault problem from the fault problem related to the fault symptom information of the vehicle includes:
  • the target failure problem among the at least two failure problems is determined according to the priority of the at least two failure problems.
  • the determining a solution corresponding to the target fault problem includes:
  • the method further includes:
  • the method further includes:
  • the displaying a solution corresponding to the target failure problem includes:
  • the relevance of the solution to the target failure problem is determined according to a historical solution result of the solution solving the target failure problem.
  • the method further includes:
  • the target solution in at least two solutions is selected according to the user's selection operation for the solution.
  • the method further includes:
  • a next diagnostic step associated with the diagnostic data and/or the diagnostic result is displayed.
  • the method further includes:
  • an embodiment of the present invention provides a vehicle diagnostic apparatus, including:
  • a determining module configured to determine a target fault problem according to the fault symptom information of the vehicle
  • a determination module is also used to determine a solution corresponding to the target failure problem.
  • the acquiring module is further configured to acquire vehicle information of the vehicle;
  • the determining module is specifically configured to:
  • a target failure problem is determined based on the vehicle information of the vehicle and the fault symptom information.
  • the acquiring module is specifically configured to: receive vehicle information of the vehicle input by a user; or
  • Vehicle information of the vehicle is acquired from an electronic control unit ECU of the vehicle.
  • the acquiring module is specifically configured to:
  • the acquiring fault symptom information related to the fault description information according to the fault description information includes:
  • the device further includes:
  • a display module configured to display the at least two fault symptom information for selection by the user when determining at least two fault symptom information related to the fault description information
  • the fault symptom information selected by the user from the at least two fault symptom information is used as the fault symptom information of the vehicle.
  • the acquiring module is further configured to:
  • the fault symptom information selected by the user from the historical fault symptom information and/or the common fault symptom information is used as the fault symptom information of the vehicle.
  • the determining module is specifically configured to:
  • the target failure problem is determined from a failure problem related to the failure symptom information of the vehicle.
  • the determining a target fault problem from the fault problem related to the fault symptom information of the vehicle includes:
  • the target fault problem is determined according to the degree of matching between the fault phenomenon occurring in the vehicle and the fault phenomenon included in the fault problem.
  • the display module is further configured to display the fault phenomenon before determining a target fault problem according to the matching degree of the fault phenomenon and the fault symptom information;
  • a fault phenomenon occurring in the vehicle is determined according to a selection operation of the user for the fault phenomenon.
  • the acquiring module is further configured to: acquire fault data from an ECU of the vehicle before determining a target fault problem according to a matching degree of the fault phenomenon and the fault symptom information;
  • a fault phenomenon occurring in the vehicle is determined according to the fault data.
  • the determining module is specifically configured to:
  • the target failure problem among the at least two failure problems is determined according to the priority of the at least two failure problems.
  • the determining module is specifically configured to:
  • the device further includes:
  • a display module for displaying a solution corresponding to the target failure problem.
  • the display module is further configured to: before the solution corresponding to the target fault problem is displayed, perform a solution corresponding to the target fault problem according to a correlation between the solution and the target fault problem Sort to get the sort result;
  • the relevance of the solution to the target failure problem is determined according to a historical solution result of the solution solving the target failure problem.
  • the determining module is further configured to: after displaying the solution corresponding to the target fault problem, when the number of solutions corresponding to the target fault problem is at least two, according to the user for the solution Select the target solution in at least 2 solutions.
  • the display module is further configured to:
  • a next diagnostic step associated with the diagnostic data and/or the diagnostic result is displayed.
  • the device further includes:
  • a storage module configured to obtain a new solution corresponding to the target failure problem according to a modification operation of the solution by the user; and save the new solution.
  • an embodiment of the present invention provides a vehicle diagnostic apparatus, including:
  • the memory stores a computer program
  • the processor invokes the computer program to perform the method of any of the first aspects.
  • an embodiment of the present invention provides a vehicle diagnosis system, including: a diagnostic device and/or a server.
  • the diagnostic apparatus and/or server is for performing the method of any of the first aspects.
  • an embodiment of the present invention provides a computer readable storage medium, comprising: a computer program, when run on a computer, causing the computer to perform the method of any one of the first aspects.
  • the vehicle diagnosis method, device and device provided by the embodiments of the present invention acquire fault symptom information of the vehicle; determine a target fault problem according to the fault symptom information of the vehicle; and determine a solution corresponding to the target fault problem.
  • the method of the invention it is not necessary to comprehensively detect the vehicle, the fault code and the data flow acquisition range are reduced, the diagnosis efficiency is high, and the vehicle can be directly diagnosed according to the fault symptom information, which not only simplifies the diagnosis process but also makes the diagnosis The result is more reliable and comprehensive, and has wide applicability.
  • FIG. 1 is a schematic diagram showing the principle of establishing a communication connection between a vehicle diagnostic device and a vehicle;
  • FIG. 2 is a flowchart of a vehicle diagnosis method according to Embodiment 1 of the present invention.
  • FIG. 3 is a schematic diagram of a prompt list with an application of the fault description information “unbalanced”;
  • FIG. 4 is a flowchart of a vehicle diagnosis method according to Embodiment 2 of the present invention.
  • FIG. 5 is a schematic structural diagram of a vehicle diagnosis apparatus according to Embodiment 3 of the present invention.
  • FIG. 6 is a schematic structural diagram of a vehicle diagnosis apparatus according to Embodiment 4 of the present invention.
  • FIG. 7 is a schematic structural diagram of a vehicle diagnosis system according to Embodiment 5 of the present invention.
  • FIG. 8 is a schematic structural diagram of a vehicle diagnosis apparatus according to Embodiment 6 of the present invention.
  • On-Board Diagnostic is used to monitor whether the working status of each system in the vehicle is abnormal. If abnormal, determine the specific fault in the corresponding system and use Diagnostic Trouble Codes (Diagnostic Trouble Codes, DTC) is stored in the form.
  • the system can perform self-diagnosis according to DTC, and repair or maintain the vehicle in time.
  • OBD can also be equipped with OBD interface.
  • the OBD interface can be connected with external vehicle diagnostic equipment, so that maintenance personnel can use the above equipment to read in time. Go to DTC and carry out repair and maintenance of the vehicle to reduce the time for manual diagnosis.
  • ECU Electronic Control Unit
  • FIG. 1 is a schematic diagram showing the principle of establishing a communication connection between a vehicle diagnostic device and a vehicle.
  • the vehicle includes one or more systems 1, such as an engine system, an emission control system, a fuel system, etc., each of which is connected to a corresponding pin in the OBD interface 3 via a bus.
  • the connection bus of the ECU in each system and the corresponding pin in the OBD interface may be the same, and may be different, and is not limited herein.
  • the OBD interface 3 can be connected to the vehicle diagnostic device 5 via a connection line 4.
  • the vehicle diagnostic device 5 may include an original diagnostic device, a comprehensive platform diagnostic device, a terminal to which an application having a diagnostic function is installed, and the like, which is not limited herein.
  • the vehicle diagnostic device 5 After the vehicle diagnostic device 5 establishes a physical connection with the OBD interface 3 through the connection line 4, the vehicle diagnostic device 5 performs a communication protocol scan on a certain pin of the OBD interface 3.
  • performing the communication protocol scanning means that a connection request is sent to the pin in sequence based on a communication protocol, and the pin can sequentially send the connection request to the corresponding system ECU through the bus until the vehicle diagnostic device 5 receives the pin. The response sent by the connection request for a certain communication protocol.
  • the vehicle diagnostic device can establish a communication connection with the system ECU based on the communication protocol to implement data communication. After the vehicle diagnostic device 5 establishes communication with the vehicle, a diagnostic routine in the vehicle diagnostic device is run to enable fault code scanning and data stream communication for the vehicle.
  • the existing vehicle diagnostic instrument requires a large number of fault code scans and data stream communication for the vehicle, and the diagnostic efficiency is low, and the obtained diagnosis result is difficult to accurately locate the fault problem, so the experience and ability of the maintenance personnel. Have higher requirements.
  • FIG. 2 is a flowchart of a method for diagnosing a vehicle according to a first embodiment of the present invention. As shown in FIG. 2, the method in this embodiment may include:
  • the method may further include: acquiring vehicle information of the vehicle; determining a target failure problem according to the vehicle information of the vehicle and the fault symptom information.
  • the vehicle information of the vehicle may be received by the user; or the vehicle information of the vehicle may be acquired from the electronic control unit ECU of the vehicle.
  • the vehicle information refers to the vehicle identification number (VIN), the vehicle type, the vehicle model, the brand, the date of manufacture, the mileage, the historical maintenance record, and the like to characterize the vehicle.
  • the fault description information input by the user may be received; and then the fault symptom information related to the fault description information is acquired according to the fault description information.
  • the keyword may be extracted according to the fault description information input by the user, and the fault symptom information matching the keyword may be searched for.
  • the fault description information input by the user may include information such as text, image, audio, and the like. If the fault description information input by the user includes image or audio information, the image or the audio signal may be parsed to extract the keyword, and the fault symptom information matching the keyword may be searched for.
  • the fault symptom information includes all or part of the extracted keywords, and then the determined keyword matches the fault symptom information, and further, the fault symptom information is related to the fault description information.
  • the fault symptom information related to the fault description information may be obtained from a local database or a cloud database.
  • the local database refers to fault symptom information stored in the memory of the diagnostic device itself
  • the cloud database refers to a network database that can communicate with the diagnostic device, and the fault symptom information is stored in the network database.
  • At least two fault symptom information related to the fault description information When determining at least two fault symptom information related to the fault description information, displaying the at least two fault symptom information for selection by a user; and selecting fault symptom information of the user from the at least two fault symptom information As the fault symptom information of the vehicle. For example, at least 2 fault symptom information can be displayed in the form of a list for the user to select.
  • the historical fault symptom information of the vehicle and/or preset common fault symptom information may be displayed to prompt the user to select; the user from the historical fault symptom information and/or the common fault
  • the fault symptom information selected in the symptom information is used as the fault symptom information of the vehicle.
  • the historical fault symptom information of the vehicle refers to a fault symptom that the vehicle has experienced before the current time.
  • historical fault symptom information can be obtained from the maintenance record of the vehicle.
  • the preset common fault symptom information refers to a symptom that often occurs in a vehicle of the same type, same brand, or other vehicle information as the vehicle.
  • the vehicle diagnosis device may further send the fault description information to the server, so that the server acquires fault symptom information related to the fault description information according to the fault description information, and the server may further fail.
  • the symptom information generates a prompt list and sends it to the vehicle diagnostic device; the vehicle diagnostic device can receive the prompt list fed back by the server and display it.
  • FIG. 3 is a schematic diagram of a prompt list of the application with the fault description information “exotic sound”, as shown in FIG. 3, in the fault description information input interface of the diagnostic apparatus, when the user inputs “exotic sound”, at the bottom of the dialog box A list of prompts is displayed, and the fault symptom information of “engine abnormal noise, abnormal gearbox noise, abnormal body noise, abnormal tire noise” is displayed in the prompt list. The user can select any or any of the fault symptom information from the list of prompts.
  • the fault symptom information related to the fault description information may also be obtained by searching from a local database or a cloud database.
  • the fault symptom information related to the fault description information may be obtained by searching from a local database through a diagnostic tool, and then generating a prompt list according to the fault symptom information.
  • the fault description information may also be sent by the diagnostic device to the service, and the server searches for the fault symptom information related to the fault description information from the cloud database, and then feeds back the fault symptom information to the diagnostic device.
  • the list of historical fault symptom information of the vehicle may be displayed on the display of the diagnostic apparatus before receiving the fault description information input by the user, and/or common faults.
  • a list of references for symptom information This provides a reference for the user to describe the vehicle fault.
  • the target failure problem is determined from a fault problem associated with the fault symptom information of the vehicle.
  • the fault problem is regarded as the target fault problem; or the fault problem is fed back to the user, and after receiving the user's confirmation information, the fault problem is regarded as the target fault problem.
  • the fault phenomenon included in the fault problem is acquired; and the target fault problem is determined according to the degree of matching between the fault phenomenon occurring in the vehicle and the fault phenomenon included in the fault problem.
  • the number of target fault problems may be one or more, and the number of target fault problems in this embodiment is not limited.
  • the fault phenomenon occurring in the vehicle may be first determined by displaying a fault phenomenon and according to a user selecting operation for the fault phenomenon. Then, the target fault problem is determined according to the degree of matching between the fault phenomenon occurring in the vehicle and the fault phenomenon included in the fault problem.
  • fault data may first be acquired from an ECU of the vehicle; and a fault phenomenon occurring in the vehicle is determined based on the fault data. Then, the target fault problem is determined according to the degree of matching between the fault phenomenon occurring in the vehicle and the fault phenomenon included in the fault problem.
  • the fault problem that meets the vehicle information and the fault symptom information of the vehicle in the local database or the cloud server may be a target fault problem.
  • the diagnostic apparatus may search the local database for all candidate fault problems that meet the vehicle information; wherein each of the candidate fault problems corresponds to at least one fault phenomenon; and then the fault phenomenon is matched with the fault symptom information.
  • the candidate failure problem is the target failure problem.
  • the candidate fault problem is multiple, the candidate fault problem with the most fault phenomenon matching the fault symptom information among the corresponding fault phenomena is determined as the target fault problem.
  • the candidate fault problem is sorted according to the priority order, and the sorting result of the candidate fault problem is obtained; the sorting result is displayed, and the user is prompted to confirm the target fault problem.
  • the priority order refers to: the more the fault phenomenon included in the target fault problem matches the fault symptom information, the higher the priority of the corresponding target fault problem.
  • the candidate fault problem with the highest priority among the priority order is taken as the target fault problem.
  • the fault problem associated with it may be xx, yy, zz.
  • the fault problem xx includes: fault phenomenon a, fault phenomenon b, fault phenomenon c;
  • fault problem yy includes: fault phenomenon a, fault phenomenon b, fault phenomenon e;
  • fault problem zz includes: fault phenomenon c, fault phenomenon f, fault Phenomenon d. It can be seen that there are three fault phenomena in the fault problem xx that match the fault symptom information; two fault phenomena in the fault problem yy match the fault symptom information; the fault problem zz has a fault phenomenon matching the fault symptom information.
  • the fault problem xx has a higher priority than the fault problem yy
  • the fault problem yy has a higher priority than the fault problem zz.
  • the user can select one of xx, yy, and zz as the final target failure problem, and can also verify and analyze all the matched failure problems in sequence until the failure problem is successfully solved.
  • the vehicle information and the fault symptom information of the vehicle may also be sent to the server through the diagnostic apparatus; so that the server determines the target fault problem according to the vehicle information and the fault symptom information; and then receives the server feedback.
  • the target failure problem When the target fault problem is multiple, the target fault problem is sorted according to a preset priority, and the sort result of the target fault problem is obtained; the server sends the sorted target fault problem to the diagnostic apparatus. The sorting result is displayed on the diagnostic device and the user is prompted to confirm the final target failure problem.
  • the priority order refers to: the more the fault phenomenon included in the target fault problem matches the fault symptom information, the higher the priority of the corresponding target fault problem.
  • all solutions corresponding to the target failure problem can be searched from the local database; then all the solutions are displayed, and the final solution is determined according to the confirmation information input by the user.
  • the solution in this embodiment refers to a specific process step of solving the target failure problem.
  • all of the solutions may be displayed in accordance with the degree of relevance to the target failure problem, with the higher the degree of relevance of the solution, the higher the display order.
  • the local database in this embodiment refers to a memory in the diagnostic instrument for storing fault problems, as well as solutions associated with fault problems.
  • the solution in this embodiment includes a diagnostic process that determines the device in which the problem is located by performing the steps in the diagnostic process.
  • the diagnostic process is as follows:
  • Step 1 Check whether the automatic transmission harness connector C30 and harness connector C31 are detached or are dirty; if yes, go to step 2; if no, go to step 3.
  • Step 2 Repair the automatic transmission line speed plug.
  • Step 3 Link the diagnostic tool, the diagnosis automatically jumps to the automatic transmission system fault code scan; check if there is a fault code other than PXXX1, PXXX2, PXXX3; if it is, go to step 4.
  • Step 4 Refer to Diagnostic Trouble Code DTC Diagnostic Flow Wizard for diagnosis and testing.
  • all solutions corresponding to the target failure problem fed back by the server may also be received by the diagnostic instrument; then all the solutions are displayed, and the final solution is determined according to the confirmation information input by the user.
  • all of the solutions may be displayed in accordance with the degree of relevance to the target failure problem, with the higher the degree of relevance of the solution, the higher the display order.
  • the solution here can be stored in the server or it can be a solution that the server finds from the cloud database. It should be noted that the solution in this embodiment may include: a diagnosis process, by performing the diagnosis process, the fault component, the cause of the fault, and the corresponding solution may be located, so that the maintenance personnel can be released according to the diagnosis process. malfunction.
  • the method shown in FIG. 2 may further include:
  • the solutions corresponding to the target fault problem are sorted to obtain a sorting result
  • the correlation between the solution and the target fault problem is determined according to a historical solution result of the solution to solve the target fault problem.
  • an implementation record of the solution corresponding to the target fault problem may be acquired; when the target fault problem is successfully solved, the target fault problem and the corresponding solution are improved according to a preset criterion. Correlation between the two; when the target failure problem is resolved, the correlation between the target failure problem and the corresponding solution is reduced.
  • the diagnostic device records the actual implementation solution corresponding to each target failure problem. When the solution to the target failure problem is successfully solved, at least according to the implementation condition of the solution, the implementation process complexity, and the number of successful solutions. An adjustment between the solution and the corresponding target failure problem.
  • the implementation conditions of the solution are simple, the implementation process complexity is lower, and the more successful the solution, the higher the correlation between the solution and the corresponding target failure problem.
  • the method in this embodiment as the number of diagnostics diagnostics increases, the more accurate the recommended solution.
  • an implementation record of the solution corresponding to the target failure problem may be acquired; an implementation record of the solution corresponding to the target failure problem is sent to the server, so that the server adjusts according to the implementation record.
  • the degree of correlation between the target failure problem and the corresponding solution the server can obtain the implementation record of the solution corresponding to the target failure problem through the diagnostic device, and when the solution to the target failure problem is successfully solved, according to the implementation condition of the solution, the implementation process complexity, and the solution At least one of the number of successes adjusts the correlation between the solution and the corresponding target failure problem.
  • the implementation conditions of the solution are simple, the implementation process complexity is lower, and the more successful the solution, the higher the correlation between the solution and the corresponding target failure problem.
  • the method in this embodiment as the number of diagnostics of the diagnostic instrument in communication with the server increases, the more accurate the recommended solution.
  • the method further includes:
  • the target solution in at least two solutions is selected according to the user's selection operation for the solution. Displaying a diagnostic step included in the target solution to prompt a user to perform a diagnostic operation on the vehicle according to the diagnostic step;
  • a next diagnostic step associated with the diagnostic data and/or the diagnostic result is displayed.
  • the user can be guided step by step through the diagnostic process, so that the diagnosis can be accurately obtained according to the solution.
  • the parameter information and the fault symptom information of the vehicle are acquired; at least one target fault problem is determined according to the parameter information of the vehicle and the fault symptom information; and then the corresponding solution is determined according to the target fault problem.
  • FIG. 4 is a flowchart of a vehicle diagnosis method according to Embodiment 2 of the present invention. As shown in FIG. 4, the method in this embodiment may include:
  • the user can modify the solution.
  • the diagnosis process of the solution is modified. Specifically, any or any of the following steps can be performed on the steps in the diagnosis process:
  • the modified new solution of the user is saved.
  • the diagnostic tool can place the new solution into a local database and associate the new solution with the corresponding failure problem.
  • the diagnostic device sends a new solution to the server, the server can save the new solution in the server's own memory, or upload it to the cloud database, and the new solution and the corresponding fault problem in the cloud database. Make an association.
  • a new solution is obtained by receiving a modification of the solution by the user, and then saving the new solution to a local database, or sending the new solution to a server, so that the server Save the new solution to the cloud database.
  • FIG. 5 is a schematic structural diagram of a vehicle diagnosing device according to Embodiment 3 of the present invention. As shown in FIG. 5, the device in this embodiment may include:
  • the obtaining module 10 is configured to acquire fault symptom information of the vehicle
  • a determining module 20 configured to determine a target fault problem according to the fault symptom information of the vehicle
  • the determining module 20 is further configured to determine a solution corresponding to the target fault problem.
  • the vehicle diagnostic device of this embodiment may be a diagnostic device, or may be a server, or may also be a diagnostic device and a server.
  • the obtaining module 10 can be implemented by a diagnostic device
  • the determining module 20 can be implemented by a server
  • the determining module 20 can also be implemented by a diagnostic device and a server for performing communication interaction.
  • the obtaining module 10 is further configured to acquire vehicle information of the vehicle.
  • the determining module 20 is specifically configured to:
  • a target failure problem is determined based on the vehicle information of the vehicle and the fault symptom information.
  • the acquiring module 10 is specifically configured to: receive vehicle information of the vehicle input by a user; or
  • Vehicle information of the vehicle is acquired from an electronic control unit ECU of the vehicle.
  • the obtaining module 10 is specifically configured to:
  • the acquiring fault symptom information related to the fault description information according to the fault description information includes:
  • This embodiment can perform the technical solutions in the foregoing methods shown in FIG. 2 and FIG. 4 , and the implementation process and technical effects are similar to the foregoing methods, and details are not described herein again.
  • FIG. 6 is a schematic structural diagram of a vehicle diagnosing device according to Embodiment 4 of the present invention. As shown in FIG. 6 , the device in this embodiment may further include:
  • the display module 30 is configured to display the at least two fault symptom information for selection by the user when determining at least two fault symptom information related to the fault description information;
  • the fault symptom information selected by the user from the at least two fault symptom information is used as the fault symptom information of the vehicle.
  • the obtaining module 10 is further configured to:
  • the fault symptom information selected by the user from the historical fault symptom information and/or the common fault symptom information is used as the fault symptom information of the vehicle.
  • the determining module 20 is specifically configured to:
  • the target failure problem is determined from a failure problem related to the failure symptom information of the vehicle.
  • the determining the target fault problem from the fault problem related to the fault symptom information of the vehicle includes:
  • the target fault problem is determined according to the degree of matching between the fault phenomenon occurring in the vehicle and the fault phenomenon included in the fault problem.
  • the display module 30 is further configured to display the fault phenomenon before determining a target fault problem according to the matching degree of the fault phenomenon and the fault symptom information;
  • a fault phenomenon occurring in the vehicle is determined according to a selection operation of the user for the fault phenomenon.
  • the obtaining module 10 is further configured to: acquire fault data from an ECU of the vehicle before determining a target fault problem according to a matching degree between the fault phenomenon and the fault symptom information;
  • a fault phenomenon occurring in the vehicle is determined according to the fault data.
  • the determining module 20 is specifically configured to:
  • the target failure problem among the at least two failure problems is determined according to the priority of the at least two failure problems.
  • the determining module 20 is specifically configured to:
  • the device further includes:
  • the display module 30 is configured to display a solution corresponding to the target failure problem.
  • the display module is further configured to: before the solution corresponding to the target fault problem is displayed, perform a solution corresponding to the target fault problem according to a correlation between the solution and the target fault problem Sort to get the sort result;
  • the relevance of the solution to the target failure problem is determined according to a historical solution result of the solution solving the target failure problem.
  • the determining module 20 is further configured to: after displaying the solution corresponding to the target fault problem, when the number of solutions corresponding to the target fault problem is at least two, according to the user Select the target solution of at least 2 solutions.
  • the display module 30 is further configured to:
  • a next diagnostic step associated with the diagnostic data and/or the diagnostic result is displayed.
  • the device further includes:
  • the storage module 40 is configured to obtain a new solution corresponding to the target failure problem according to a modification operation of the solution by the user; and save the new solution.
  • This embodiment can perform the technical solutions in the foregoing methods shown in FIG. 2 and FIG. 4 , and the implementation process and technical effects are similar to the foregoing methods, and details are not described herein again.
  • FIG. 7 is a schematic structural diagram of a vehicle diagnosis system according to Embodiment 5 of the present invention.
  • the system in this embodiment includes: a diagnostic device 50 and/or a server 60, and the diagnostic device 50 and/or server 60
  • the technical solution in the method shown in FIG. 2 and FIG. 4 is implemented, and the implementation process and technical effects are similar to the above methods, and details are not described herein again.
  • FIG. 8 is a schematic structural diagram of a vehicle diagnosis apparatus according to Embodiment 6 of the present invention. As shown in FIG. 8, the vehicle diagnosis apparatus 70 in this embodiment includes:
  • the memory 72 is configured to store a computer program (such as an application, a function module, etc. for implementing the above diagnostic function), a computer instruction, data (such as fault symptom information, a fault problem, a solution, etc.), the above computer program, computer instruction, Data or the like may be partitioned and stored in one or more memories 72. And the above computer program, computer instructions, data, etc. can be called by the processor 71.
  • a computer program such as an application, a function module, etc. for implementing the above diagnostic function
  • a computer instruction, data such as fault symptom information, a fault problem, a solution, etc.
  • the above computer program, computer instruction, Data or the like may be partitioned and stored in one or more memories 72.
  • the above computer program, computer instructions, data, etc. can be called by the processor 71.
  • the processor 71 is configured to execute the computer program stored by the memory 72 to implement various steps in the method involved in the foregoing embodiments. For details, refer to the related description in the foregoing method embodiments.
  • the communication interface 73 is configured to implement an OBD interface communication connection with the vehicle and implement a communication connection with the server.
  • the communication interface 73 may include a wired communication interface and a wireless communication interface.
  • the vehicle diagnostic device can be connected to the OBD interface of the vehicle by using a wired communication interface or a wireless communication interface. Similarly, the vehicle diagnostic device can also implement a communication connection with the server by using a wired communication interface or a wireless communication interface.
  • the memory 72, the processor 71 and the communication interface 73 can be coupled by a bus 74.
  • the processor 71 can communicate with the vehicle via the control communication interface 73.
  • This embodiment can perform the technical solutions in the foregoing methods shown in FIG. 2 and FIG. 4 , and the implementation process and technical effects are similar to the foregoing methods, and details are not described herein again.
  • the embodiment of the present application further provides a computer readable storage medium, where the computer program is stored in a computer program, and when the computer program is run by the vehicle diagnostic device, any of the foregoing embodiments of FIG. 2 and FIG. 4 may be implemented. Said method.
  • the computer readable medium comprises a computer storage medium and a communication medium, wherein the communication medium comprises any medium that facilitates transfer of the computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a vehicle diagnostic device.
  • the processor and the storage medium may also reside as discrete components in the communication device.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Fuzzy Systems (AREA)
  • Mathematical Physics (AREA)
  • Quality & Reliability (AREA)
  • Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本发明提供一种车辆诊断方法、装置及设备，该方法包括：获取车辆的故障症状信息；根据所述车辆的故障症状信息，确定目标故障问题；确定与所述目标故障问题对应的解决方案。采用本发明中的方法，无需对车辆进行全面检测，缩小了故障码、数据流的获取范围，诊断效率高，并能够根据故障症状信息直接对车辆进行诊断，不仅简化了诊断流程，还使得诊断结果更加可靠全面，适用性广。

Description

车辆诊断方法、装置及设备
本申请要求于2018年4月25日提交中国专利局、申请号为201810382862.3、申请名称为“车辆诊断方法、装置及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及汽车故障诊断技术领域，尤其涉及一种车辆诊断方法、装置及设备。
背景技术
随着车辆诊断技术的发展，在进行车辆故障诊断时，往往借助于专业的诊断仪器对车辆的各种诊断参数进行检测、试验、分析，以确定车辆的故障原因。然后根据确定的故障原因选用对应的解决方案对车辆进行维修。
目前，市场上的车辆诊断仪器的诊断流程一般是：首先确定车型，然后进行故障码扫描、数据流读取等操作；最后通过对诊断仪器输出的故障码和数据流进行人为分析来确定故障问题。
但是，现有的这种车辆诊断仪器，需要对车辆进行大量的故障码扫描，以及数据流通信，诊断效率低，得出的诊断结果很难准确定位故障问题，因此对维修人员的经验和能力均有较高的要求。
发明内容
本发明实施例提供一种车辆诊断方法、装置及设备，以简化车辆诊断流程，提高车辆诊断结果的可靠性。
第一方面，本发明实施例提供一种车辆诊断方法，包括：
获取车辆的故障症状信息；
根据所述车辆的故障症状信息，确定目标故障问题；
确定与所述目标故障问题对应的解决方案。
可选地，所述方法还包括：
获取所述车辆的车辆信息；
所述根据所述车辆的故障症状信息，确定目标故障问题，包括：
根据所述车辆的所述车辆信息和所述故障症状信息，确定目标故障问题。
可选地，所述获取所述车辆的车辆信息，包括：
接收用户输入的所述车辆的车辆信息；或者，
从所述车辆的电子控制单元ECU中获取所述车辆的车辆信息。
可选地，所述获取车辆的故障症状信息，包括：
接收用户输入的故障描述信息；
根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息。
可选地，所述根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息，包括：
从本地数据库或云端数据库中获取所述故障描述信息相关的故障症状信息。
可选地，所述方法还包括：
当确定与所述故障描述信息相关的至少2个故障症状信息时，显示所述至少2个故障症状信息，以供用户选择；
将用户从所述至少2个故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
可选地，所述获取车辆的故障症状信息，包括：
显示所述车辆的历史故障症状信息和/或预设的常见故障症状信息，以提示用户选取；
将用户从所述历史故障症状信息和/或所述常见故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
可选地，所述根据所述车辆的故障症状信息，确定目标故障问题，包括：
从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题。
可选地，所述从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题，包括：
获取所述故障问题包括的故障现象；
根据所述车辆出现的故障现象与所述故障问题包括的故障现象的匹配程度，确定目标故障问题。
可选地，所述根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，所述方法还包括：
显示所述故障现象；
根据用户针对所述故障现象的选取操作，确定所述车辆出现的故障现象。
可选地，所述根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，所述方法还包括：
从所述车辆的ECU中获取故障数据；
根据所述故障数据确定所述车辆出现的故障现象。
可选地，所述从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题，包括：
当与所述车辆的故障症状信息相关的故障问题的数量为至少2个时，根据至少2个故障问题的优先级，确定所述至少2个故障问题中的目标故障问题。
可选地，所述确定与所述目标故障问题对应的解决方案，包括：
从本地数据库或云端数据库中获取与所述目标故障问题对应的解决方案。
可选地，所述方法还包括：
显示与所述目标故障问题对应的解决方案。
可选地，所述显示与所述目标故障问题对应的解决方案之前，还包括：
按照解决方案与所述目标故障问题的相关度，对所述目标故障问题对应的解决方案进行排序，得到排序结果；
所述显示与所述目标故障问题对应的解决方案，包括：
根据所述排序结果，显示与所述目标故障问题对应的解决方案。
可选地，所述解决方案与所述目标故障问题的相关度是根据所述解决方案解决所述目标故障问题的历史解决结果确定的。
可选地，所述显示与所述目标故障问题对应的解决方案之后，所述方法还包括：
当与所述目标故障问题对应的解决方案的数量为至少2个时，根据用户针对解决方案的选取操作，选取至少2个解决方案中的目标解决方案。
可选地，所述方法还包括：
显示所述目标解决方案包括的诊断步骤，以提示用户根据所述诊断步骤对所述车辆进行诊断操作；
获取所述车辆被执行所述诊断操作后的诊断数据和/或诊断结果；
根据所述诊断数据和/或所述诊断结果，显示与所述诊断数据和/或所述诊断结果相关的下一个诊断步骤。
可选地，所述方法还包括：
根据用户对所述解决方案的修改操作，得到所述目标故障问题对应的新的解决方案；
保存所述新的解决方案。
第二方面，本发明实施例提供一种车辆诊断装置，包括：
获取模块，用于获取车辆的故障症状信息；
确定模块，用于根据所述车辆的故障症状信息，确定目标故障问题；
确定模块，还用于确定与所述目标故障问题对应的解决方案。
可选地，所述获取模块，还用于获取所述车辆的车辆信息；
所述确定模块，具体用于：
根据所述车辆的所述车辆信息和所述故障症状信息，确定目标故障问题。
可选地，所述获取模块，具体用于：接收用户输入的所述车辆的车辆信息；或者，
从所述车辆的电子控制单元ECU中获取所述车辆的车辆信息。
可选地，所述获取模块，具体用于：
接收用户输入的故障描述信息；
根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息。
可选地，所述根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息，包括：
从本地数据库或云端数据库中获取所述故障描述信息相关的故障症状信息。
可选地，所述装置还包括：
显示模块，用于在确定与所述故障描述信息相关的至少2个故障症状信息时，显示所述至少2个故障症状信息，以供用户选择；
将用户从所述至少2个故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
可选地，所述获取模块，还用于：
显示所述车辆的历史故障症状信息和/或预设的常见故障症状信息，以提示用户选取；
将用户从所述历史故障症状信息和/或所述常见故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
可选地，所述确定模块，具体用于：
从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题。
可选地，所述从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题，包括：
获取所述故障问题包括的故障现象；
根据所述车辆出现的故障现象与所述故障问题包括的故障现象的匹配程度，确定目标故障问题。
可选地，所述显示模块，还用于在根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，显示所述故障现象；
根据用户针对所述故障现象的选取操作，确定所述车辆出现的故障现象。
可选地，所述获取模块，还用于在根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，从所述车辆的ECU中获取故障数据；
根据所述故障数据确定所述车辆出现的故障现象。
可选地，所述确定模块，具体用于：
在与所述车辆的故障症状信息相关的故障问题的数量为至少2个时，根据至少2个故障问题的优先级，确定所述至少2个故障问题中的目标故障问题。
可选地，所述确定模块，具体用于：
从本地数据库或云端数据库中获取与所述目标故障问题对应的解决方案。
可选地，所述装置还包括：
显示模块，用于显示与所述目标故障问题对应的解决方案。
可选地，所述显示模块，还用于在显示与所述目标故障问题对应的解决方案之前，按照解决方案与所述目标故障问题的相关度，对所述目标故障问题对应的解决方案进行排序，得到排序结果；
根据所述排序结果，显示与所述目标故障问题对应的解决方案。
可选地，所述解决方案与所述目标故障问题的相关度是根据所述解决方案解决所述目标故障问题的历史解决结果确定的。
可选地，所述确定模块，还用于在显示与所述目标故障问题对应的解决方案之后，当与所述目标故障问题对应的解决方案的数量为至少2个时，根据用 户针对解决方案的选取操作，选取至少2个解决方案中的目标解决方案。
可选地，所述显示模块，还用于：
显示所述目标解决方案包括的诊断步骤，以提示用户根据所述诊断步骤对所述车辆进行诊断操作；
获取所述车辆被执行所述诊断操作后的诊断数据和/或诊断结果；
根据所述诊断数据和/或所述诊断结果，显示与所述诊断数据和/或所述诊断结果相关的下一个诊断步骤。
可选地，所述装置还包括：
存储模块，用于根据用户对所述解决方案的修改操作，得到所述目标故障问题对应的新的解决方案；保存所述新的解决方案。
第三方面，本发明实施例提供一种车辆诊断设备，包括：
存储器，以及与所述存储器连接的处理器；
其中，所述存储器存储有计算机程序；
所述处理器调用所述计算机程序，以执行如第一方面中任一项所述的方法。
第四方面，本发明实施例提供一种车辆诊断系统，包括：诊断仪和/或服务器，
所述诊断仪和/或服务器用于执行第一方面中任一项所述的方法。
第五方面，本发明实施例提供一种计算机可读存储介质，包括：计算机程序，当其在计算机上运行时，使得计算机执行第一方面中任一所述的方法。
本发明实施例提供的车辆诊断方法、装置及设备，获取车辆的故障症状信息；根据所述车辆的故障症状信息，确定目标故障问题；确定与所述目标故障问题对应的解决方案。采用本发明中的方法，无需对车辆进行全面检测，缩小了故障码、数据流的获取范围，诊断效率高，并能够根据故障症状信息直接对车辆进行诊断，不仅简化了诊断流程，还使得诊断结果更加可靠全面，适用性广。
附图说明
图1为车辆诊断设备与车辆建立通信连接的原理示意图；
图2为本发明实施例一提供的车辆诊断方法的流程图；
图3为与故障描述信息“异响”对应用的提示列表的示意图；
图4为本发明实施例二提供的车辆诊断方法的流程图；
图5为本发明实施例三提供的车辆诊断装置的结构示意图；
图6为本发明实施例四提供的车辆诊断装置的结构示意图；
图7为本发明实施例五提供的车辆诊断系统的结构示意图；
图8为本发明实施例六提供的车辆诊断设备的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
以下，对本申请中的部分用语进行解释说明，以便于本领域技术人员理解：
1)车载诊断系统(On-Board Diagnostic，OBD)，用于监测车辆中各系统的工作状态是否异常，若异常，则确定出对应系统中的具体故障，并以诊断故障码(Diagnostic Trouble Codes，DTC)的形式进行存储。系统可根据DTC进行自诊断，以及时对车辆进行维修或保养，OBD也可以设有OBD接口，该OBD接口可以与外部的车辆诊断设备进行通信连接，从而可以使维修人员利用上述设备及时读取到DTC，并进行对车辆的维修和保养，减少人工诊断的时间。
2)电子控制单元(Electronic Control Unit，ECU)，其布设在车辆的各系统中，如发动机系统、排放控制系统、燃油系统等；其可以通过OBD接口与车辆诊断设备实现通信。
下面结合图1，对本申请实施例涉及的应用场景进行说明。
图1为车辆诊断设备与车辆建立通信连接的原理示意图。如图1所示，车辆包括一个或多个系统1，如发动机系统、排放控制系统、燃油系统等，每个系统中的ECU2各自通过总线与OBD接口3中对应的管脚连接。各系统中的ECU与OBD接口中对应管脚的连接总线可以相同，可以不同，在此不予限定。OBD接口3可以通过连接线4与车辆诊断设备5连接。在此，车辆诊断设备5可以包括原厂诊断仪，综合平台诊断设备，安装有具备诊断功能的应用程序的终端等，在此不予限定。具体地，车辆诊断设备5通过连接线4与OBD接口3建立物理连接后，车辆诊断设备5会对OBD接口3的某一个管脚进行通信协议扫描。在此，进行通信协议扫描是指依次基于一个通信协议向该管脚发送连接请求，该管脚可以依次将连接请求通过总线发送至对应的系统ECU中，直至车辆诊断设备5接收到该管脚发送的针对某一通信协议的连接请求的响应。进而，车辆诊断设备可以与该系统ECU基于该通信协议建立通信连接，以实现数据通信。当车辆诊断设备5与车辆建立通信之后，运行车辆诊断设备中的诊断程序，以实现对车辆的故障码扫描和数据流通信。
但是，现有的这种车辆诊断仪器，需要对车辆进行大量的故障码扫描，以及数据流通信，诊断效率低，得出的诊断结果很难准确定位故障问题，因此对维修人员的经验和能力均有较高的要求。
基于上述问题，下面结合附图介绍本申请实施例。
图2为本发明实施例一提供的车辆诊断方法的流程图，如图2所示，本实施例中的方法可以包括：
S101、获取车辆的故障症状信息。
在步骤S101之前，所述方法还可以包括：获取所述车辆的车辆信息；根据所述车辆的所述车辆信息和所述故障症状信息，确定目标故障问题。
本实施例中，可以通过接收用户输入的所述车辆的车辆信息；或者，从所述车辆的电子控制单元ECU中获取所述车辆的车辆信息。其中，车辆信息是指车辆的标识码(Vehicle Identification Number，VIN)、车型、车款、品牌、出厂日期、行驶里程、历史维修记录等用以表征车辆的信息。
在一种实施方式中，可以通过接收用户输入的故障描述信息；然后根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息。具体地，可以根据用户输入的故障描述信息，提取出关键词，并查找与该关键词相匹配的故障症状信息。其中，用户输入的故障描述信息可以包括文字、图像、音频等信息。若用户输入的故障描述信息包括图像或音频信息时，可以对图像或音频信号进行解析，进而提取出关键词，并可以查找与该关键词相匹配的故障症状信息。例如，故障症状信息包括提取出的全部或部分关键词，则确定关键词与故障症状信息相匹配，进而，该故障症状信息与故障描述信息相关。
可选地，可以从本地数据库或云端数据库中获取所述故障描述信息相关的故障症状信息。其中，本地数据库是指诊断设备自身的存储器中存储的故障症状信息，云端数据库是指可以与诊断设备通信的网络数据库，在该网络数据库中存储有故障症状信息。
当确定与所述故障描述信息相关的至少2个故障症状信息时，显示所述至少2个故障症状信息，以供用户选择；将用户从所述至少2个故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。例如，可以将至少2个故障症状信息以列表的形式进行显示，以供用户选择。
在另一种实施方式中，可以显示所述车辆的历史故障症状信息和/或预设的常见故障症状信息，以提示用户选取；将用户从所述历史故障症状信息和/或所述常见故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
本实施例中，车辆的历史故障症状信息是指：该车辆在当前时间以前曾经出现过的故障症状。具体地，可以从车辆的维修记录中获取到历史故障症状信息。预设的常见故障症状信息是指：对应该车辆的同类型、同品牌，或其他车辆信息相同的车辆经常会出现的故障症状。
一种实现方式中，车辆诊断设备还可以向服务器发送所述故障描述信息，以使所述服务器根据所述故障描述信息获取与该故障描述信息相关的故障症状信息，服务器还可以进一步的将故障症状信息生成提示列表，并发送给车辆诊断设备；车辆诊断设备可以接收服务器反馈的所述提示列表，并进行显示。图3为与故障描述信息“异响”对应用的提示列表的示意图，如图3所示，在诊断仪的故障描述信息输入界面中，当用户输入“异响”时，在对话框的下方显示提示列表，提示列表中显示了“发动机异响、变速箱异响、车身异响、轮胎异响”这些故障症状信息。用户可以从提示列表中选择任一或者任多个故障 症状信息。
本实施例中，还可以从本地数据库或云端数据库中搜索获得与所述故障描述信息相关的故障症状信息。具体地，可以通过诊断仪从本地数据库中搜索获得与所述故障描述信息相关的故障症状信息，然后根据所述故障症状信息，生成提示列表。也可以由诊断仪向服务发送故障描述信息，由服务器从云端数据库中搜索出于所述故障描述信息相关的故障症状信息，然后将该故障症状信息反馈给诊断仪。
本实施例中，为了方便用户对车辆故障进行更加准确的描述，还可以在在接收用户输入的故障描述信息之前，在诊断仪的显示器上显示车辆的历史故障症状信息列表，和/或常见故障症状信息的参考列表。从而为用户描述车辆故障提供参考。
S102、根据所述车辆的故障症状信息，确定目标故障问题。
可选地，从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题。当只有1个故障问题时，将该故障问题作为目标故障问题；或者将该故障问题反馈给用户，在接收到用户的确认信息后，将该故障问题作为目标故障问题。当存在2个以上的故障问题时，获取所述故障问题包括的故障现象；根据所述车辆出现的故障现象与所述故障问题包括的故障现象的匹配程度，确定目标故障问题。
需要说明的是，目标故障问题的数量可以是1个或者1个以上，本实施例对目标故障问题的数量不予限定。
在一种实施方式中，首先可以通过显示故障现象，并根据用户针对所述故障现象的选取操作，确定所述车辆出现的故障现象。然后，根据所述车辆出现的故障现象与所述故障问题包括的故障现象的匹配程度，确定目标故障问题。
在另一种实施方式中，首先可以从所述车辆的ECU中获取故障数据；并根据所述故障数据确定所述车辆出现的故障现象。然后，根据所述车辆出现的故障现象与所述故障问题包括的故障现象的匹配程度，确定目标故障问题。
本实施例中，可以从本地数据库或云端服务器中符合所述车辆信息和所述车辆的故障症状信息的故障问题，作为目标故障问题。例如，诊断仪可以从本地数据库中搜索符合所述车辆信息的所有候选故障问题；其中，每个所述候选故障问题均对应至少一个故障现象；然后将存在故障现象与所述故障症状信息匹配的候选故障问题作为目标故障问题。当所述候选故障问题为多个时，将其对应的故障现象中与所述故障症状信息匹配的故障现象最多的候选故障问题，确定为目标故障问题。当候选故障问题为多个时，按照优先级顺序对所述候选故障问题进行排序，得到所述候选故障问题的排序结果；显示所述排序结果，并提示用户确认目标故障问题。可选地，所述优先级顺序是指：目标故障问题中所包含的故障现象与所述故障症状信息匹配的数量越多，则对应的目标故障问题的优先级越高。或者，将优先级顺序中优先级最高的候选故障问题作为目标故障问题。
举例说明，假设故障症状信息为“a、b、c”，与其相关的故障问题可以是xx，yy，zz。其中，故障问题xx包括：故障现象a、故障现象b、故障现象c；故障问题yy包括：故障现象a、故障现象b、故障现象e；故障问题zz包括：故障现象c、故障现象f、故障现象d。由此可见，故障问题xx中有三个故障现象与故障症状信息匹配；故障问题yy中有两个故障现象与故障症状信息匹配；故障问题zz有一个故障现象与故障症状信息匹配。因此，故障问题xx的优先级高于故障问题yy，故障问题yy的优先级高于故障问题zz。用户可以从xx，yy，zz中选取一个作为最终的目标故障问题，也可以顺序对所有匹配的故障问题进行验证和分析，直到成功解决故障问题。
本实施例中，也可以通过诊断仪向服务器发送所述车辆信息和所述车辆的故障症状信息；以使所述服务器根据所述车辆信息和故障症状信息，确定目标故障问题；然后接收服务器反馈的目标故障问题。当目标故障问题为多个时，按照预设的优先级对所述目标故障问题进行排序，得到所述目标故障问题的排序结果；服务器向诊断仪发送排序后的目标故障问题。在诊断仪上显示所述排序结果，并提示用户确认最终的目标故障问题。其中，所述优先级顺序是指：目标故障问题中所包含的故障现象与所述故障症状信息匹配的数量越多，则对应的目标故障问题的优先级越高。
S103、确定与所述目标故障问题对应的解决方案。
本实施例中，可以从本地数据库中搜索与所述目标故障问题对应的所有解决方案；然后显示所有所述解决方案，并根据用户输入的确认信息，确定最终的解决方案。本实施例中的解决方案是指解决目标故障问题的具体流程步骤。可选地，可以按照与所述目标故障问题的相关度显示所有所述解决方案，其中相关度越高的解决方案的显示顺序越靠前。本实施例中的本地数据库是指诊断仪中用于存储故障问题，以及与故障问题相关联的解决方案的存储器。
本实施例中的解决方案包括：诊断流程，通过执行诊断流程中的步骤来确定故障问题所在的器件。例如，以ATF温度传感器短路/开路故障解决方案为例，其诊断流程如下：
步骤1：检查自动变速器线束插头C30、线束插头C31固定是否脱落，或者存在污损；若是，则执行步骤2；若否，则执行步骤3。
步骤2：维修自动变速器线速插头。
步骤3：链接诊断仪，诊断自动跳转至自动变速器系统故障码扫描；检查是否有PXXX1、PXXX2、PXXX3之外的故障码；若是执行步骤4。
步骤4：参考诊断故障码DTC诊断流程向导进行诊断与测试。
本实施例中，还可以通过诊断仪来接收服务器反馈的与所述目标故障问题对应的所有解决方案；然后显示所有所述解决方案，并根据用户输入的确认信息，确定最终的解决方案。可选地，可以按照与所述目标故障问题的相关度显示所有所述解决方案，其中相关度越高的解决方案的显示顺序越靠前。这里的解决方案可以存储在服务器中，也可以是服务器从云端数据库中找到的解决方 案。需要说明的是，本实施例中的解决方案中可以包括：诊断流程，通过执行所述诊断流程，可以定位故障部件、故障产生的原因以及相应的解决方法，以使得维修人员能够根据诊断流程解除故障。
可选地，图2所示方法，还可以包括：
显示与所述目标故障问题对应的解决方案。
可选地，显示与所述目标故障问题对应的解决方案之前，按照解决方案与所述目标故障问题的相关度，对所述目标故障问题对应的解决方案进行排序，得到排序结果；
根据所述排序结果，显示与所述目标故障问题对应的解决方案。
本实施例中，所述解决方案与所述目标故障问题的相关度是根据所述解决方案解决所述目标故障问题的历史解决结果确定的。
在一种实施方式中，可以获取所述目标故障问题对应的解决方案的实施记录；当所述目标故障问题解决成功时，根据预设的评判标准提高所述目标故障问题与对应的解决方案之间的相关度；当所述目标故障问题解决失败时，降低所述目标故障问题与对应的解决方案之间的相关度。诊断仪记录下每次目标故障问题对应的实际实施的解决方案，当目标故障问题被实施的解决方案成功解决时，根据该解决方案的实施条件、实施流程复杂度、解决成功的次数中的至少一项调整该解决方案与对应目标故障问题之间的相关度。其中，解决方案的实施条件简单，实施流程复杂度越低，解决成功次数越多，则该解决方案与对应目标故障问题之间的相关度越高。本实施例中的方法，随着诊断仪诊断的次数的增加，其推荐的解决方案也会越准确。
在另一种实施方式中，可以获取所述目标故障问题对应的解决方案的实施记录；向服务器发送所述目标故障问题对应的解决方案的实施记录，以使所述服务器根据所述实施记录调整所述目标故障问题与对应的解决方案之间的相关度。本实施例中，服务器可以通过诊断仪获取目标故障问题对应的解决方案的实施记录，当目标故障问题被实施的解决方案成功解决时，根据该解决方案的的实施条件、实施流程复杂度、解决成功的次数中的至少一项调整该解决方案与对应目标故障问题之间的相关度。其中，解决方案的实施条件简单，实施流程复杂度越低，解决成功次数越多，则该解决方案与对应目标故障问题之间的相关度越高。本实施例中的方法，随着与服务器通信的诊断仪的诊断次数的增加，其推荐的解决方案也会越准确。
可选地，在所述显示与所述目标故障问题对应的解决方案之后，所述方法还包括：
当与所述目标故障问题对应的解决方案的数量为至少2个时，根据用户针对解决方案的选取操作，选取至少2个解决方案中的目标解决方案。显示所述目标解决方案包括的诊断步骤，以提示用户根据所述诊断步骤对所述车辆进行诊断操作；
获取所述车辆被执行所述诊断操作后的诊断数据和/或诊断结果；
根据所述诊断数据和/或所述诊断结果，显示与所述诊断数据和/或所述诊断结果相关的下一个诊断步骤。
进而可以逐步引导用户执行诊断流程，进而可以精确地根据解决方案得到诊断结果。
本实施例，通过获取车辆的参数信息和故障症状信息；根据所述车辆的参数信息和故障症状信息，确定至少一个目标故障问题；然后根据所述目标故障问题，确定对应的解决方案。采用本发明中的方法，无需对车辆进行全面检测，缩小了故障码、数据流的获取范围，诊断效率高，并能够根据故障症状信息直接对车辆进行诊断，不仅简化了诊断流程，还使得诊断结果更加可靠全面，适用性广。
图4为本发明实施例二提供的车辆诊断方法的流程图，如图4所示，本实施例中的方法可以包括：
S201、获取车辆的故障症状信息。
S202、根据所述车辆的故障症状信息，确定目标故障问题。
S203、确定与所述目标故障问题对应的解决方案。
本实施例中的步骤S201～步骤S203的具体实现过程和技术原理请参考图2所示方法中的相关描述，此处不再赘述。
S204、根据用户对所述解决方案的修改操作，得到所述目标故障问题对应的新的解决方案。
本实施例中，当确定与目标故障问题对应的解决方案之后，用户可以对该解决方案进行修改。例如，对解决方案的诊断流程进行修改，具体地，可以对诊断流程中的步骤进行如下任一或者任多操作：
删减诊断流程中的步骤；
改变诊断流程中步骤的执行顺序；
添加自定义的诊断步骤。
S205、保存所述新的解决方案。
本实施例中，将用户修改后的新的解决方案进行保存。具体地，诊断仪可以将新的解决方案至本地数据库中，并将该新的解决方案与对应的故障问题进行关联。或者诊断仪将新的解决方案发送给服务器，服务器可以将该新的解决方案保存在服务器自身的存储器中，也可以上传至云端数据库，在云端数据库中将该新的解决方案与对应的故障问题进行关联。
本实施例，通过接收用户对所述解决方案的修改，得到新的解决方案，然后保存所述新的解决方案至本地数据库，或者将所述新的解决方案发送给服务器，以使所述服务器将所述新的解决方案保存至云端数据库。从而可以对诊断仪或者云端中存储的解决方案进行更新，使得诊断仪或者云端中包含的解决方案更加全面，以提升故障诊断的精确度。
图5为本发明实施例三提供的车辆诊断装置的结构示意图，如图5所示，本实施例中的装置，可以包括：
获取模块10，用于获取车辆的故障症状信息；
确定模块20，用于根据所述车辆的故障症状信息，确定目标故障问题；
确定模块20，还用于确定与所述目标故障问题对应的解决方案。
实际应用中，本实施例的车辆诊断装置可以为诊断仪，或者可以为服务器，或者还可以为诊断仪和服务器。具体的，当车辆诊断装置为诊断仪和服务器时，获取模块10可以通过诊断仪实现，确定模块20可以通过服务器实现，或者确定模块20也可以通过进行通信交互的诊断仪和服务器实现。可选的，实际应用中不同模块的实现方式有多种，具体可以参照前述方法实施例中举例的实施方式。
可选地，所述获取模块10，还用于获取所述车辆的车辆信息。
所述确定模块20，具体用于：
根据所述车辆的所述车辆信息和所述故障症状信息，确定目标故障问题。
可选地，所述获取模块10，具体用于：接收用户输入的所述车辆的车辆信息；或者，
从所述车辆的电子控制单元ECU中获取所述车辆的车辆信息。
可选地，所述获取模块10，具体用于：
接收用户输入的故障描述信息；
根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息。
可选地，所述根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息，包括：
从本地数据库或云端数据库中获取所述故障描述信息相关的故障症状信息。
本实施例可以执行上述图2、图4所示的方法中的技术方案，其实现过程和技术效果与上述方法类似，此处不再赘述。
图6为本发明实施例四提供的车辆诊断装置的结构示意图，如图6所示，本实施例中的装置在图5所示装置的基础上，还可以包括：
显示模块30，用于在确定与所述故障描述信息相关的至少2个故障症状信息时，显示所述至少2个故障症状信息，以供用户选择；
将用户从所述至少2个故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
可选地，所述获取模块10，还用于：
显示所述车辆的历史故障症状信息和/或预设的常见故障症状信息，以提示用户选取；
将用户从所述历史故障症状信息和/或所述常见故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
可选地，所述确定模块20，具体用于：
从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题。
可选地，所述从与所述车辆的故障症状信息相关的故障问题中，确定目标 故障问题，包括：
获取所述故障问题包括的故障现象；
根据所述车辆出现的故障现象与所述故障问题包括的故障现象的匹配程度，确定目标故障问题。
可选地，所述显示模块30，还用于在根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，显示所述故障现象；
根据用户针对所述故障现象的选取操作，确定所述车辆出现的故障现象。
可选地，所述获取模块10，还用于在根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，从所述车辆的ECU中获取故障数据；
根据所述故障数据确定所述车辆出现的故障现象。
可选地，所述确定模块20，具体用于：
在与所述车辆的故障症状信息相关的故障问题的数量为至少2个时，根据至少2个故障问题的优先级，确定所述至少2个故障问题中的目标故障问题。
可选地，所述确定模块20，具体用于：
从本地数据库或云端数据库中获取与所述目标故障问题对应的解决方案。
可选地，所述装置还包括：
显示模块30，用于显示与所述目标故障问题对应的解决方案。
可选地，所述显示模块，还用于在显示与所述目标故障问题对应的解决方案之前，按照解决方案与所述目标故障问题的相关度，对所述目标故障问题对应的解决方案进行排序，得到排序结果；
根据所述排序结果，显示与所述目标故障问题对应的解决方案。
可选地，所述解决方案与所述目标故障问题的相关度是根据所述解决方案解决所述目标故障问题的历史解决结果确定的。
可选地，所述确定模块20，还用于在显示与所述目标故障问题对应的解决方案之后，当与所述目标故障问题对应的解决方案的数量为至少2个时，根据用户针对解决方案的选取操作，选取至少2个解决方案中的目标解决方案。
可选地，所述显示模块30，还用于：
显示所述目标解决方案包括的诊断步骤，以提示用户根据所述诊断步骤对所述车辆进行诊断操作；
获取所述车辆被执行所述诊断操作后的诊断数据和/或诊断结果；
根据所述诊断数据和/或所述诊断结果，显示与所述诊断数据和/或所述诊断结果相关的下一个诊断步骤。
可选地，所述装置还包括：
存储模块40，用于根据用户对所述解决方案的修改操作，得到所述目标故障问题对应的新的解决方案；保存所述新的解决方案。
本实施例可以执行上述图2、图4所示的方法中的技术方案，其实现过程和技术效果与上述方法类似，此处不再赘述。
图7为本发明实施例五提供的车辆诊断系统的结构示意图，如图7所示， 本实施例中的系统包括：诊断仪50和/或服务器60，所述诊断仪50和/或服务器60用于执行上述图2、图4所示的方法中的技术方案，其实现过程和技术效果与上述方法类似，此处不再赘述。
图8为本发明实施例六提供的车辆诊断设备的结构示意图，如图8所示，本实施例中的车辆诊断设备70包括：
存储器72，用于存储计算机程序(如实现上述诊断功能的应用程序、功能模块等)、计算机指令、数据(如故障症状信息、故障问题、解决方案等)等，上述的计算机程序、计算机指令、数据等可以分区存储在一个或多个存储器72中。并且上述的计算机程序、计算机指令、数据等可以被处理器71调用。
处理器71，用于执行所述存储器72存储的所述计算机程序，以实现上述实施例涉及的方法中的各个步骤。具体可以参见前面方法实施例中的相关描述。
通信接口73，用于实现与车辆的OBD接口通信连接，并实现与服务器通信连接。其中，通信接口73可以包括有线通信接口和无线通信接口。车辆诊断设备可以利用有线通信接口或无线通信接口实现与车辆的OBD接口连接，同理，车辆诊断设备也可以利用有线通信接口或无线通信接口实现与服务器通信连接。
其中，存储器72、处理器71与通信接口73可以通过总线74耦合连接。处理器71可以通过控制通信接口73实现与车辆的通信。
本实施例可以执行上述图2、图4所示的方法中的技术方案，其实现过程和技术效果与上述方法类似，此处不再赘述。
此外，本申请实施例还提供一种计算机可读存储介质，该计算机刻度存储介质中存储有计算机程序，该计算机程序被车辆诊断设备运行时，可以实现上述图2、图4实施例中任一所述的方法。
其中，计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于车辆诊断设备中。当然，处理器和存储介质也可以作为分立组件存在于通信设备中。
本领域普通技术人员可以理解：实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者 对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (39)

  1. 一种车辆诊断方法，其特征在于，包括：
    获取车辆的故障症状信息；
    根据所述车辆的故障症状信息，确定目标故障问题；
    确定与所述目标故障问题对应的解决方案。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    获取所述车辆的车辆信息；
    所述根据所述车辆的故障症状信息，确定目标故障问题，包括：
    根据所述车辆的所述车辆信息和所述故障症状信息，确定目标故障问题。
  3. 根据权利要求2所述的方法，其特征在于，所述获取所述车辆的车辆信息，包括：
    接收用户输入的所述车辆的车辆信息；或者，
    从所述车辆的电子控制单元ECU中获取所述车辆的车辆信息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述获取车辆的故障症状信息，包括：
    接收用户输入的故障描述信息；
    根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息。
  5. 根据权利要求4所述的方法，其特征在于，所述根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息，包括：
    从本地数据库或云端数据库中获取所述故障描述信息相关的故障症状信息。
  6. 根据权利要求4或5所述的方法，其特征在于，所述方法还包括：
    当确定与所述故障描述信息相关的至少2个故障症状信息时，显示所述至少2个故障症状信息，以供用户选择；
    将用户从所述至少2个故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
  7. 根据权利要求1至3中任一项所述的方法，其特征在于，所述获取车辆的故障症状信息，包括：
    显示所述车辆的历史故障症状信息和/或预设的常见故障症状信息，以提示用户选取；
    将用户从所述历史故障症状信息和/或所述常见故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述根据所述车辆的故障症状信息，确定目标故障问题，包括：
    从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题。
  9. 根据权利要求8所述的方法，其特征在于，所述从与所述车辆的故障 症状信息相关的故障问题中，确定目标故障问题，包括：
    获取所述故障问题包括的故障现象；
    根据所述车辆出现的故障现象与所述故障问题包括的故障现象的匹配程度，确定目标故障问题。
  10. 根据权利要求9所述的方法，其特征在于，所述根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，所述方法还包括：
    显示所述故障现象；
    根据用户针对所述故障现象的选取操作，确定所述车辆出现的故障现象。
  11. 根据权利要求9所述的方法，其特征在于，所述根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，所述方法还包括：
    从所述车辆的ECU中获取故障数据；
    根据所述故障数据确定所述车辆出现的故障现象。
  12. 根据权利要求8所述的方法，其特征在于，所述从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题，包括：
    当与所述车辆的故障症状信息相关的故障问题的数量为至少2个时，根据至少2个故障问题的优先级，确定所述至少2个故障问题中的目标故障问题。
  13. 根据权利要求1至12中任一项所述的方法，其特征在于，所述确定与所述目标故障问题对应的解决方案，包括：
    从本地数据库或云端数据库中获取与所述目标故障问题对应的解决方案。
  14. 根据权利要求1至13中任一项所述的方法，其特征在于，所述方法还包括：
    显示与所述目标故障问题对应的解决方案。
  15. 根据权利要求14所述的方法，其特征在于，所述显示与所述目标故障问题对应的解决方案之前，还包括：
    按照解决方案与所述目标故障问题的相关度，对所述目标故障问题对应的解决方案进行排序，得到排序结果；
    所述显示与所述目标故障问题对应的解决方案，包括：
    根据所述排序结果，显示与所述目标故障问题对应的解决方案。
  16. 根据权利要求15所述的方法，其特征在于，所述解决方案与所述目标故障问题的相关度是根据所述解决方案解决所述目标故障问题的历史解决结果确定的。
  17. 根据权利要求14至16中任一项所述的方法，其特征在于，所述显示与所述目标故障问题对应的解决方案之后，所述方法还包括：
    当与所述目标故障问题对应的解决方案的数量为至少2个时，根据用户针对解决方案的选取操作，选取至少2个解决方案中的目标解决方案。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    显示所述目标解决方案包括的诊断步骤，以提示用户根据所述诊断步骤对所述车辆进行诊断操作；
    获取所述车辆被执行所述诊断操作后的诊断数据和/或诊断结果；
    根据所述诊断数据和/或所述诊断结果，显示与所述诊断数据和/或所述诊断结果相关的下一个诊断步骤。
  19. 根据权利要求1至18中任一项所述的方法，其特征在于，所述方法还包括：
    根据用户对所述解决方案的修改操作，得到所述目标故障问题对应的新的解决方案；
    保存所述新的解决方案。
  20. 一种车辆诊断装置，其特征在于，包括：
    获取模块，用于获取车辆的故障症状信息；
    确定模块，用于根据所述车辆的故障症状信息，确定目标故障问题；
    确定模块，还用于确定与所述目标故障问题对应的解决方案。
  21. 根据权利要求20所述的装置，其特征在于，所述获取模块，还用于获取所述车辆的车辆信息；
    所述确定模块，具体用于：
    根据所述车辆的所述车辆信息和所述故障症状信息，确定目标故障问题。
  22. 根据权利要求21所述的装置，其特征在于，所述获取模块，具体用于：接收用户输入的所述车辆的车辆信息；或者，
    从所述车辆的电子控制单元ECU中获取所述车辆的车辆信息。
  23. 根据权利要求20至22中任一项所述的装置，其特征在于，所述获取模块，具体用于：
    接收用户输入的故障描述信息；
    根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息。
  24. 根据权利要求23所述的装置，其特征在于，所述根据所述故障描述信息，获取与所述故障描述信息相关的故障症状信息，包括：
    从本地数据库或云端数据库中获取所述故障描述信息相关的故障症状信息。
  25. 根据权利要求23或24所述的装置，其特征在于，所述装置还包括：
    显示模块，用于在确定与所述故障描述信息相关的至少2个故障症状信息时，显示所述至少2个故障症状信息，以供用户选择；
    将用户从所述至少2个故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
  26. 根据权利要求20至22中任一项所述的装置，其特征在于，所述获取模块，还用于：
    显示所述车辆的历史故障症状信息和/或预设的常见故障症状信息，以提示用户选取；
    将用户从所述历史故障症状信息和/或所述常见故障症状信息中选取的故障症状信息作为所述车辆的故障症状信息。
  27. 根据权利要求20至26中任一项所述的装置，其特征在于，所述确定模块，具体用于：
    从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题。
  28. 根据权利要求27所述的装置，其特征在于，所述从与所述车辆的故障症状信息相关的故障问题中，确定目标故障问题，包括：
    获取所述故障问题包括的故障现象；
    根据所述车辆出现的故障现象与所述故障问题包括的故障现象的匹配程度，确定目标故障问题。
  29. 根据权利要求28所述的装置，其特征在于，所述显示模块，还用于在根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，显示所述故障现象；
    根据用户针对所述故障现象的选取操作，确定所述车辆出现的故障现象。
  30. 根据权利要求28所述的装置，其特征在于，所述获取模块，还用于在根据所述故障现象与所述故障症状信息的匹配程度，确定目标故障问题之前，从所述车辆的ECU中获取故障数据；
    根据所述故障数据确定所述车辆出现的故障现象。
  31. 根据权利要求27所述的装置，其特征在于，所述确定模块，具体用于：
    在与所述车辆的故障症状信息相关的故障问题的数量为至少2个时，根据至少2个故障问题的优先级，确定所述至少2个故障问题中的目标故障问题。
  32. 根据权利要求20至31中任一项所述的装置，其特征在于，所述确定模块，具体用于：
    从本地数据库或云端数据库中获取与所述目标故障问题对应的解决方案。
  33. 根据权利要求20至32中任一项所述的装置，其特征在于，所述装置还包括：
    显示模块，用于显示与所述目标故障问题对应的解决方案。
  34. 根据权利要求33所述的装置，其特征在于，所述显示模块，还用于在显示与所述目标故障问题对应的解决方案之前，按照解决方案与所述目标故障问题的相关度，对所述目标故障问题对应的解决方案进行排序，得到排序结果；
    根据所述排序结果，显示与所述目标故障问题对应的解决方案。
  35. 根据权利要求34所述的装置，其特征在于，所述解决方案与所述目标故障问题的相关度是根据所述解决方案解决所述目标故障问题的历史解决结果确定的。
  36. 根据权利要求33至35中任一项所述的装置，其特征在于，所述确定模块，还用于在显示与所述目标故障问题对应的解决方案之后，当与所述目标故障问题对应的解决方案的数量为至少2个时，根据用户针对解决方案的选取操作，选取至少2个解决方案中的目标解决方案。
  37. 根据权利要求36所述的装置，其特征在于，所述显示模块，还用于：
    显示所述目标解决方案包括的诊断步骤，以提示用户根据所述诊断步骤对所述车辆进行诊断操作；
    获取所述车辆被执行所述诊断操作后的诊断数据和/或诊断结果；
    根据所述诊断数据和/或所述诊断结果，显示与所述诊断数据和/或所述诊断结果相关的下一个诊断步骤。
  38. 根据权利要求20至37中任一项所述的装置，其特征在于，所述装置还包括：
    存储模块，用于根据用户对所述解决方案的修改操作，得到所述目标故障问题对应的新的解决方案；保存所述新的解决方案。
  39. 一种车辆诊断设备，其特征在于，包括：存储器，以及与所述存储器连接的处理器；
    其中，所述存储器存储有计算机程序；
    所述处理器调用所述计算机程序，以执行如权利要求1至19中任一项所述的方法。
PCT/CN2019/079556 2018-04-25 2019-03-25 车辆诊断方法、装置及设备 WO2019205858A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810382862.3A CN108563214B (zh) 2018-04-25 2018-04-25 车辆诊断方法、装置及设备
CN201810382862.3 2018-04-25

Publications (1)

Publication Number Publication Date
WO2019205858A1 true WO2019205858A1 (zh) 2019-10-31

Family

ID=63536871

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/079556 WO2019205858A1 (zh) 2018-04-25 2019-03-25 车辆诊断方法、装置及设备

Country Status (2)

Country Link
CN (1) CN108563214B (zh)
WO (1) WO2019205858A1 (zh)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108563214B (zh) * 2018-04-25 2021-07-06 深圳市道通科技股份有限公司 车辆诊断方法、装置及设备
CN109783313B (zh) * 2018-12-18 2023-03-14 平安科技（深圳）有限公司 一种系统异常处理方法及系统
CN110288100A (zh) * 2019-06-10 2019-09-27 广州思创科技发展有限公司 一种根据车辆故障自动匹配维修项目方法及系统
CN112306034A (zh) * 2019-08-02 2021-02-02 深圳市道通科技股份有限公司 一种汽车维修方法、装置及其系统
CN110781381B (zh) * 2019-09-11 2023-09-01 平安科技（深圳）有限公司 基于神经网络的数据验证方法、装置、设备及存储介质
CN110990519A (zh) * 2019-11-08 2020-04-10 深圳市轱辘汽车维修技术有限公司 一种车辆故障诊断方法、装置、电子设备及存储介质
CN110930131A (zh) * 2019-12-16 2020-03-27 深圳市元征科技股份有限公司 一种车辆维修方法、装置、设备及介质
CN110930538A (zh) * 2019-12-18 2020-03-27 三一重机有限公司 车辆可视化故障信息的方法和系统
CN111414477B (zh) * 2020-03-11 2024-02-13 科大讯飞股份有限公司 车辆故障自动诊断方法、装置以及设备
CN111391865B (zh) * 2020-03-24 2021-08-03 西安法士特汽车传动有限公司 一种纯电动商用车emt自动变速器故障诊断处理系统及方法
CN111679647A (zh) * 2020-05-06 2020-09-18 一汽奔腾轿车有限公司 一种基于车型代码自动匹配标定数据的刷写系统及刷写方法
CN111736571A (zh) * 2020-06-16 2020-10-02 深圳科瑞技术股份有限公司 一种故障诊断系统及方法、存储介质
CN111967614B (zh) * 2020-09-03 2024-02-06 中国联合网络通信集团有限公司 一种人工智能学习方法及装置
CN112034824A (zh) * 2020-09-04 2020-12-04 深圳市云伽智能技术有限公司 汽车诊断方法、装置、设备及计算机可读存储介质
CN112182364A (zh) * 2020-09-11 2021-01-05 上海仙塔智能科技有限公司 用车方案分享方法、服务器及计算机存储介质
CN112148887B (zh) * 2020-09-16 2024-05-03 珠海格力电器股份有限公司 设备故障诊断方法、装置、存储介质和电子设备
CN112874248A (zh) * 2021-02-05 2021-06-01 深圳市道通科技股份有限公司 胎压故障修复方法及相关设备
CN112965871A (zh) * 2021-02-05 2021-06-15 深圳市道通科技股份有限公司 车辆故障提示信息获取方法、装置及存储介质
CN112947382A (zh) * 2021-03-16 2021-06-11 奇瑞新能源汽车股份有限公司 一种汽车故障诊断系统及诊断方法
KR102366017B1 (ko) * 2021-07-07 2022-02-23 쿠팡 주식회사 설치 서비스를 위한 정보 제공 방법 및 장치
CN113552858B (zh) * 2021-07-27 2022-07-22 上海科络达云软件技术有限公司 一种高效的uds诊断系统及方法
CN114022973B (zh) * 2021-11-02 2024-03-01 阿波罗智联(北京)科技有限公司 一种车辆故障的处理方法、装置、设备以及存储介质
CN114185326A (zh) * 2021-11-26 2022-03-15 东风悦享科技有限公司 一种车辆远程诊断方法、系统及存储装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103164724A (zh) * 2013-02-27 2013-06-19 深圳市元征软件开发有限公司 基于二维码技术的汽车诊断装置及方法
CN104181911A (zh) * 2014-07-30 2014-12-03 麦特汽车服务股份有限公司 车辆远程诊断的方法和装置
CN106557773A (zh) * 2015-09-25 2017-04-05 北汽福田汽车股份有限公司 一种车辆故障诊断的方法及系统
CN108563214A (zh) * 2018-04-25 2018-09-21 深圳市道通科技股份有限公司 车辆诊断方法、装置及设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5099436A (en) * 1988-11-03 1992-03-24 Allied-Signal Inc. Methods and apparatus for performing system fault diagnosis
CN103001328B (zh) * 2012-11-19 2014-06-18 山东大学 一种智能变电站的故障诊断与评估方法
CN103592934B (zh) * 2013-11-08 2016-08-24 深圳市道通科技股份有限公司 一种实现汽车诊断的方法、装置和系统
CN105988462A (zh) * 2015-06-30 2016-10-05 陕西同力重工股份有限公司 一种矿区车辆电气故障诊断方法
CN105292021B (zh) * 2015-11-27 2017-09-19 北京汽车研究总院有限公司 一种车载终端系统及汽车
CN105629962A (zh) * 2016-03-03 2016-06-01 中国铁路总公司 高铁列控设备无线闭塞中心rbc系统的故障诊断方法
CN106021545B (zh) * 2016-05-27 2019-12-24 大连楼兰科技股份有限公司 用于车辆远程诊断与备件检索的方法
CN109407646B (zh) * 2017-08-18 2020-06-02 宝沃汽车（中国）有限公司 车辆故障数据的获取方法、装置、存储介质和管理服务器
CN107808430B (zh) * 2017-10-31 2020-01-31 深圳市道通合创软件开发有限公司 计算机可读存储介质、故障检测方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103164724A (zh) * 2013-02-27 2013-06-19 深圳市元征软件开发有限公司 基于二维码技术的汽车诊断装置及方法
CN104181911A (zh) * 2014-07-30 2014-12-03 麦特汽车服务股份有限公司 车辆远程诊断的方法和装置
CN106557773A (zh) * 2015-09-25 2017-04-05 北汽福田汽车股份有限公司 一种车辆故障诊断的方法及系统
CN108563214A (zh) * 2018-04-25 2018-09-21 深圳市道通科技股份有限公司 车辆诊断方法、装置及设备

Also Published As

Publication number Publication date
CN108563214B (zh) 2021-07-06
CN108563214A (zh) 2018-09-21

Similar Documents

Publication Publication Date Title
WO2019205858A1 (zh) 车辆诊断方法、装置及设备
WO2022095790A1 (zh) 一种汽车故障诊断方法、系统和汽车故障诊断仪
US8527441B2 (en) Developing fault model from service procedures
US10474561B2 (en) Method and system for automated testing of human machine interface (HMI) applications associated with vehicles
US7957860B2 (en) Method and system for optimizing vehicle diagnostic trees using similar templates
WO2019141114A1 (zh) 车辆诊断方法和装置
US7373226B1 (en) System and method for optimizing vehicle diagnostic tress using similar templates
WO2017000424A1 (zh) 协议检测方法及装置
CN112965871A (zh) 车辆故障提示信息获取方法、装置及存储介质
CN108021505B (zh) 数据上线方法、装置和计算机设备
US20240028491A1 (en) Automobile Bus Fault Diagnosis Method, Apparatus and Computing Device
EP3865963A1 (en) Method and device for analyzing vehicle failure
CN110471395B (zh) 一种故障检测方法、装置、设备及存储介质
WO2020015471A1 (zh) 汽车诊断方法、装置及存储介质
CN112199277B (zh) 一种基于浏览器的缺陷复现方法、装置、设备及存储介质
CN115080299B (zh) 软件故障反馈处理方法、装置、介质及设备
US10102690B2 (en) Non-starting engine remote diagnostic
CN109101604A (zh) 车辆品牌识别的方法及车辆品牌识别装置
CN113179195A (zh) 一种can报文埋点检测方法、系统、装置及计算机可读存储介质
US20240326838A1 (en) Optimized diagnostic model using vehicle data
CN115373366A (zh) 一种交互式诊断系统、诊断方法及存储介质
CN116107286A (zh) 一种车辆故障的诊断方法、装置、车辆及存储介质
CN113887452A (zh) 基于相关性矩阵的故障诊断优化方法
CN112817800B (zh) 交互设备的测试方法、装置、计算机设备及存储介质
CN117405159A (zh) 车辆故障检测方法、装置、终端设备以及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19792396

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19792396

Country of ref document: EP

Kind code of ref document: A1