CN117519079A

CN117519079A - Automobile diagnosis method, electronic device and storage medium

Info

Publication number: CN117519079A
Application number: CN202311502625.3A
Authority: CN
Inventors: 王亚军
Original assignee: Shenzhen Road Tongsheng Software Development Co ltd
Current assignee: Shenzhen Road Tongsheng Software Development Co ltd
Priority date: 2023-11-10
Filing date: 2023-11-10
Publication date: 2024-02-06

Abstract

The embodiment of the application relates to the technical field of vehicle diagnosis, and discloses an automobile diagnosis method, electronic equipment and a storage medium. In the embodiment, visual fault symptoms are taken as input, one or a group of suggested solutions are obtained, the solution adopts guide type to guide operators to operate, the operators can be effectively assisted to rapidly solve the vehicle faults, the operation is simple, the use threshold is low, and the popularization is easy.

Description

Automobile diagnosis method, electronic device and storage medium

Technical Field

The embodiment of the application relates to the technical field of vehicle diagnosis, in particular to an automobile diagnosis method, electronic equipment and a storage medium.

Background

Along with the progress of social development and scientific technology, the design and production of automobiles also increasingly adopt electronic control units (Electronic Control Unit, ECU), so that the automation degree of automobiles is higher and higher, the performance is more excellent, the operation is more convenient and flexible, and higher requirements are put forward on automobile maintenance on the other hand. The traditional manual maintenance mode can not meet the maintenance requirement of the automobile. For this reason, it is necessary to provide a diagnostic device to detect a failure of the vehicle-related system.

Current diagnostic devices typically employ fault diagnosis codes (Diagnostic Trouble Code, DTCs) for fault diagnosis, by reading or interpreting these codes, the diagnostic device is able to determine problems that may exist with the vehicle. However, the fault diagnosis code DTC has limitations such as not necessarily providing detailed description of the problem, missing information, existence of standardized differences or necessity of expertise in interpretation, and the like.

Disclosure of Invention

In view of this, some embodiments of the present application provide an automobile diagnosis method, an electronic device, and a storage medium, which can solve a vehicle failure more accurately, and is simple to operate, low in use threshold, and easy to popularize.

In a first aspect, some embodiments of the present application provide an automobile diagnostic method, comprising:

displaying a first interface for inputting symptoms of a fault;

in response to an operation to input at least one symptom of the fault, a second interface providing a guided solution is displayed.

In some embodiments, the first interface includes a search box, the method further comprising:

receiving information input into a search box;

searching a plurality of selectable fault symptoms from the database according to the information, and displaying a third interface, wherein the selectable fault symptoms are displayed in the form of a symptom tree in the third interface;

the selected at least one selectable symptom of the fault is received to complete the input of the at least one symptom of the fault.

In some embodiments, locating a plurality of selectable symptoms of the fault from the database based on the information includes:

determining at least one keyword from the information;

and searching and matching in the database by adopting at least one keyword to find out a plurality of optional fault symptoms.

In some embodiments, the database includes a plurality of symptom trees covering different vehicle models, and the same fault symptom corresponding to each vehicle model is represented by the same symptom tree.

In some embodiments, the first interface includes a system control, the method further comprising:

responding to the operation of clicking the system control, displaying a fourth interface, and displaying selectable fault symptoms by the fourth interface in a hierarchical menu mode;

the selected selectable fault symptoms are received and input of at least one fault symptom is completed.

In some embodiments, the first interface includes a meter selection area including a plurality of meter controls, the method further comprising:

responsive to clicking the meter control, displaying a fifth interface, the fifth interface including a plurality of selectable fault symptoms;

In some embodiments, the first interface further comprises an intelligent recommendation region, the method further comprising:

displaying common fault symptoms, historical diagnosis fault symptoms, fault symptoms related to fault diagnosis codes or fault symptoms related to searching in an intelligent recommendation area, and taking the common fault symptoms, the historical diagnosis fault symptoms, the fault symptoms related to fault diagnosis codes or the fault symptoms related to searching as optional fault symptoms;

In some embodiments, in response to an operation to enter at least one symptom of a fault, a wizard solution is provided, comprising:

determining a priority of the input at least one symptom of the fault;

the guided solutions for each fault symptom are provided in turn by priority.

In a second aspect, some embodiments of the present application provide an electronic device, including:

