Vehicle diagnosis method and related device

Abstract

The present application discloses a vehicle diagnosis method, including: obtaining vehicle model information of a vehicle to be diagnosed; obtaining and executing a target diagnosis file based on the vehicle model information to realize diagnosis of the vehicle to be diagnosed; wherein the target diagnosis file is compiled based on an ODX file and an OTX file corresponding to the vehicle model information. Since the target diagnosis file is compiled based on an ODX file and an OTX file corresponding to the vehicle model information, the data of the corresponding ODX file can be directly used in the diagnosis process without searching for the corresponding data from the ODX file, thereby improving the efficiency of vehicle diagnosis. The present application also discloses a vehicle diagnosis device, a computing device, and a computer-readable storage medium, which have the above beneficial effects.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a vehicle diagnostic method, a vehicle diagnostic device, a computing device, and a computer-readable storage medium. Background Art

[0002] ODX and OTX are generally used in the process of vehicle diagnosis. Among them, ODX (Open Diagnostic Data Exchange) is equivalent to a diagnostic database, which contains the diagnostic commands, algorithms, communication parameters and other data of each ECU of the vehicle, and OTX (Open Test Sequence Exchange Format) is a sequence development standard specially developed for the automotive industry.

[0003] In the related technology, the diagnostic sequence process developed using OTX needs to use the diagnostic data in ODX, so if you want to diagnose a vehicle, you must have both OTX and ODX files at the same time, which will also cause the diagnostic package to be too large. In addition, when OTX is running, it needs to search for the corresponding diagnostic data in ODX multiple times, which will also reduce the efficiency of diagnosis.

[0004] Therefore, how to improve the efficiency of vehicle diagnosis is a key issue that technicians in this field are concerned about. Summary of the invention

[0005] The purpose of this application is to provide a vehicle diagnostic method, a vehicle diagnostic device, a computing device, and a computer-readable storage medium to improve the efficiency of vehicle diagnosis.

[0006] In order to solve the above technical problems, the present application provides a vehicle diagnosis method, comprising:

[0007] Obtain the model information of the vehicle to be diagnosed;

[0008] Based on the vehicle type information, a target diagnostic file is obtained and executed to implement diagnosis of the vehicle to be diagnosed; wherein the target diagnostic file is compiled based on an ODX file and an OTX file corresponding to the vehicle type information.

[0009] Optionally, obtaining the vehicle model information of the vehicle to be diagnosed includes:

[0010] Obtaining the vehicle model information of the vehicle to be diagnosed and the target diagnostic function to be executed;

[0011] Accordingly, the acquiring and executing the target diagnostic file based on the vehicle type information includes:

[0012] Based on the vehicle type information and the target diagnostic function, a corresponding target diagnostic file is obtained and executed; wherein the target diagnostic file is compiled based on the ODX file and the OTX file corresponding to the vehicle type information and the target diagnostic function.

[0013] Optionally, before obtaining the vehicle model information of the vehicle to be diagnosed, the method further includes:

[0014] Obtain at least one OTX file, each of the OTX files corresponding to a diagnostic function of a vehicle type information;

[0015] For each of the OTX files, parse the diagnostic sequence process corresponding to the OTX file to obtain at least one diagnostic node;

[0016] For each of the diagnosis nodes, determining corresponding ODX data to be referenced from the ODX file;

[0017] The reference code in each of the diagnosis nodes is replaced with corresponding ODX data to obtain a diagnosis file corresponding to the OTX file.

[0018] Optionally, the ODX data includes one or more of a diagnostic command, a communication parameter, and a diagnostic algorithm.

[0019] Optionally, when the diagnosis node is a node for creating a communication link, determining corresponding ODX data to be referenced from the ODX file for each diagnosis node includes:

[0020] Based on the reference code corresponding to the node for creating the communication link, communication parameters are obtained from the ODX file, and the communication parameters are used as the ODX data.

[0021] Optionally, when the diagnosis node is a node for obtaining a diagnosis command, determining corresponding ODX data to be referenced from the ODX file for each diagnosis node includes:

[0022] A diagnostic command is obtained from the ODX file based on a reference code corresponding to the node for obtaining the diagnostic command, and the diagnostic command is used as the ODX data.

[0023] Optionally, the process of diagnosing the vehicle to be diagnosed includes:

[0024] The vehicle to be diagnosed is diagnosed based on the diagnostic sequence flow in the target diagnostic file and the corresponding ODX data.

