CN111386454A - Vehicle diagnosis method and device and readable storage medium - Google Patents
Vehicle diagnosis method and device and readable storage medium Download PDFInfo
- Publication number
- CN111386454A CN111386454A CN201880075798.2A CN201880075798A CN111386454A CN 111386454 A CN111386454 A CN 111386454A CN 201880075798 A CN201880075798 A CN 201880075798A CN 111386454 A CN111386454 A CN 111386454A
- Authority
- CN
- China
- Prior art keywords
- target
- diagnosis
- subtask
- instruction
- execution path
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01M—TESTING STATIC OR DYNAMIC BALANCE OF MACHINES OR STRUCTURES; TESTING OF STRUCTURES OR APPARATUS, NOT OTHERWISE PROVIDED FOR
- G01M17/00—Testing of vehicles
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
- Testing And Monitoring For Control Systems (AREA)
Abstract
A vehicle diagnostic method includes: acquiring a user instruction; analyzing the user instruction to obtain a corresponding target diagnosis instruction; acquiring a corresponding execution path according to the target diagnosis instruction; executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result; and returning the diagnosis result. The method does not need to interact with the system layer by layer, does not need to read other data except for the diagnosis task, and solves the problems of reading irrelevant data, complicated interaction steps and low response speed in the prior art. A vehicle diagnostic apparatus including the memory, processor, etc., and a readable storage medium are also provided.
Description
The present disclosure relates to the field of vehicle detection technologies, and in particular, to a vehicle diagnostic method, a device and a readable storage medium.
In order to reduce the difficulty of diagnosis and maintenance of an automobile electric control system, automobile manufacturers respectively provide diagnostic tools for respective data analysis and fault diagnosis, but the diagnostic tools are complicated in use, and a user needs to interact with a terminal computer of an automobile for multiple times through the diagnostic tools to select a correct sub-menu path from a multi-level menu, so that information required by a final user can be finally obtained.
To simplify the diagnostic process and automate the diagnosis, some diagnostic devices are configured with commonly used operation functions and operation paths. However, in the prior art, when the so-called diagnosis automation is performed, the operation path is still specified according to the original diagnosis software mode, so that the operation clicked by the user is reduced, a lot of data and interfaces irrelevant to the user purpose are still performed during the execution, and taking a bmw as an example, when the information that the user needs to execute the reading of the fault code of the engine system of the detected vehicle is collected, the diagnosis device still scans all systems of the detected vehicle first, after a system selection item containing the engine system is given, the diagnosis device selects the function menu of the engine system again, then selects the reading of the fault code function option, and then reads the fault code information of the engine system. In fact, such operations read a large amount of data irrelevant to the user's purpose, affecting the response speed of the user's instructions, and displaying such irrelevant data on the user interface may affect the user experience.
Therefore, how to provide a solution to the above technical problems is a problem to be solved by those skilled in the art.
Content of application
In view of the above, an object of the present application is to provide a vehicle diagnostic method, a device and a readable storage medium, which can directly complete a diagnostic task and quickly feed back a user instruction. The specific scheme is as follows:
in a first aspect, the present application discloses a vehicle diagnostic method applied to a diagnostic apparatus, including:
acquiring a user instruction;
analyzing the user instruction to obtain a corresponding target diagnosis instruction;
acquiring a corresponding execution path according to the target diagnosis instruction;
executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result;
and returning the diagnosis result.
Preferably, the process of obtaining a corresponding execution path according to the target diagnosis instruction specifically includes:
judging whether the target diagnosis instruction is matched with a preset quick diagnosis instruction or not, and acquiring a matching result;
and acquiring a corresponding execution path according to the matching result.
Preferably, if the matching result is negative, the process of obtaining the corresponding execution path according to the matching result specifically includes:
determining a target diagnosis task corresponding to the target diagnosis instruction;
judging whether the target diagnosis task can construct a subtask or not;
if so, constructing the subtasks, and determining a target subtask from the subtasks;
and acquiring an execution path of the target subtask.
Preferably, the process of constructing the subtasks of the target diagnosis task and determining the target subtask from the subtasks specifically includes:
acquiring the subtask layer number N of the target diagnosis task, wherein N is a positive integer;
constructing a subtask of a layer 1, and selecting a target subtask of the layer 1 from the subtasks;
constructing an ith layer subtask of an i-1 th layer target subtask, and selecting an ith layer target subtask from the ith layer target subtask, wherein i is 2, 3 … N;
and determining the target subtask of the Nth layer as the target subtask of the target diagnosis task.
Preferably, if the matching result is yes, the process of obtaining the corresponding execution path according to the matching result specifically includes:
searching for a quick diagnosis instruction corresponding to the target diagnosis instruction;
and acquiring an execution path corresponding to the shortcut diagnosis instruction as the execution path of the target diagnosis instruction.
In a second aspect, the present application discloses a vehicle diagnostic apparatus comprising:
a memory for storing a computer program;
a processor for executing the computer program to implement the steps of:
acquiring a user instruction;
analyzing the user instruction to obtain a corresponding target diagnosis instruction;
acquiring a corresponding execution path according to the target diagnosis instruction;
executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result;
and returning the diagnosis result.
Preferably, the process of obtaining a corresponding execution path according to the target diagnosis instruction specifically includes:
judging whether the target diagnosis instruction is matched with a preset quick diagnosis instruction or not, and acquiring a matching result;
and acquiring a corresponding execution path according to the matching result.
Preferably, if the matching result is negative, the process of obtaining the corresponding execution path according to the matching result specifically includes:
determining a target diagnosis task corresponding to the target diagnosis instruction;
judging whether the target diagnosis task can construct a subtask or not;
if so, constructing the subtasks, and determining a target subtask from the subtasks;
and acquiring an execution path of the target subtask.
Preferably, the process of constructing the subtasks of the target diagnosis task and determining the target subtask from the subtasks specifically includes:
acquiring the subtask layer number N of the target diagnosis task, wherein N is a positive integer;
constructing a subtask of a layer 1, and selecting a target subtask of the layer 1 from the subtasks;
constructing an ith layer subtask of an i-1 th layer target subtask, and selecting an ith layer target subtask from the ith layer target subtask, wherein i is 2, 3 … N;
and determining the target subtask of the Nth layer as the target subtask of the target diagnosis task.
Preferably, if the matching result is yes, the process of obtaining the corresponding execution path according to the matching result specifically includes:
searching for a quick diagnosis instruction corresponding to the target diagnosis instruction;
and acquiring an execution path corresponding to the shortcut diagnosis instruction as the execution path of the target diagnosis instruction.
Based on the target sub-task of the previous layer,
in a third aspect, the present application discloses a readable storage medium for use in a diagnostic device, the readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
acquiring a user instruction;
analyzing the user instruction to obtain a corresponding target diagnosis instruction;
acquiring a corresponding execution path according to the target diagnosis instruction;
executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result;
and returning the diagnosis result.
Preferably, the process of obtaining a corresponding execution path according to the target diagnosis instruction specifically includes:
judging whether the target diagnosis instruction is matched with a preset quick diagnosis instruction or not, and acquiring a matching result;
and acquiring a corresponding execution path according to the matching result.
Preferably, if the matching result is negative, the process of obtaining the corresponding execution path according to the matching result specifically includes:
determining a target diagnosis task corresponding to the target diagnosis instruction;
judging whether the target diagnosis task can construct a subtask or not;
if so, constructing the subtasks, and determining a target subtask from the subtasks;
and acquiring an execution path of the target subtask.
Preferably, the process of constructing the subtasks of the target diagnosis task and determining the target subtask from the subtasks specifically includes:
acquiring the subtask layer number N of the target diagnosis task, wherein N is a positive integer;
constructing a subtask of a layer 1, and selecting a target subtask of the layer 1 from the subtasks;
constructing an ith layer subtask of an i-1 th layer target subtask, and selecting an ith layer target subtask from the ith layer target subtask, wherein i is 2, 3 … N;
and determining the target subtask of the Nth layer as the target subtask of the target diagnosis task.
Preferably, if the matching result is yes, the process of obtaining the corresponding execution path according to the matching result specifically includes:
searching for a quick diagnosis instruction corresponding to the target diagnosis instruction;
and acquiring an execution path corresponding to the shortcut diagnosis instruction as the execution path of the target diagnosis instruction.
Thus, it can be seen that the present application discloses a vehicle diagnostic method applied to a diagnostic apparatus, comprising: acquiring a user instruction; analyzing the user instruction to obtain a corresponding target diagnosis instruction; acquiring a corresponding execution path according to the target diagnosis instruction; executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result; and returning the diagnosis result. Because the direct execution path is obtained according to the user instruction, when the diagnosis task is executed, the diagnosis task corresponding to the user instruction can be accurately executed without interacting with the system layer by layer or reading other data except the diagnosis task, the user can be accurately and quickly responded, and the problems of reading irrelevant data, complicated interaction steps and low response speed in the prior art are solved.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
FIG. 1 is a flow chart illustrating steps of a method for vehicle diagnostics according to an embodiment of the present application;
FIG. 2 is a flow chart illustrating sub-steps of a vehicle diagnostic method according to an embodiment of the present application;
fig. 3 is a structural distribution diagram of a vehicle diagnostic apparatus in an embodiment of the present application.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
In order to simplify the vehicle diagnostic process and automate the diagnosis, some diagnostic devices are configured with commonly used operation functions and operation paths in advance. For example, executing a "reading a fault code for an engine system" of a bmw requires configuring a path for reading the fault code after entering the engine system of the bmw on the diagnostic device. When the diagnosis equipment receives an operation instruction of reading an engine fault code by a user, a corresponding execution path is read, after the diagnosis software of the BMW vehicle is entered, an entry function is automatically selected according to the path, and the fault code data of an engine system is read through the automatic data interaction of the diagnosis equipment and a terminal computer of the automobile.
However, in the prior art, when the so-called diagnosis automation is performed, the operation path is still specified according to the original diagnosis software mode, so that the operation clicked by the user is reduced, and a lot of data and interfaces irrelevant to the user purpose are still performed during the execution, for example, when information that the user needs to execute the reading of the fault code of the engine system of the bmw is collected, the diagnosis device still scans all systems of the detected vehicle, after a system selection item containing the engine system is given, the diagnosis device selects the function menu of the engine system again, then selects the reading of the fault code function option, and then reads the fault code information of the engine system. In fact, such operations read a large amount of data irrelevant to the user's purpose, affecting the response speed of the user's instructions, and displaying such irrelevant data on the user interface may affect the user experience.
Because the direct execution path is obtained according to the user instruction, when the diagnosis task is executed, the diagnosis task corresponding to the user instruction can be accurately executed without interacting with the system layer by layer or reading other data except the diagnosis task, the user can be accurately and quickly responded, and the problems of reading irrelevant data, complicated interaction steps and low response speed in the prior art are solved.
The technical scheme disclosed in the application is applied to the Diagnostic equipment for acquiring vehicle Diagnostic data through an OBD (On-Board Diagnostic) connector. In the process of implementing the application, as the vehicle-mounted equipment has various types, the OBD connector and the diagnostic equipment need to select corresponding models and adjust relevant parameters.
The embodiment of the application discloses a vehicle diagnosis method, which is applied to diagnosis equipment, and the steps of the method are shown in a flow chart in figure 1, and comprise the following steps:
s1: acquiring a user instruction;
specifically, the user command is a request command sent by a user and expressing a definite diagnosis purpose, and mainly expresses a requirement in terms of the user, and the user can be a professional maintenance person or the owner himself.
S2: analyzing the user instruction to obtain a corresponding target diagnosis instruction;
generally, the user command has an accurate and strict preset format so as to directly obtain the corresponding target diagnosis command. However, if the user is not a professional maintenance person, the user command may be a fuzzy requirement that the user command is spoken and partial words are omitted, and at this time, the user command needs to be analyzed to obtain a target diagnosis command corresponding to the user command. For example, the user instruction is 'read fault code', and the system of the fault code required by the user instruction cannot be confirmed due to the fuzzy user instruction, so that possible user instructions can be listed, the user can be inquired again, the user can be waited for confirmation, and the user instruction accurately corresponding to the diagnosis task can be obtained; and for example, the user instruction is 'read engine fault code', and the user instruction is supplemented and completed as 'read engine system fault code' when the user instruction is analyzed.
It will be appreciated that the user instructions are for the same essential purpose as the diagnostic task, but the user instructions are requirements expressed from the user's perspective, and the target diagnostic instructions are diagnostic instructions expressed in machine language for the diagnostic device, which are expressed in different forms and in different perspectives. And one user instruction may result in a corresponding plurality of target diagnostic instructions after analysis.
S3: acquiring a corresponding execution path according to the target diagnosis instruction;
s4: executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result;
it is understood that the execution path is closely related to the target diagnosis instruction, and the target diagnosis instruction is executed along the execution path, so that the diagnosis result required by the user can be obtained finally.
S5: and returning the diagnosis result.
It is understood that the method of the present embodiment is generally performed by a processor executing a program in a memory, and therefore step S1 is human-computer interaction, and the processor obtains information of a user; step S2 is an internal algorithm analysis; s3 and S4 are information interaction between the processor and the vehicle-mounted terminal computer; and step S5, performing human-computer interaction, and displaying the final diagnosis result to the user.
The embodiment of the application discloses a vehicle diagnosis method, which is applied to diagnosis equipment and comprises the following steps: acquiring a user instruction; analyzing the user instruction to obtain a corresponding target diagnosis instruction; acquiring a corresponding execution path according to the target diagnosis instruction; corresponding diagnostic tasks and execution paths; executing the target diagnosis instruction diagnosis task according to the execution path, and obtaining a diagnosis result; and returning the diagnosis result. Because the direct execution path is obtained according to the user instruction, when the diagnosis task is executed, the diagnosis task corresponding to the user instruction can be accurately executed without interacting with the system layer by layer or reading other data except the diagnosis task, the user can be accurately and quickly responded, and the problems of reading irrelevant data, complicated interaction steps and low response speed in the prior art are solved.
The embodiment of the application discloses a specific vehicle diagnosis method, and compared with the previous embodiment, the embodiment further explains and optimizes the technical scheme. See in particular fig. 2:
the process of obtaining a corresponding execution path according to the target diagnosis instruction in step S3 specifically includes:
s31: judging whether the target diagnosis instruction is matched with a preset quick diagnosis instruction or not, and acquiring a matching result;
it is understood that the preset shortcut diagnosis instruction is a diagnosis command with a preset execution path. The specific judgment process is that the keywords of the target diagnosis instruction are compared with the preset quick diagnosis instruction one by one, and if the comparison is successful, the matching is successful.
The diagnosis instruction which is not matched with the preset quick diagnosis instruction is generally a diagnosis task which involves more systems and has lower application frequency, the use frequency of the diagnosis instruction which is matched with the diagnosis instruction is higher, and the execution path of the diagnosis instruction needs to be fixed, so that the time for acquiring the execution path each time is saved, and the analysis efficiency is improved.
S32: and acquiring a corresponding execution path according to the matching result.
Specifically, if the matching result is negative, the step S32 of obtaining the corresponding execution path according to the matching result specifically includes:
s3211: determining a target diagnosis task corresponding to the target diagnosis instruction;
s3212: judging whether the target diagnosis task can construct a subtask or not;
s3213: if so, constructing the subtasks, and determining a target subtask from the subtasks;
if not, namely the target diagnosis task does not have a subtask, the execution path of the target diagnosis task is directly obtained.
It will be appreciated that some of the target diagnostic tasks are primary diagnostic tasks, while other target diagnostic tasks include sub-tasks, and even sub-tasks that include a lower level. The first-level diagnosis task is decomposed until all the functional tasks can be embodied, the diagnosis task has a deeper execution path, and due to the fact that the subtasks to be executed are decomposed and confirmed, other tasks which are the same as but unrelated to the subtasks can be omitted in the subsequent process of executing the subtasks according to the execution path, computing power is saved, and only the relevant parts of the subtasks can be accurately computed.
Therefore, the process of constructing the subtasks of the target diagnosis task and determining the target subtask from the subtasks in step S3213 specifically includes:
acquiring the subtask layer number N of the target diagnosis task, wherein N is a positive integer;
constructing a subtask of a layer 1, and selecting a target subtask of the layer 1 from the subtasks;
constructing an ith layer subtask of the ith-1 layer target subtask, and selecting an ith layer target subtask from the ith layer target subtask, wherein i is 2, 3 … N;
and determining the target subtask of the Nth layer as the target subtask of the target diagnosis task.
The process of selecting the target subtask in each layer of subtasks can be completed by analysis and calculation of the diagnosis equipment or by selection of a user through a display interface: and constructing each layer of subtask on the display interface and displaying the subtasks to the user, selecting the target subtask on the layer by the user, acquiring the selection of the user by the diagnosis equipment, constructing the next layer, and sequentially circulating until the Nth layer.
S3214: and acquiring an execution path of the target subtask.
In addition, if the matching result is yes, the process of obtaining the corresponding execution path according to the matching result in step S32 specifically includes:
s3221: searching for a quick diagnosis instruction corresponding to the target diagnosis instruction;
s3222: and acquiring an execution path corresponding to the shortcut diagnosis instruction as the execution path of the target diagnosis instruction.
It can be seen that the subsequent execution of the target diagnosis instruction matching the preset quick diagnosis instruction is far simpler and quicker than that of the unmatched target diagnosis instruction, so that if the execution process of a certain target diagnosis instruction is too frequent, the execution path can be stored in the history record for a long time, that is, the preset quick diagnosis instruction.
Because the direct execution path is obtained according to the user instruction, when the diagnosis task is executed, the diagnosis task corresponding to the user instruction can be accurately executed without interacting with the system layer by layer or reading other data except the diagnosis task, the user can be accurately and quickly responded, and the problems of reading irrelevant data, complicated interaction steps and low response speed in the prior art are solved.
In addition, the target diagnosis instruction is specifically a task code corresponding to an execution action.
It will be appreciated that the subject diagnostic instructions are user instructions in substance, but may be presented in any machine language, including task code.
Taking a certain vehicle type to be diagnosed as an example, the execution actions include "fast test", "system scan", and "system selection". The 'quick test' is to quickly scan the whole vehicle system to obtain the fault code information of the whole vehicle system, does not contain subtasks, and allocates task codes, namely allocates the task ID to be 1; the system scanning is to scan the whole vehicle, scan the supporting system condition of the detected vehicle, does not contain subtasks, and assigns a task ID of 2; and the 'system selection' needs to provide a next level menu for the user to further select the system, including the subtask, so that the subtask under the 'system selection' needs to be constructed except for allocating the corresponding task ID to be 3. The subtasks under the 'system selection' list all possible systems of the detected vehicle, and a task ID is respectively allocated to each system menu, so that the corresponding menu function can be directly executed by specifying the task ID; under each system menu, a corresponding function menu is constructed again, a different task ID is allocated, and task IDs of subtask 'version information', 'fault code reading', 'fault code clearing', 'data stream reading' are specifically allocated as 301, 302, 303 and 304. When the diagnosis equipment obtains the operation that a user needs to execute reading of the engine fault code, the operation is directly converted into calling of diagnosis software, the task ID is designated as 302, the diagnosis software executes a corresponding function according to the task ID, the engine system fault code data of the detected vehicle are read, and the engine system fault code data are returned as a diagnosis result and displayed on the diagnosis equipment.
The embodiment of the application also discloses a vehicle diagnosis device, which is shown in fig. 3 and comprises a processor 11 and a memory 12; wherein the processing 11 implements the following steps when executing the computer program stored in the memory 12:
acquiring a user instruction;
analyzing the user instruction to obtain a corresponding target diagnosis instruction;
acquiring a corresponding execution path according to the target diagnosis instruction;
executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result;
and returning the diagnosis result.
Because the direct execution path is obtained according to the user instruction, when the diagnosis task is executed, the diagnosis task corresponding to the user instruction can be accurately executed without interacting with the system layer by layer or reading other data except the diagnosis task, the user can be accurately and quickly responded, and the problems of reading irrelevant data, complicated interaction steps and low response speed in the prior art are solved.
In some embodiments, when the processor 11 executes the computer sub-program stored in the memory 12, the following steps may be specifically implemented:
judging whether the target diagnosis instruction is matched with a preset quick diagnosis instruction or not, and acquiring a matching result;
and acquiring a corresponding execution path according to the matching result.
In some embodiments, when the processor 11 executes the computer sub-program stored in the memory 12, the following steps may be specifically implemented:
determining a target diagnosis task corresponding to the target diagnosis instruction;
judging whether the target diagnosis task can construct a subtask or not;
if so, constructing the subtasks, and determining a target subtask from the subtasks;
and acquiring an execution path of the target subtask.
In some embodiments, when the processor 11 executes the computer sub-program stored in the memory 12, the following steps may be specifically implemented:
acquiring the subtask layer number N of the target diagnosis task, wherein N is a positive integer;
constructing a subtask of a layer 1, and selecting a target subtask of the layer 1 from the subtasks;
constructing an ith layer subtask of an i-1 th layer target subtask, and selecting an ith layer target subtask from the ith layer target subtask, wherein i is 2, 3 … N;
and determining the target subtask of the Nth layer as the target subtask of the target diagnosis task.
In some embodiments, when the processor 11 executes the computer sub-program stored in the memory 12, the following steps may be specifically implemented:
searching for a quick diagnosis instruction corresponding to the target diagnosis instruction;
and acquiring an execution path corresponding to the shortcut diagnosis instruction as the execution path of the target diagnosis instruction.
Based on the target sub-task of the previous layer,
in some specific embodiments, the vehicle diagnosis apparatus may further include:
the input interface 13 is configured to obtain a computer program imported from the outside, store the obtained computer program in the memory 12, and also be configured to obtain various instructions and parameters transmitted by an external terminal device, and transmit the instructions and parameters to the processor 11, so that the processor 11 performs corresponding processing by using the instructions and parameters. In this embodiment, the input interface 13 may specifically include, but is not limited to, a USB interface, a serial interface, a voice input interface, a fingerprint input interface, a hard disk reading interface, and the like.
And an output interface 14, configured to output various data generated by the processor 11 to a terminal device connected thereto, so that other terminal devices connected to the output interface 14 can acquire various data generated by the processor 11. In this embodiment, the output interface 14 may specifically include, but is not limited to, a USB interface, a serial interface, and the like.
And a communication unit 15 for establishing a remote communication connection between the vehicle diagnosis apparatus and the external server so that the vehicle diagnosis apparatus can mount the image file into the external server. In this embodiment, the communication unit 15 may specifically include, but is not limited to, a remote communication unit based on a wireless communication technology or a wired communication technology.
And the keyboard 16 is used for acquiring various parameter data or instructions input by a user through real-time key cap knocking.
And the display 17 is used for displaying relevant information of the vehicle diagnosis process in real time so that a user can know the current vehicle diagnosis condition and the final diagnosis result in time.
The mouse 18 may be used to assist the user in entering data and to simplify the user's operation.
The application discloses a readable storage medium for a diagnostic device, the readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
acquiring a user instruction;
analyzing the user instruction to obtain a corresponding target diagnosis instruction;
acquiring a corresponding execution path according to the target diagnosis instruction;
executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result;
and returning the diagnosis result.
Because the direct execution path is obtained according to the user instruction, when the diagnosis task is executed, the diagnosis task corresponding to the user instruction can be accurately executed without interacting with the system layer by layer or reading other data except the diagnosis task, the user can be accurately and quickly responded, and the problems of reading irrelevant data, complicated interaction steps and low response speed in the prior art are solved.
In some specific embodiments, the process of obtaining a corresponding execution path according to the target diagnosis instruction specifically includes:
judging whether the target diagnosis instruction is matched with a preset quick diagnosis instruction or not, and acquiring a matching result;
and acquiring a corresponding execution path according to the matching result.
In some specific embodiments, if the matching result is negative, the process of obtaining the corresponding execution path according to the matching result specifically includes:
determining a target diagnosis task corresponding to the target diagnosis instruction;
judging whether the target diagnosis task can construct a subtask or not;
if so, constructing the subtasks, and determining a target subtask from the subtasks;
and acquiring an execution path of the target subtask.
In some specific embodiments, the process of constructing the subtasks of the target diagnosis task and determining the target subtask from the subtasks specifically includes:
acquiring the subtask layer number N of the target diagnosis task, wherein N is a positive integer;
constructing a subtask of a layer 1, and selecting a target subtask of the layer 1 from the subtasks;
constructing an ith layer subtask of an i-1 th layer target subtask, and selecting an ith layer target subtask from the ith layer target subtask, wherein i is 2, 3 … N;
and determining the target subtask of the Nth layer as the target subtask of the target diagnosis task.
In some specific embodiments, if the matching result is yes, the process of obtaining the corresponding execution path according to the matching result specifically includes:
searching for a quick diagnosis instruction corresponding to the target diagnosis instruction;
and acquiring an execution path corresponding to the shortcut diagnosis instruction as the execution path of the target diagnosis instruction.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The present application provides a vehicle diagnostic method, a system, a device and a readable storage medium, which are described in detail above, and the principles and embodiments of the present application are explained herein using specific examples, and the description of the above embodiments is only provided to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (15)
- A vehicle diagnostic method is applied to a diagnostic apparatus, and includes:acquiring a user instruction;analyzing the user instruction to obtain a corresponding target diagnosis instruction;acquiring a corresponding execution path according to the target diagnosis instruction;executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result;and returning the diagnosis result.
- The vehicle diagnostic method according to claim 1, wherein the process of obtaining the corresponding execution path according to the target diagnostic instruction specifically includes:judging whether the target diagnosis instruction is matched with a preset quick diagnosis instruction or not, and acquiring a matching result;and acquiring a corresponding execution path according to the matching result.
- The vehicle diagnostic method according to claim 2, wherein if the matching result is negative, the process of obtaining the corresponding execution path according to the matching result specifically includes:determining a target diagnosis task corresponding to the target diagnosis instruction;judging whether the target diagnosis task can construct a subtask or not;if so, constructing the subtasks, and determining a target subtask from the subtasks;and acquiring an execution path of the target subtask.
- The vehicle diagnostic method according to claim 3, wherein the process of constructing the subtasks of the target diagnostic task and determining the target subtask from the subtasks specifically comprises:acquiring the subtask layer number N of the target diagnosis task, wherein N is a positive integer;constructing a subtask of a layer 1, and selecting a target subtask of the layer 1 from the subtasks;constructing an ith layer subtask of an i-1 th layer target subtask, and selecting an ith layer target subtask from the ith layer target subtask, wherein i is 2, 3 … N;and determining the target subtask of the Nth layer as the target subtask of the target diagnosis task.
- The vehicle diagnostic method according to claim 2, wherein if the matching result is yes, the process of obtaining the corresponding execution path according to the matching result specifically includes:searching for a quick diagnosis instruction corresponding to the target diagnosis instruction;and acquiring an execution path corresponding to the shortcut diagnosis instruction as the execution path of the target diagnosis instruction.
- A vehicle diagnostic apparatus characterized by comprising:a memory for storing a computer program;a processor for executing the computer program to implement the steps of:acquiring a user instruction;analyzing the user instruction to obtain a corresponding target diagnosis instruction;acquiring a corresponding execution path according to the target diagnosis instruction;executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result;and returning the diagnosis result.
- The vehicle diagnostic apparatus according to claim 6, wherein the process of obtaining the corresponding execution path according to the target diagnostic instruction specifically includes:judging whether the target diagnosis instruction is matched with a preset quick diagnosis instruction or not, and acquiring a matching result;and acquiring a corresponding execution path according to the matching result.
- The vehicle diagnostic apparatus according to claim 7, wherein if the matching result is negative, the process of obtaining the corresponding execution path according to the matching result specifically includes:determining a target diagnosis task corresponding to the target diagnosis instruction;judging whether the target diagnosis task can construct a subtask or not;if so, constructing the subtasks, and determining a target subtask from the subtasks;and acquiring an execution path of the target subtask.
- The vehicle diagnostic apparatus according to claim 8, wherein the process of constructing the subtasks of the target diagnostic task and determining the target subtask from the subtasks specifically includes:acquiring the subtask layer number N of the target diagnosis task, wherein N is a positive integer;constructing a subtask of a layer 1, and selecting a target subtask of the layer 1 from the subtasks;constructing an ith layer subtask of an i-1 th layer target subtask, and selecting an ith layer target subtask from the ith layer target subtask, wherein i is 2, 3 … N;and determining the target subtask of the Nth layer as the target subtask of the target diagnosis task.
- The vehicle diagnostic apparatus according to claim 7, wherein if the matching result is yes, the process of obtaining the corresponding execution path according to the matching result specifically includes:searching for a quick diagnosis instruction corresponding to the target diagnosis instruction;and acquiring an execution path corresponding to the shortcut diagnosis instruction as the execution path of the target diagnosis instruction.
- A readable storage medium, for use in a diagnostic device, having a computer program stored thereon, which when executed by a processor, performs the steps of:acquiring a user instruction;analyzing the user instruction to obtain a corresponding target diagnosis instruction;acquiring a corresponding execution path according to the target diagnosis instruction;executing the target diagnosis instruction according to the execution path and obtaining a diagnosis result;and returning the diagnosis result.
- The readable storage medium according to claim 11, wherein the process of obtaining the corresponding execution path according to the target diagnosis instruction specifically includes:judging whether the target diagnosis instruction is matched with a preset quick diagnosis instruction or not, and acquiring a matching result;and acquiring a corresponding execution path according to the matching result.
- The readable storage medium according to claim 12, wherein if the matching result is negative, the process of obtaining the corresponding execution path according to the matching result specifically includes:determining a target diagnosis task corresponding to the target diagnosis instruction;judging whether the target diagnosis task can construct a subtask or not;if so, constructing the subtasks, and determining a target subtask from the subtasks;and acquiring an execution path of the target subtask.
- The readable storage medium according to claim 13, wherein the process of constructing the subtasks of the target diagnostic task and determining the target subtask from the subtasks specifically comprises:acquiring the subtask layer number N of the target diagnosis task, wherein N is a positive integer;constructing a subtask of a layer 1, and selecting a target subtask of the layer 1 from the subtasks;constructing an ith layer subtask of an i-1 th layer target subtask, and selecting an ith layer target subtask from the ith layer target subtask, wherein i is 2, 3 … N;and determining the target subtask of the Nth layer as the target subtask of the target diagnosis task.
- The readable storage medium according to claim 12, wherein if the matching result is yes, the process of obtaining the corresponding execution path according to the matching result specifically includes:searching for a quick diagnosis instruction corresponding to the target diagnosis instruction;and acquiring an execution path corresponding to the shortcut diagnosis instruction as the execution path of the target diagnosis instruction.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2018/102612 WO2020041957A1 (en) | 2018-08-28 | 2018-08-28 | Vehicle diagnostic method and device and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111386454A true CN111386454A (en) | 2020-07-07 |
Family
ID=69643452
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201880075798.2A Pending CN111386454A (en) | 2018-08-28 | 2018-08-28 | Vehicle diagnosis method and device and readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111386454A (en) |
| WO (1) | WO2020041957A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112631254A (en) * | 2020-12-24 | 2021-04-09 | 湖南联科科技有限公司 | Vehicle fault diagnosis method, system, server and storage medium |
| CN112903308A (en) * | 2021-01-20 | 2021-06-04 | 湖南联科科技有限公司 | Performance detection method and device for automobile equipment, electronic equipment and storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113552858B (en) * | 2021-07-27 | 2022-07-22 | 上海科络达云软件技术有限公司 | Efficient UDS diagnosis system and method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9520006B1 (en) * | 2014-08-28 | 2016-12-13 | Allstate Insurance Company | Vehicle diagnostics |
| CN108323189A (en) * | 2017-07-14 | 2018-07-24 | 深圳市元征科技股份有限公司 | Vehicular diagnostic method, terminal device and computer readable storage medium |
| CN108323210A (en) * | 2017-12-28 | 2018-07-24 | 深圳市元征软件开发有限公司 | Vehicle checking method, device, equipment and readable storage medium storing program for executing |
| CN108366115A (en) * | 2018-02-08 | 2018-08-03 | 深圳市轱辘车联数据技术有限公司 | A kind of vehicle OBD connectors management method, system and relevant apparatus |
| CN108416449A (en) * | 2018-02-05 | 2018-08-17 | 北京奇艺世纪科技有限公司 | A kind of O＆M method and apparatus |
-
2018
- 2018-08-28 WO PCT/CN2018/102612 patent/WO2020041957A1/en active Application Filing
- 2018-08-28 CN CN201880075798.2A patent/CN111386454A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9520006B1 (en) * | 2014-08-28 | 2016-12-13 | Allstate Insurance Company | Vehicle diagnostics |
| CN108323189A (en) * | 2017-07-14 | 2018-07-24 | 深圳市元征科技股份有限公司 | Vehicular diagnostic method, terminal device and computer readable storage medium |
| CN108323210A (en) * | 2017-12-28 | 2018-07-24 | 深圳市元征软件开发有限公司 | Vehicle checking method, device, equipment and readable storage medium storing program for executing |
| CN108416449A (en) * | 2018-02-05 | 2018-08-17 | 北京奇艺世纪科技有限公司 | A kind of O＆M method and apparatus |
| CN108366115A (en) * | 2018-02-08 | 2018-08-03 | 深圳市轱辘车联数据技术有限公司 | A kind of vehicle OBD connectors management method, system and relevant apparatus |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112631254A (en) * | 2020-12-24 | 2021-04-09 | 湖南联科科技有限公司 | Vehicle fault diagnosis method, system, server and storage medium |
| CN112903308A (en) * | 2021-01-20 | 2021-06-04 | 湖南联科科技有限公司 | Performance detection method and device for automobile equipment, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020041957A1 (en) | 2020-03-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108304201B (en) | Object updating method, device and equipment | |
| US7340648B2 (en) | User support | |
| CN111386454A (en) | Vehicle diagnosis method and device and readable storage medium | |
| CN112577760A (en) | Method, system, equipment and readable storage medium for vehicle diagnosis | |
| US10902339B2 (en) | System and method providing automatic completion of task structures in a project plan | |
| CN111080170A (en) | Workflow modeling method and device, electronic equipment and storage medium | |
| CN113760359A (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN116304909A (en) | Abnormality detection model training method, fault scene positioning method and device | |
| CN113448936A (en) | Log tracking method, device, server, system and storage medium | |
| US20200321084A1 (en) | Device, system, and method for optimizing pathology workflows | |
| CN112612393B (en) | Interaction method and device of interface function | |
| US20210097787A1 (en) | Information presentation method and apparatus | |
| CN117235527A (en) | End-to-end containerized big data model construction method, device, equipment and medium | |
| US20220172002A1 (en) | Dynamic and continuous composition of features extraction and learning operation tool for episodic industrial process | |
| CN113190458A (en) | Method and device for automatically analyzing buried point data, computer equipment and storage medium | |
| CN111176624B (en) | Method and device for generating stream type calculation index | |
| CN111125336A (en) | Information prompting method, device, equipment and medium | |
| CN112183982A (en) | Workflow creating method and device, computer equipment and storage medium | |
| US11650796B2 (en) | Method for assisting a utilizer in creating a software application and computer program having an implementation of the method and also programming interface usable for such method | |
| JP2020086705A (en) | Information processing system and information processing method | |
| CN113225717B (en) | Control method and device of Bluetooth equipment and computer readable storage medium | |
| CN113065033B (en) | ODX file-based diagnosis method | |
| CN112015656B (en) | Visual debugging method and device for workflow designer | |
| CN114881350A (en) | Execution method and device of prediction task, computer equipment and storage medium | |
| CN114840309A (en) | Dynamic container arranging system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200707 |
|
| RJ01 | Rejection of invention patent application after publication |