at least one processor;

a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the automotive diagnostic method of the first aspect.

In a third aspect, some embodiments of the present application provide a computer-readable storage medium having stored thereon computer-executable instructions for causing a computer device to perform the vehicle diagnostic method of the first aspect.

The beneficial effects of the embodiment of the application are that: in contrast to the situation of the prior art, in the automobile diagnosis method provided by the embodiment of the application, the electronic device displays a first interface for indicating to input the fault symptoms, and after the operator inputs at least one fault symptom in the first interface, the operator jumps to a second interface in response to the operation of inputting the at least one fault symptom, and a guide type solution is provided, wherein the guide type solution is used for providing a guide step for solving the fault. In the embodiment, visual fault symptoms are taken as input, one or a group of suggested solutions are obtained, the solution adopts guide type to guide operators to operate, the operators can be effectively assisted to rapidly solve the vehicle faults, the operation is simple, the use threshold is low, and the popularization is easy.

Drawings

One or more embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which the figures of the drawings are not to be taken in a limiting sense, unless otherwise indicated.

FIG. 1 is a schematic diagram of a diagnostic system in some embodiments of the present application;

FIG. 2 is a schematic diagram of a main interface of a diagnostic terminal according to some embodiments of the present application;

FIG. 3 is a flow chart of a method of diagnosing an automobile in some embodiments of the present application;

FIG. 4 is a schematic diagram of a first interface in some embodiments of the present application;

FIG. 5 is a schematic illustration of a third interface in some embodiments of the present application;

FIG. 6 is a schematic view of a third interface in accordance with further embodiments of the present application;

FIG. 7 is a schematic diagram of a fourth interface in some embodiments of the present application;

FIG. 8 is a schematic illustration of a fifth interface in some embodiments of the present application;

FIG. 9 is a schematic diagram of a second interface and its subordinate interfaces according to some embodiments of the present application;

fig. 10 is a schematic structural diagram of an electronic device according to some embodiments of the present application.

Detailed Description

The present application is described in detail with reference to specific examples. The following examples will assist those skilled in the art in further understanding the present application, but are not intended to limit the present application in any way. It should be noted that variations and modifications could be made by those skilled in the art without departing from the spirit of the present application. These are all within the scope of the present application.

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

It should be noted that, if not conflicting, the various features in the embodiments of the present application may be combined with each other, which is within the protection scope of the present application. In addition, while functional block division is performed in a device diagram and logical order is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the block division in the device, or in the flowchart. Moreover, the words "first," "second," "third," and the like as used herein do not limit the data and order of execution, but merely distinguish between identical or similar items that have substantially the same function and effect.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description of the present application in this description is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The term "and/or" as used in this specification includes any and all combinations of one or more of the associated listed items.

In addition, technical features described below in the various embodiments of the present application may be combined with each other as long as they do not conflict with each other.

Referring to fig. 1, fig. 1 is a schematic view of an application environment of an automobile diagnosis method according to some embodiments of the present application, and a diagnosis system 100 includes an automobile 10, a diagnosis terminal 20 and a server 30, where the diagnosis terminal 20 is respectively connected to the automobile 20 and the server 30 in a communication manner.

In some implementations, the diagnostic terminal 20 may be a tablet computer, a smart phone, or various forms of handheld smart devices, etc. Taking a tablet computer as an example for illustration, the tablet computer is connected to the automobile through a connector in wired communication, in some embodiments, the connector may be an automobile communication interface (vehicle communication interface, VCI). And the OBD interface is used for being connected with the OBD interface of the automobile in a wired way, and the USB interface is used for being connected with the USB interface of the tablet personal computer in a wired way, so that the tablet personal computer and the automobile are connected in a communication way through the connector. The connector (the vehicle communication interface VCI) can convert the data on the bus of the vehicle 10 into the data that can be recognized by the diagnostic terminal 20, or can convert the data issued by the diagnostic terminal 20 into the data that can be recognized by the bus of the vehicle 10, thereby realizing the communication connection between the diagnostic terminal 20 and the vehicle 10.

In some implementations, the diagnostic terminal 20 and the server 30 may be communicatively connected through a wireless network, where the wireless network may be a WIFI or other network. In some embodiments, the server 30 may be a physical server or a cloud server, etc., and no limitation is placed on the server 30 herein. It will be appreciated that the server 30 may serve as a data storage and access center for the diagnostic terminal 20, as well as providing internet-connected services and computing services.