[0025] The present application also provides a vehicle diagnostic device, comprising:

[0026] A vehicle model information determination module is used to obtain the vehicle model information of the vehicle to be diagnosed;

[0027] A vehicle diagnosis module is used to obtain and execute a target diagnosis file based on the vehicle model information to realize the diagnosis of the vehicle to be diagnosed; wherein the target diagnosis file is compiled based on the ODX file and the OTX file corresponding to the vehicle model information.

[0028] The present application also provides a computing device, including:

[0029] Memory for storing computer programs;

[0030] A processor is used to implement the steps of the vehicle diagnosis method as described above when executing the computer program.

[0031] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the vehicle diagnostic method described above are implemented.

[0032] A vehicle diagnostic method provided in the present application includes: obtaining vehicle model information of a vehicle to be diagnosed; obtaining and executing a target diagnostic file based on the vehicle model information to realize diagnosis of the vehicle to be diagnosed; wherein the target diagnostic file is compiled jointly according to an ODX file and an OTX file corresponding to the vehicle model information.

[0033] The vehicle to be diagnosed is diagnosed by acquiring the vehicle model information of the vehicle to be diagnosed, and then acquiring and executing the target diagnostic file based on the vehicle model information. Since the target diagnostic file is compiled based on the ODX file and the OTX file corresponding to the vehicle model information, the data of the corresponding ODX file can be directly used in the diagnosis process without searching for the corresponding data from the ODX file, thereby improving the efficiency of vehicle diagnosis.

[0034] The present application also provides a vehicle diagnostic device, a computing device, and a computer-readable storage medium, which have the above beneficial effects and are not elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0036] Figure 1 A flow chart of a vehicle diagnostic method provided by an embodiment of the present application;

[0037] Figure 2 A schematic diagram of the structure of a vehicle diagnostic device provided in an embodiment of the present application;

[0038] Figure 3 A schematic diagram of the structure of a computing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The core of this application is to provide a vehicle diagnostic method, a vehicle diagnostic device, a computing device and a computer-readable storage medium to improve the efficiency of vehicle diagnosis.

[0040] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0041] In the related art, the diagnostic sequence process developed using OTX needs to use the diagnostic data in ODX, so if you want to diagnose a vehicle, you must download both the OTX and ODX files at the same time. The entire ODX file contains the diagnostic data of all ECUs of all models. However, when diagnosing a vehicle, the ODX data retrieved from the ODX file when running the OTX diagnostic sequence is only a small part. In the prior art, downloading the entire ODX file each time will result in an overly large diagnostic package, and the need to search for the corresponding diagnostic data in ODX multiple times during OTX operation will also reduce the efficiency of diagnosis.

[0042] Therefore, the present application provides a vehicle diagnosis method, which obtains the vehicle model information of the vehicle to be diagnosed, and then obtains and executes the target diagnostic file based on the vehicle model information to realize the diagnosis of the vehicle to be diagnosed. Since the target diagnostic file is compiled based on the ODX file and the OTX file corresponding to the vehicle model information, the data of the corresponding ODX file can be directly used in the diagnosis process without having to search for the corresponding data from the ODX file, thereby improving the efficiency of vehicle diagnosis.

[0043] A vehicle diagnostic method provided by the present application is described below through an embodiment.

[0044] Please refer to Figure 1 , Figure 1 A flow chart of a vehicle diagnostic method provided in an embodiment of the present application.

[0045] In this embodiment, the method may include:

[0046] S101, obtaining vehicle model information of a vehicle to be diagnosed;

[0047] Specifically, the vehicle model information can be determined by obtaining the vehicle's VIN code.

[0048] S102, acquiring and executing a target diagnostic file based on the vehicle model information to implement diagnosis of the vehicle to be diagnosed; wherein the target diagnostic file is compiled based on the ODX file and the OTX file corresponding to the vehicle model information.

[0049] In this embodiment, a target diagnostic file corresponding to the vehicle model information is downloaded from a server according to the vehicle model information of the vehicle to be diagnosed. The target diagnostic file is compiled based on the ODX file and the OTX file corresponding to the vehicle model information. It contains all diagnostic sequence nodes of the OTX file corresponding to the vehicle model, and contains the ODX data corresponding to the vehicle model in the ODX file.