The diagnostic terminal 20 is loaded with a factory application (app) whose front-end interface includes elements of a user interface, an operation mode, a menu, buttons, etc., through which an operator interacts with the application. Illustratively, an operator may communicate with an application by clicking, sliding, entering text, etc., while the application provides services by displaying information, responding to user input. It will be appreciated that the front-end interfaces of the application are separate from the back-end services behind them. The backend is the part that handles application logic, manages data, communicates with databases, etc., and is typically located in a server. The front end and the back end work cooperatively, so that the application can provide comprehensive functions and good user experience.

In some embodiments, the diagnostic terminal 20 includes a touch display screen so as to be able to receive an operation of an operator or an interface displaying an application program, or the like.

For example, referring to fig. 2, the main interface displayed by the diagnostic terminal 20 includes functionality controls such as "diagnose", "maintenance", "anti-theft", "new energy", "remote desktop", "set", "battery detect", and "update". The operator can click on the functional controls and enter the corresponding functional interfaces. For example, clicking on the "diagnosis" functionality control, enters a diagnosis-related interface.

The above is merely an example of the diagnostic system 100, and the diagnostic system 100 may be implemented by other hardware and software. For example, the function of the connector may be implemented by software, and a network communication interface may be added to the software of the diagnostic terminal 20, through which data is transmitted with the server 30. For another example, the application program incorporated in the diagnostic terminal 20 has other functions.

In some solutions known to the inventors of the present application, the interface of the application program in the diagnostic terminal includes an "auto scan" function control, and after the operator clicks the "auto scan" function control, the diagnostic terminal 20 scans each electronic control unit (Electronic Control Unit, ECU) on the vehicle main line, specifically, sends request information to the ECU, receives reply information of the ECU under normal conditions, and generates a fault diagnosis code (Diagnostic Trouble Code, DTC) if the reply information of the ECU is not received. After the scan is completed, the operator may view the list of fault diagnosis codes to know the fault that the car has occurred.

However, the fault diagnosis code DTC has limitations such as not necessarily providing detailed description of the problem, missing information, existence of standardized differences or necessity of expertise in interpretation, and the like. For example, in some cases, the fault diagnostic code is typically only indicative of a problem with a certain system, and does not necessarily provide a detailed description of the problem, requiring further testing and analysis to determine the specific cause of the fault. Different manufacturers, different types of vehicles, may employ different fault diagnosis code criteria, and this difference complicates unified fault diagnosis across different systems or brands. Interpretation of fault diagnosis codes may require specialized skills and knowledge, which may be difficult for an average user or owner to understand. Some potential problems may not generate a significant fault diagnosis code, and thus relying solely on the diagnosis code may ignore certain problems.

In view of the foregoing, an embodiment of the present application provides an automobile diagnosis method, in which an electronic device displays a first interface for indicating input of a fault symptom, and when an operator inputs at least one fault symptom in the first interface, the operator jumps to a second interface in response to an operation of inputting the at least one fault symptom, and a guide-type solution is provided, where the guide-type solution is used to provide a guide step for solving the fault. In the embodiment, visual fault symptoms are taken as input, one or a group of suggested solutions are obtained, the solution adopts guide type to guide operators to operate, the operators can be effectively assisted to rapidly solve the vehicle faults, the operation is simple, the use threshold is low, and the popularization is easy.

The electronic device may be the diagnostic terminal 20 in the above embodiment. As can be appreciated from the foregoing, the automobile diagnosis method provided in the embodiment of the present application may be implemented by an electronic device, for example, by the diagnosis terminal 20 in the foregoing embodiment. Or with the aid of a server communicatively coupled to the electronic device. The electronic device is provided with a touch screen, which is an interface for displaying and interacting with a user.

The automobile diagnosis method provided by the embodiment of the application is described below in connection with exemplary applications and implementations of the electronic device provided by the embodiment of the application. Referring to fig. 3, fig. 3 is a flow chart of an automobile diagnosis method according to an embodiment of the present application. It is understood that the subject of execution of the automotive diagnostic method may be one or more processors of an electronic device.

As shown in fig. 3, the method S100 may specifically include the following steps:

s10: a first interface for entering symptoms of a fault is displayed.

Wherein the first interface is a main interface or a sub-interface of an application program related to automobile diagnosis in the electronic device. Illustratively, the first interface is a sub-interface of an application, and the main interface of the application includes a content area or a bottom navigation bar. The content area comprises functional controls such as symptom diagnosis, maintenance, theft prevention, new energy, remote desktop, setting, battery detection, updating and the like. In some implementations, the first interface is entered when an operator clicks on a "symptom diagnosis" functionality control. In some implementations, the first interface may also be accessed by other sub-interfaces.

As shown in fig. 4, the first interface includes an interactive interface that can input symptoms of a fault, indicating to the operator to input symptoms of a fault. It will be appreciated that the fault symptoms represent operator perceivable fault events, such as visible leakage problems, audible abnormal sound problems, etc. That is, the operator inputs the failure symptom from the first interface after observing the failure symptom sensed by the vehicle. The input of the fault symptoms does not require the operators to have professional automobile repair knowledge, and has universality.

In some embodiments, the first interface includes a search box. As shown in fig. 4, the search box is located below the top menu bar in the first interface. It will be appreciated that the search box is an element in the first interface for receiving information such as a search query or keywords entered by an operator.

In some embodiments, the search box includes a text entry box or search button. For example, an operator may enter text information within a text entry box and click a search button to search. In some embodiments, the search box may also not include a search button, and when no input is entered for a preset time (e.g., 0.3 seconds) after the input is completed, the search is started and the search results are presented in a timely manner.

In some embodiments, the search box further includes a voice button, and the operator can make voice entries by pressing the voice button long. For example, a voice recognition model built in the electronic equipment converts voice into characters to be displayed in a text input box, and after the input is stopped, the search is started to be executed, and the search result is timely displayed.

In this embodiment, the method S100 further includes:

s30: symptom information entered into a search box is received.

The symptom information input into the search box is text information which is input by an operator through a keyboard or voice and reflects fault symptoms. The text information may be one or more words, sentences, or the like. Illustratively, the symptom information entered into the search box is "launch".

It will be appreciated that after the operator enters symptom information in the search box, the processor of the electronic device can receive the symptom information entered in the search box.

S40: and searching a plurality of selectable fault symptoms from the database according to the symptom information, and displaying a third interface, wherein the selectable fault symptoms are displayed in the form of a symptom tree in the third interface.

It will be appreciated that for different vehicle models, there may be different implementations of the system due to differences in different vehicle model structures, components, and naming or routing of fault symptoms. To maintain partial consistency, in this embodiment, the symptoms of the fault are uniformly named using a symptom tree having multiple levels, i.e., the symptom tree names the symptoms of the fault in a hierarchical manner. Illustratively, the symptom tree is divided into less than 5 levels (5 levels are included), the first three levels represent fault symptom paths (less than 3 if insufficient), and the last two levels represent fault symptom descriptions (one level if insufficient). For example, the symptom tree includes 5 levels, the first 3 levels are paths, the 4 th level is a specific fault symptom, the 5 th level is a fault symptom detail or a fault symptom condition, etc.

Wherein, the database refers to a database in which symptom trees are collected. In some embodiments, the database includes a plurality of symptom trees covering different vehicle models, and the same fault symptom corresponding to each vehicle model is represented by the same symptom tree. That is, several symptom trees in the database are different, representing different fault symptoms, and one symptom tree can be matched with multiple vehicle types. Namely, the same symptom tree is adopted for naming a certain fault symptom of various vehicle types. The level of the symptom tree in the database depends on the specific symptom of the fault, that is, the levels of several symptom trees in the database may be different.

And searching a plurality of selectable fault symptoms from the database according to the information when the processor of the electronic equipment acquires the information and searches. After the search is completed, the process jumps to a third interface as shown in fig. 5. The third interface displays a plurality of selectable fault symptoms, namely the selectable fault symptoms are searched symptom trees, and a selection control is arranged behind each selectable fault symptom for the operator to click and select. In some embodiments, when the operator clicks on the search box but does not enter information, the third interface displays a list of historical symptoms of the fault that the operator selected, the list of historical symptoms of the fault being associated with only the current vehicle model. As shown in fig. 6, the near 5 day data is displayed as a set of one diagnosis, with time and selection controls for each symptom of failure. In some embodiments, the first interface includes a control that characterizes the selected list of symptoms of the fault, and clicking on the control displays the selected list of symptoms of the fault.