[0050] In this embodiment, the target diagnostic file contains all diagnostic sequence nodes of the OTX file corresponding to the vehicle model. For each diagnostic sequence node, if the ODX data of the vehicle model needs to be referenced, the corresponding ODX data directly replaces the reference of the OTX file. Therefore, when the vehicle is diagnosed, the target diagnostic file can be directly executed without downloading the entire ODX file, which greatly reduces the size of the diagnostic package. Moreover, when the target diagnostic file is executed, there is no need to search for diagnostic data in the ODX file multiple times, which improves the diagnostic efficiency.

[0051] Furthermore, in other embodiments, step S101 may include:

[0052] Step 1, obtaining the vehicle model information of the vehicle to be diagnosed and the target diagnostic function to be executed;

[0053] Step 2, based on the vehicle type information and the target diagnostic function, obtain and execute the corresponding target diagnostic file; wherein the target diagnostic file is compiled based on the ODX file and the vehicle type information and the OTX file corresponding to the target diagnostic function.

[0054] It can be seen that this optional solution mainly explains how to execute the corresponding target diagnostic file based on the target diagnostic function. In the above embodiment, the target diagnostic file is further refined to correspond to the specific functions of a specific vehicle model. The specific application scenario may be: when it is detected that the user has triggered the target diagnostic function, the corresponding target diagnostic file is downloaded from the server and executed based on the current vehicle model information and the currently triggered target diagnostic function. The target diagnostic file in this embodiment is compiled according to the OTX file corresponding to the diagnostic function of the vehicle model and the corresponding ODX data that needs to be referenced.

[0055] In some other embodiments, the target diagnostic file may also be downloaded to the diagnostic device in advance, which is not limited in this solution. Further, the above step 2 may include:

[0056] The vehicle to be diagnosed is diagnosed based on the diagnostic sequence process in the target diagnostic file and the corresponding ODX data.

[0057] Furthermore, in this embodiment, before obtaining the vehicle model information of the vehicle to be diagnosed, it is necessary to compile a diagnostic file. Therefore, this embodiment may also include:

[0058] Step A, obtaining at least one OTX file, each OTX file corresponding to a diagnostic function of a vehicle type information;

[0059] Step B, for each OTX file, parsing the diagnostic sequence process corresponding to the OTX file to obtain at least one diagnostic node;

[0060] Step C, for each diagnosis node, determining the corresponding ODX data to be referenced from the ODX file;

[0061] Step D: Replace the reference code in each diagnosis node with the corresponding ODX data to obtain a diagnosis file corresponding to the OTX file.

[0062] It can be seen that this optional solution mainly explains how to obtain a diagnostic file. In this optional solution, at least one OTX file is obtained, and each OTX file corresponds to a diagnostic function of a vehicle type information; for each OTX file, the diagnostic sequence process corresponding to the OTX file is parsed to obtain at least one diagnostic node; for each diagnostic node, the corresponding ODX data to be referenced is determined from the ODX file; the reference code in each diagnostic node is replaced with the corresponding ODX data to obtain the diagnostic file corresponding to the OTX file.

[0063] The data in the ODX file is the parameter data used in the diagnosis process, and the OTX file is the diagnostic operation sequence data. The diagnostic sequence process includes multiple diagnostic nodes. In the process of executing the diagnostic node, there may be a situation where diagnostic data is needed. The diagnostic data required by the diagnostic node is the data referenced from the ODX file.

[0064] The ODX file includes one or more of a diagnostic command, a communication parameter, and a diagnostic algorithm.

[0065] Furthermore, when the diagnosis node is a node for creating a communication link, for each diagnosis node, the process of determining the corresponding ODX data to be referenced from the ODX file may include:

[0066] The communication parameters are obtained from the ODX file based on the reference code corresponding to the node for creating the communication link, and the communication parameters are used as ODX data.

[0067] It can be seen that this optional solution mainly explains how to determine the referenced ODX data. In this optional solution, when the diagnostic node is a node that creates a communication link, the communication parameters are obtained from the ODX file based on the reference code corresponding to the node that creates the communication link, and the communication parameters are used as ODX data. That is, the communication parameters in the ODX file corresponding to the node that creates the communication link are used as referenced data and added to the diagnostic file.

[0068] Furthermore, when the diagnosis node is a node for obtaining a diagnosis command, for each diagnosis node, the process of determining corresponding ODX data to be referenced from the ODX file may include:

[0069] The diagnostic command is obtained from the ODX file based on the reference code corresponding to the node for obtaining the diagnostic command, and the diagnostic command is used as ODX data.