In some embodiments, the database may also be stored in a server communicatively coupled to the electronic device, and the electronic device may search the database for a plurality of selectable symptoms of the fault based on the information by accessing the server, and send the selectable symptoms of the fault to the electronic device for display.

In some embodiments, the searching the database for the plurality of selectable fault conditions based on the information includes:

s41: determining at least one keyword from symptom information _。

S42: and searching and matching in the database by adopting at least one keyword, and searching a plurality of optional fault symptoms.

The symptom information may be one or more words or sentences, so that at least one keyword may be determined according to the symptom information. In some embodiments, a plurality of keywords are extracted from the parsing from the statement. In some embodiments, each term is directly used as a keyword. In some embodiments, semantic analysis is performed based on the entered symptom information, with a paraphrasing or synonym as a key.

The keywords are adopted to search and match in the database, so that a plurality of optional fault symptoms can be accurately found. It is understood that the search result(s) include matching content including the matched selectable symptoms based on the words in the symptom information and recommended content including the matched selectable symptoms based on the semantic analysis and the synonyms.

In this embodiment, at least one keyword is extracted from the inputted symptom information, and the keywords are used to search and match in the database, so that a plurality of selectable fault symptoms can be accurately found for selection by an operator.

In some embodiments, the input text information may not be disassembled, and a string matching algorithm may be used for searching. Among them, the string matching algorithm is a prior art in the search field, and will not be described in detail here.

S50: the selected at least one selectable symptom of the fault is received and input of the at least one symptom of the fault is completed.

Based on the selection control set after each selectable fault symptom, when the operator clicks the selection control or the corresponding selectable fault symptom, the selectable fault symptom is selected. The processor of the electronic device is capable of receiving the selected selectable symptoms of the fault, thereby completing the input of at least one symptom of the fault.

In this embodiment, by entering information about the observed symptoms of the fault in the search box, the electronic device may search the database for possible selectable symptoms of the fault, and the operator may complete the entry of at least one symptom of the fault upon selection. That is, one or more fault symptoms can be input through searching and selecting modes, so that the operation of operators is facilitated, in addition, the input fault symptoms are unified in naming, easy to identify and convenient for subsequent electronic equipment to calculate an output solution.

In some embodiments, the first interface includes a system control. Referring again to FIG. 4, the system control is located in the "symptom select" area, from which the next level of interface can be entered to select a symptom of failure. It is understood that a system control is a functionality control that triggers entry into a car system selection. For example, the operator clicks on a system control, enters a next level interface or displays a pop-up window with a selection of selectable fault symptoms in the next level interface or pop-up window.

The method S100 further comprises:

s60: responding to the operation of clicking the system control, displaying a fourth interface, and displaying selectable fault symptoms by the fourth interface in a hierarchical menu mode;

s70: the selected selectable fault symptoms are received and input of at least one fault symptom is completed.

After the operator clicks the system control, the electronic device, in response to the operation of the clicking system control, jumps to a fourth interface as shown in fig. 7, in which optional symptoms of the fault are displayed in a hierarchical menu.

Thus, the operator may choose from layer-by-layer to determine the selectable symptoms of the fault, completing the input of the symptoms of the fault. As shown in fig. 7, "gearbox" - "drive" - "front differential" - "transfer case operation inconsistency" - "guest pyridazine" is selected layer by layer, thereby completing the input fault symptom "gearbox > drive > front differential > transfer case operation inconsistency > guest pyridazine".

In some embodiments, if a fault symptom is selected last time, the fault symptom is still in the checked selection state in the current selection to remind the operator.

In this embodiment, by setting the hierarchical menu in the fourth interface, the operator can complete inputting at least one fault symptom after selecting in the hierarchical menu, which is convenient to operate.

In some embodiments, the first interface further includes a sensory control, as shown in fig. 4, located in a "failure symptom selection" area from which a next level of interface can be accessed to select a failure symptom. It is understood that a sensory control is a functional control that triggers entry into a sensory selection. For example, the operator clicks on the sensory control, enters the next level interface or displays a popup window with choices of selectable symptoms of the fault.

In the next level interface of the sensory control, the selectable symptoms of the fault are displayed in a hierarchical menu. When the operator discovers phenomena such as appearance damage, leakage, smoke, peculiar smell, noise, vibration, alarm and the like based on the sense, the operator can click the sense control to select layer by layer to determine optional fault symptoms, and input the fault symptoms.

In this embodiment, by setting the sensory hierarchical menu, the operator can complete inputting at least one fault symptom after selecting in the hierarchical menu, and the operation is convenient.

In some embodiments, the first interface includes a meter selection area including a plurality of meter controls. Referring again to fig. 4, the meter selection area is located below the fault symptom selection area. The instrument control is a functional control which triggers the selection item of the indicator lamp of the entering instrument panel. For example, the operator clicks on the instrument control, enters the next level interface or displays a pop-up window in which there is a selection of selectable fault symptoms for the dashboard indicator.

The method S100 further comprises:

s80: responsive to clicking the meter control, displaying a fifth interface, the fifth interface including a plurality of selectable fault symptoms;

s90: the selected selectable fault symptoms are received and input of at least one fault symptom is completed.

After the operator clicks the instrument control, the electronic device jumps to the fifth interface in response to the operation of clicking the instrument control. As shown in fig. 8, if the instrument control representing "battery and alternator indicator" is clicked, the next stage popup window interface (fifth interface) of "battery and alternator indicator" is entered, in which lamp failure symptoms and related failure symptoms are listed, and a selection control is configured after each failure symptom for the operator to select.

For example, if the operator selects the selection control corresponding to "battery and alternator knowledge point > lamp on" (selectable fault symptom), then the selectable fault symptom is selected. The processor of the electronic device can receive the selected selectable fault symptom, thereby completing the input fault symptom "battery and alternator knowledge point > lamp on.

In this embodiment, by setting the plurality of meter controls, the operator can quickly select the fault symptom associated with the meter by clicking from the meter controls into the fifth interface (including a plurality of selectable fault symptoms associated with the meter), thereby facilitating the operator's operation.

In some embodiments, the first interface further includes an intelligent recommendation area, as shown in fig. 4, located below the meter area. The intelligent recommendation area comprises a plurality of fault symptoms automatically recommended by the electronic equipment.

The method S100 further comprises:

s101: displaying common fault symptoms, historical diagnosis fault symptoms, fault symptoms related to fault diagnosis codes or fault symptoms related to searching in an intelligent recommendation area to serve as optional fault symptoms;

s102: the selected selectable fault symptoms are received and input of at least one fault symptom is completed.

In some embodiments, the symptoms of the faults disclosed by the technical service bulletin (Technical Service Bulletin, TSB) can be summarized and displayed as common symptoms of the faults in the intelligent recommendation area for the operator to quickly select. In some embodiments, the historical diagnosis fault symptoms of the current automobile can be counted, and more historical diagnosis fault symptoms are displayed in the intelligent recommendation area for the operator to quickly select.

In some embodiments, fault symptoms associated with the fault diagnosis code may be displayed in the intelligent recommendation area for quick selection by the operator based on the current scan condition. In some embodiments, based on the search behavior of the operator, the fault symptom associated with the search may be displayed in the intelligent recommendation area, for example, if the operator searches for the fault symptom a, the fault symptom B associated with the fault symptom a is displayed in the intelligent recommendation area for the operator to quickly select.

After the operator clicks the selection control corresponding to the selectable fault symptom in the intelligent recommendation area, the processor of the electronic device receives the selected selectable fault symptom, and accordingly input of one fault symptom is completed.

In this embodiment, by setting the intelligent recommendation area in the first interface, the intelligent recommendation area displays possible selectable fault symptoms, so that the operator can conveniently and quickly select the possible selectable fault symptoms.

S20: in response to an operation to input at least one symptom of the fault, a second interface providing a guided solution is displayed.

Wherein the operation of entering at least one symptom of a fault may include selecting by search, selecting after entering from a system control, selecting after entering from a sensory control, selecting after entering from a meter control, or selecting from an intelligent recommendation area in the implementations described above.

After the processor of the electronic device receives the input of at least one symptom of the fault, a second interface providing a guided solution is displayed. Illustratively, a wizard solution is provided sequentially in the second interface for a plurality of symptoms of the fault. The wizard solution is used to provide a guidance step to resolve the failure.

In some embodiments, the foregoing step S20 specifically includes:

s21: determining a priority of the input at least one symptom of the fault;