[0070] It can be seen that this optional solution mainly explains how to determine the referenced ODX data. In this optional solution, when the diagnostic node is a node for obtaining a diagnostic command, the diagnostic command is obtained from the ODX file based on the reference code corresponding to the node for obtaining the diagnostic command, and the diagnostic command is used as ODX data. That is, the diagnostic command corresponding to the node for obtaining the diagnostic command is used as referenced data and added to the diagnostic file.

[0071] In summary, this embodiment obtains the vehicle model information of the vehicle to be diagnosed, and then obtains and executes the target diagnostic file based on the vehicle model information to achieve diagnosis of the vehicle to be diagnosed. Since the target diagnostic file is compiled based on the ODX file and the OTX file corresponding to the vehicle model information, the data of the corresponding ODX file can be directly used in the diagnosis process without having to search for the corresponding data from the ODX file, thereby improving the efficiency of vehicle diagnosis.

[0072] The vehicle diagnostic method provided by the present application is further described below through another specific embodiment.

[0073] In this embodiment, ODX files are all files in XML (Extensible Markup Language) format. ODX mainly stores diagnostic data information of each ECU (Electronic Control Unit) in the car. The entire ODX data model is divided into seven layers: ODX-D, ODX-C, ODX-V, ODX-E, ODX-FD, ODX-F, and ODX-M.

[0074] Among them, the ODX-M part describes certain diagnostic function information implemented by multiple ECUs.

[0075] The ODX-FD part describes function-oriented diagnostic information.

[0076] The ODX-E part describes the vehicle's configuration information, including enabling / disabling optional functions and setting characteristic curves according to specific vehicle environments and locations. It is mainly used in ECU production and after-sales.

[0077] Among them, the ODX-D part mainly describes the communication process between the diagnostic instrument and the ECU, including the request and response format of the diagnostic service and the parameter types used.

[0078] Among them, the ODX-C part describes the communication parameters between the diagnostic instrument and the ECU, such as network layer timing parameters, application layer timing parameters, baud rate, etc.

[0079] Among them, ODX-V describes the vehicle information, such as OEM (original equipment manufacturer) information, vehicle model information, vehicle topology, etc.

[0080] Among them, the ODX-F part mainly describes the uploaded and downloaded data and is used in the online refresh program.

[0081] OTX is also an XML format file, which is mainly used to develop the sequence flow of diagnostic functions (a sequence is executed in a certain order by multiple steps). Each independent diagnostic function can correspond to an OTX file, such as vehicle key matching, writing configuration words to the ECU, ECU replacement, vehicle calibration, etc.

[0082] Once the ODX diagnostic data and OTX diagnostic sequence flow XML files are developed, they can be compiled and merged into one diagnostic file. The compilation process first requires loading the corresponding OTX and ODX files. For example, the key matching OTX file of the BMW 325 model and the ODX file of the 325 model.

[0083] Then, the diagnostic sequence process in the OTX file is parsed and compiled as a unit for each diagnostic node in the process. An OTX process is composed of multiple diagnostic nodes combined in a certain order.

[0084] When processing each node, it is determined whether ODX data is referenced therein. If ODX is not referenced, the node information can be directly output to the compilation diagnosis file as is.

[0085] If the node references data in the ODX file, it is necessary to determine which type of data in the ODX file is referenced. Common references include diagnostic commands, communication parameters, and diagnostic algorithms, and each type requires special processing.

[0086] For example, to create a communication link in the diagnostic node of OTX, you need to obtain the communication parameters from the ODX file. You can open the ODX file, and then find the [Logical Link] information of the ECU through ODX-V, which includes physical communication pins such as 6 and 14. Then find the communication baud rate parameter [CP_Baudrate] of 500000 through ODX-C, and the system communication ID such as [CP_CanPhysReqId] is 0x7E0, [CP_CanRespUSDTId] is 0x 7E8, and other parameters are obtained similarly.

[0087] For example, to obtain diagnostic commands in the OTX diagnostic node, you can search and combine diagnostic commands from the [Diagnosticservices] data part in ODX-D according to the ShortName of the service. For example, if the OTX node wants to send a diagnostic service command with the ShortName of ECUReset, you can search for the diagnostic service information named ECUReset in [Diagnostic services] in ODX-D, and then take out the [Request] command. The command found is 0x1001.

[0088] Finally, after the OTX node obtains the diagnostic data in ODX, it directly replaces the OTX reference part with the found diagnostic data and then outputs it to the compiled diagnostic file.