s22: the guided solutions for each fault symptom are provided in turn by priority.

In this embodiment, the priority of the input fault symptoms is determined first, considering that the vehicle may have a plurality of fault symptoms, such as jitter associated with abnormal sound of the vehicle.

In some embodiments, the priorities are assigned by setting a priority factor for the symptoms of the failure. Illustratively, priority factors include urgency of service, failure impact range, etc., such as mechanical and electrical combination automotive systems, mechanical failure symptoms take precedence over electrical portion failure symptoms. And setting corresponding weights for each fault symptom in the database after comprehensively considering the priority factors. Thus, for incoming fault symptoms, the order of priority is obtained by ordering the input fault symptoms from high to low in their weights.

In this embodiment, the guided solutions of the respective fault symptoms are provided in order of priority, so that the input fault symptoms can be reasonably solved.

In the following, a guide-type solution will be exemplarily described by taking a fault symptom as an example, referring to (a) in fig. 9, the left side of the second interface is a basic information field, and the right side is a fault symptom analysis field. In the basic information field, a possible cause of the failure symptom or a tool required for solving the failure symptom is displayed. The failure symptom analysis field displays a preliminary inspection step and a visual inspection step to instruct an operator to perform an inspection. After the operator performs the corresponding examination, he can click the "Continue" button in fig. 9 (a), jump to the interface shown in fig. 9 (b), where the left side is the parameter reference table, and the right side is the fault symptom diagnosis guide. In the parameter reference table, values, ranges, units, and the like of some index parameters are displayed, and in the fault symptom diagnosis guide, each flow node and the skip relation are included. Thus, the operator can refer to the parameter reference table, and solve the fault causing the current fault symptom based on the fault symptom diagnosis guide.

As can be seen, embodiments herein provide a varied way of selecting input fault symptoms (search selection, selection after entering from system controls, selection after entering from sensory controls, selection after entering from meter controls, or selection from intelligent recommendation areas), and a guided solution that is simple to operate, does not require operators to have specialized auto repair knowledge, and is ubiquitous. Compared with the limitation of the fault diagnosis code (detailed description of the problem, missing information, standardized difference or professional knowledge required for interpretation, etc. are not necessarily provided), the fault diagnosis code can overcome the defect of the fault diagnosis code in a fault symptom diagnosis mode. In some embodiments, fault symptom diagnosis may be combined with and used by fault diagnosis codes to improve the accuracy of fault diagnosis.

In summary, according to the vehicle diagnosis method provided by the embodiment of the application, the electronic device displays the first interface for indicating to input the fault symptom, and when the operator inputs at least one fault symptom in the first interface, the operator jumps to the second interface in response to the operation of inputting the at least one fault symptom, so as to provide the guided solution. In the embodiment, visual fault symptoms are taken as input, one or a group of suggested solutions are obtained, the solution adopts guide type to guide operators to operate, the operators can be effectively assisted to rapidly solve the vehicle faults, the operation is simple, the use threshold is low, and the popularization is easy.

The embodiment of the application also provides an electronic device, please refer to fig. 10, and fig. 10 is a schematic hardware structure of the electronic device provided in the embodiment of the application. In some embodiments, the electronic device may be a tablet computer, a smart phone, or various forms of handheld smart devices, etc.

As shown in fig. 10, the electronic device 300 comprises at least one processor 301 and a memory 302 (bus connection, one processor being an example in fig. 10) in communication connection.

The processor 301 is configured to provide computing and control capabilities to control the electronic device 300 to perform corresponding tasks, for example, to control the electronic device 300 to perform the automobile diagnostic method in any of the above-described method embodiments.

The processor 301 may be a general purpose processor including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), a hardware chip, or any combination thereof; it may also be a digital signal processor (DigitalS ignal Processing, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), programmable logic device (programmable logic device, PLD), or a combination thereof. The PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), general-purpose array logic (generic array logic, GAL), or any combination thereof.

The memory 302 serves as a non-transitory computer readable storage medium, and may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the automobile diagnostic method in the embodiments of the present application. The processor 301 may implement the automobile diagnosis method in any of the above method embodiments by running non-transitory software programs, instructions and modules stored in the memory 302, and will not be described here again to avoid repetition.