[0089] After all nodes in the OTX file have been processed, the compilation diagnosis file is generated, which integrates the OTX process and the data in ODX and can be used directly for diagnosis.

[0090] It can be seen that this embodiment first determines the reference data that each diagnostic node in the original diagnostic sequence process needs to use, and then directly replaces the corresponding code in the original diagnostic sequence process with the reference data, so that the corresponding data can be directly used in the diagnostic process without having to search for the data from the original diagnostic data, thereby improving the efficiency of vehicle diagnosis.

[0091] The vehicle diagnostic device provided in an embodiment of the present application is introduced below. The vehicle diagnostic device described below and the vehicle diagnostic method described above can be referenced to each other.

[0092] Please refer to Figure 2 , Figure 2 A schematic diagram of the structure of a vehicle diagnostic device provided in an embodiment of the present application.

[0093] In this embodiment, the device may include:

[0094] The vehicle model information determination module 100 is used to obtain the vehicle model information of the vehicle to be diagnosed;

[0095] The vehicle diagnosis module 200 is used to obtain and execute a target diagnosis file based on the vehicle model information to diagnose the vehicle to be diagnosed; wherein the target diagnosis file is compiled based on the ODX file and the OTX file corresponding to the vehicle model information.

[0096] Optionally, the vehicle model information determination module 100 is specifically used to obtain the vehicle model information of the vehicle to be diagnosed and the target diagnostic function to be executed;

[0097] Correspondingly, the vehicle diagnostic module 200 is specifically used to obtain and execute the corresponding target diagnostic file based on the vehicle model information and the target diagnostic function; wherein the target diagnostic file is compiled based on the ODX file and the vehicle model information and the OTX file corresponding to the target diagnostic function.

[0098] Optionally, the device may further include:

[0099] The diagnostic file fusion module is used to obtain at least one OTX file, each OTX file corresponds to a diagnostic function of a vehicle type information; for each OTX file, the diagnostic sequence process corresponding to the OTX file is parsed to obtain at least one diagnostic node; for each diagnostic node, the corresponding ODX data to be referenced is determined from the ODX file; the reference code in each diagnostic node is replaced with the corresponding ODX data to obtain the diagnostic file corresponding to the OTX file.

[0100] Optionally, the ODX data includes one or more of a diagnostic command, a communication parameter, and a diagnostic algorithm.

[0101] Optionally, the vehicle diagnosis module 200 is specifically configured to perform diagnosis processing on the vehicle to be diagnosed based on the diagnosis sequence flow and corresponding ODX data in the target diagnosis file.

[0102] It can be seen that this embodiment obtains the vehicle model information of the vehicle to be diagnosed, and then obtains and executes the target diagnostic file based on the vehicle model information to achieve the diagnosis of the vehicle to be diagnosed. Since the target diagnostic file is compiled based on the ODX file and the OTX file corresponding to the vehicle model information, the data of the corresponding ODX file can be directly used in the diagnosis process without having to search for the corresponding data from the ODX file, thereby improving the efficiency of vehicle diagnosis.

[0103] This application also provides a computing device, please refer to Figure 3 , Figure 3 A schematic diagram of a computing device provided in an embodiment of the present application may include:

[0104] Memory for storing computer programs;

[0105] The processor is used to implement the steps of any one of the above-mentioned vehicle diagnosis methods when executing the computer program.

[0106] like Figure 3 , which is a schematic diagram of the structure of a computing device, the computing device may include: a processor 10, a memory 11, a communication interface 12 and a communication bus 13. The processor 10, the memory 11 and the communication interface 12 communicate with each other through the communication bus 13.

[0107] In the embodiment of the present application, the processor 10 may be a central processing unit (CPU), an application specific integrated circuit, a digital signal processor, a field programmable gate array or other programmable logic devices, etc.

[0108] The processor 10 may call a program stored in the memory 11. Specifically, the processor 10 may execute operations in an embodiment of the abnormal IP identification method.

[0109] The memory 11 is used to store one or more programs, which may include program codes, and the program codes include computer operation instructions. In the embodiment of the present application, the memory 11 at least stores programs for implementing the following functions:

[0110] Obtain the model information of the vehicle to be diagnosed;

[0111] The target diagnostic file is obtained and executed based on the vehicle model information to realize the diagnosis of the vehicle to be diagnosed; wherein the target diagnostic file is compiled together according to the ODX file and the OTX file corresponding to the vehicle model information.

[0112] In a possible implementation, the memory 11 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function, etc.; the data storage area may store data created during use.