In particular, the memory 302 may include Volatile Memory (VM), such as random access memory (random access memory, RAM); the memory 302 may also include a non-volatile memory (NVM), such as read-only memory (ROM), flash memory (flash memory), hard disk (HDD) or Solid State Drive (SSD), or other non-transitory solid state storage devices; memory 302 may also include a combination of the types of memory described above.

In embodiments of the present application, memory 302 may also include memory located remotely from the processor, which may be connected to the processor via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

In this embodiment of the present application, the electronic device 300 may further have a wired or wireless network interface, a keyboard, an input/output interface, and other components for implementing the functions of the device, which are not described herein.

The present application also provides a computer-readable storage medium, such as a memory, including program code executable by a processor to perform the vehicle diagnostic method of the above embodiments. For example, the computer readable storage medium may be Read-only Memory (ROM), random access Memory (Random Access Memory, RAM), compact disk Read-only Memory (CDROM), magnetic tape, floppy disk, optical data storage device, etc.

Embodiments of the present application also provide a computer program product comprising one or more program codes stored in a computer-readable storage medium. The processor of the electronic device reads the program code from the computer-readable storage medium, and the processor executes the program code to complete the method steps of the automobile diagnosis method provided in the above-described embodiment.

It should be noted that the above-described apparatus embodiments are merely illustrative, and the units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

From the above description of embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus a general purpose hardware platform, or may be implemented by hardware. Those skilled in the art will appreciate that all or part of the processes implementing the methods of the above embodiments may be implemented by a computer program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and where the program may include processes implementing the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-only Memory (ROM), a random-access Memory (Random Access Memory, RAM), or the like.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; the technical features of the above embodiments or in the different embodiments may also be combined under the idea of the present application, the steps may be implemented in any order, and there are many other variations of the different aspects of the present application as described above, which are not provided in details for the sake of brevity; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method of diagnosing an automobile, comprising:

displaying a first interface for inputting symptoms of a fault;

in response to an operation to input at least one symptom of the fault, a second interface is displayed that provides a guided solution, wherein the guided solution is used to provide a guiding step to address the fault.

2. The method of claim 1, wherein the first interface comprises a search box, the method further comprising, prior to the operation of responding to the input of the at least one symptom of the fault:

receiving symptom information entered into the search box;

searching a plurality of selectable fault symptoms from a database according to the symptom information, and displaying a third interface, wherein the selectable fault symptoms are displayed in the form of a symptom tree in the third interface;

receiving the selected at least one selectable symptom of failure and completing the input of the at least one symptom of failure.

3. The method of claim 2, wherein the locating a plurality of selectable fault conditions from the database based on the symptom information comprises:

determining at least one keyword according to the symptom information;

and searching and matching in the database by adopting the at least one keyword, and searching out the plurality of selectable fault symptoms.

4. The method according to claim 2, wherein the database comprises a plurality of symptom trees covering different vehicle types, and the same fault symptoms corresponding to each vehicle type are represented by the same symptom tree.

5. The method of claim 1, wherein the first interface comprises a system control, the method further comprising:

responding to the operation of clicking the system control, displaying a fourth interface, wherein the fourth interface displays selectable fault symptoms in a hierarchical menu mode;

the selected selectable fault symptoms are received and the input of at least one fault symptom is completed.

6. The method of claim 1, wherein the first interface comprises a meter selection area comprising a plurality of meter controls, the method further comprising:

responsive to an operation of clicking the meter control, displaying a fifth interface, the fifth interface comprising a plurality of selectable symptoms of a fault;

7. The method of claim 1, wherein the first interface further comprises an intelligent recommendation area, the method further comprising:

displaying common fault symptoms, historical diagnosis fault symptoms, fault symptoms related to fault diagnosis codes or fault symptoms related to searching in the intelligent recommendation area, and taking the common fault symptoms, the historical diagnosis fault symptoms, the fault symptoms related to fault diagnosis codes or the fault symptoms related to searching as optional fault symptoms;

8. The method of claim 1, wherein providing a guided solution in response to the operation of inputting at least one symptom of a fault comprises:

determining a priority of the input at least one symptom of the fault;

the guided solutions for each fault symptom are provided in turn by priority.

9. An electronic device, comprising:

at least one processor;

a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the automotive diagnostic method of any one of claims 1-8.

10. A computer-readable storage medium storing computer-executable instructions for causing a computer device to perform the vehicle diagnostic method of any one of claims 1-8.