[0113] In addition, the memory 11 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device.

[0114] The communication interface 12 may be an interface of a communication module, and is used to connect to other devices or systems.

[0115] Of course, it should be noted that Figure 3 The structure shown does not constitute a limitation on the computing device in the embodiment of the present application. In actual applications, the computing device may include Figure 3More or fewer components than shown, or combinations of certain components.

[0116] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned vehicle diagnostic methods can be implemented.

[0117] The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0118] For an introduction to the computer-readable storage medium provided in this application, please refer to the above method embodiment, and this application will not go into details here.

[0119] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0120] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0121] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0122] The above is a detailed introduction to a vehicle diagnostic method, a vehicle diagnostic device, a computing device, and a computer-readable storage medium provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

Claims

1. A vehicle diagnostic method, characterized in that: include: Obtain the model information of the vehicle to be diagnosed; Acquire and execute a target diagnostic file based on the vehicle model information to implement diagnosis of the vehicle to be diagnosed; wherein the target diagnostic file is compiled based on the ODX file and the OTX file corresponding to the vehicle model information; Before obtaining the vehicle model information of the vehicle to be diagnosed, the method further includes: Obtain at least one OTX file, each of the OTX files corresponding to a diagnostic function of a vehicle type information; For each of the OTX files, parse the diagnostic sequence process corresponding to the OTX file to obtain at least one diagnostic node; For each of the diagnosis nodes, determining corresponding ODX data to be referenced from the ODX file; The reference code in each of the diagnosis nodes is replaced with corresponding ODX data to obtain a diagnosis file corresponding to the OTX file.

2. The vehicle diagnostic method according to claim 1, characterized in that: The step of obtaining the vehicle model information of the vehicle to be diagnosed includes: Obtaining the vehicle model information of the vehicle to be diagnosed and the target diagnostic function to be executed; Accordingly, the acquiring and executing the target diagnostic file based on the vehicle type information includes: Based on the vehicle type information and the target diagnostic function, a corresponding target diagnostic file is obtained and executed; wherein the target diagnostic file is compiled based on the ODX file and the OTX file corresponding to the vehicle type information and the target diagnostic function.

3. The vehicle diagnostic method according to claim 2, characterized in that: The ODX data includes one or more of a diagnostic command, a communication parameter, and a diagnostic algorithm.

4. The vehicle diagnostic method according to claim 2, characterized in that: When the diagnosis node is a node for creating a communication link, for each of the diagnosis nodes, determining corresponding ODX data to be referenced from the ODX file includes: Based on the reference code corresponding to the node for creating the communication link, communication parameters are obtained from the ODX file, and the communication parameters are used as the ODX data.

5. The vehicle diagnostic method according to claim 2, characterized in that: When the diagnosis node is a node for obtaining a diagnosis command, the step of determining corresponding ODX data to be referenced from the ODX file for each diagnosis node includes: A diagnostic command is obtained from the ODX file based on a reference code corresponding to the node for obtaining the diagnostic command, and the diagnostic command is used as the ODX data.

6. The vehicle diagnostic method according to claim 1, characterized in that: The process of diagnosing the vehicle to be diagnosed includes: The vehicle to be diagnosed is diagnosed based on the diagnostic sequence flow in the target diagnostic file and the corresponding ODX data.

7. A vehicle diagnostic device, characterized in that: include: A vehicle model information determination module is used to obtain the vehicle model information of the vehicle to be diagnosed; A vehicle diagnosis module, used for acquiring and executing a target diagnosis file based on the vehicle model information, so as to realize the diagnosis of the vehicle to be diagnosed; wherein the target diagnosis file is compiled according to the ODX file and the OTX file corresponding to the vehicle model information; It also includes: a diagnostic file fusion module, which is used to obtain at least one OTX file, each OTX file corresponds to a diagnostic function of a vehicle type information; for each OTX file, the diagnostic sequence process corresponding to the OTX file is parsed to obtain at least one diagnostic node; for each diagnostic node, the corresponding ODX data to be referenced is determined from the ODX file; the reference code in each diagnostic node is replaced with the corresponding ODX data to obtain the diagnostic file corresponding to the OTX file.

8. A computing device, characterized in that include: Memory for storing computer programs; A processor is used to implement the steps of the vehicle diagnostic method as claimed in any one of claims 1 to 6 when executing the computer program.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the vehicle diagnostic method according to any one of claims 1 to 6 are implemented.

Images