Vehicle fault diagnosis method, device, equipment and storage medium

Abstract

The present application discloses a vehicle fault diagnosis method, device, equipment and storage medium, the method comprising: obtaining an identification code of a vehicle to be diagnosed, analyzing the identification code to obtain a material number list of the vehicle to be diagnosed, and determining an ODX file group corresponding to the material number list; wherein the vehicle to be diagnosed comprises a controller group for controlling the vehicle to be diagnosed and a controller in the controller group; parsing the ODX file group to obtain a diagnostic instruction for the controller in the controller group; based on the diagnostic instruction, diagnosing the controller corresponding to the diagnostic instruction to obtain a diagnostic result. The present application only needs to obtain a vehicle identification code and a detection request to diagnose the vehicle, and does not require other diagnostic equipment, thereby reducing the use of diagnostic equipment and reducing the complexity of operations during vehicle fault diagnosis.

Description

Technical Field

[0001] The present application relates to the field of vehicle maintenance technology, and in particular to a vehicle fault diagnosis method, device, equipment and storage medium. Background Art

[0002] As vehicle performance improves and vehicle structure becomes more complex, the difficulty of vehicle fault diagnosis also increases.

[0003] At present, there are two methods for vehicle fault diagnosis: manual diagnosis and instrument diagnosis. In practical applications, the two methods are usually used in combination. The vehicle is initially inspected manually, and then the vehicle fault is further screened and confirmed by instrument diagnosis. However, when using the diagnostic equipment, it is necessary to select the corresponding diagnostic equipment based on the vehicle model. After connecting the diagnostic equipment, it is necessary to select the vehicle information and determine the version of the diagnostic file, which makes the operation complicated during the vehicle fault diagnosis process. Summary of the invention

[0004] The main purpose of the present application is to provide a vehicle fault diagnosis method, device, equipment and storage medium, aiming to solve the technical problem of complex operation process in the vehicle fault diagnosis process in the prior art.

[0005] To achieve the above object, the present application provides a vehicle fault diagnosis method, the vehicle fault diagnosis method comprising:

[0006] Obtaining an identification code of the vehicle to be diagnosed, analyzing the identification code to obtain a material number list of the vehicle to be diagnosed, and determining an ODX file group corresponding to the material number list;

[0007] Wherein, the vehicle to be diagnosed includes a controller group for controlling the vehicle to be diagnosed and a controller in the controller group;

[0008] Parsing the ODX file group to obtain diagnostic instructions of controllers in the controller group;

[0009] Based on the diagnosis instruction, a controller corresponding to the diagnosis instruction is diagnosed to obtain a diagnosis result.

[0010] Optionally, before the step of obtaining the identification code of the vehicle to be diagnosed, the method includes:

[0011] Parsing the preset diagnostic information in each of the controller groups to obtain a diagnostic service information table in a tabular format, wherein the preset diagnostic information is preset in the controller;

[0012] Convert the diagnostic service information table into an ODX format to obtain an ODX information table in an ODX format;

[0013] The ODX information table is converted into the Json format to obtain a Json file group for generating the diagnostic instruction.

[0014] Optionally, the preset diagnostic information is a table format file;

[0015] The step of parsing the preset diagnostic information to obtain a diagnostic service information table in a tabular format includes:

[0016] Parsing and screening the preset diagnostic information, removing repeated first diagnostic information in the preset diagnostic information, and obtaining second diagnostic information without repeated data;

[0017] The second diagnostic information is integrated and classified to obtain a diagnostic service information table in a tabular format.

[0018] Optionally, the step of parsing the ODX file group to obtain the diagnostic instructions of the controllers in the controller group includes:

[0019] Parsing the ODX file group to obtain a first ODX file in the ODX file group, and determining a controller in the detection vehicle that corresponds to the first ODX file and needs to be diagnosed;

[0020] analyzing the controller to determine third diagnostic information in the controller;

[0021] A first Json file in the Json file group corresponding to the third diagnostic information is obtained, and a diagnostic instruction of the vehicle to be diagnosed is obtained based on the first Json file.

[0022] Optionally, the step of parsing the ODX file group to obtain a first ODX file in the ODX file group, and determining a controller in the detection vehicle corresponding to the first ODX file and requiring diagnosis, comprises:

[0023] Analyze the ODX file group to obtain the first ODX file in the ODX file group;

[0024] Based on the first ODX file, analyzing the material number list to determine a first material number corresponding to the first ODX file;

[0025] Based on the first material number, determining a component to be diagnosed in the vehicle to be diagnosed that corresponds to the first material number;

[0026] A subordinate query process is performed on the component to be diagnosed to determine a controller in the detection vehicle that corresponds to the first ODX file and needs to be diagnosed.

[0027] Optionally, the step of obtaining the identification code of the vehicle to be diagnosed, analyzing the identification code to obtain a material number list of the vehicle to be diagnosed, and determining an ODX file group corresponding to the material number list includes:

[0028] Obtaining an identification code of the vehicle to be diagnosed, analyzing the identification code, and determining the model and production batch of the vehicle to be diagnosed;

[0029] Based on the production batch of the model, obtain a list of material numbers of the vehicle to be diagnosed;

[0030] The material number list includes the second material number of each component constituting the vehicle to be diagnosed;

[0031] Determine whether there is a second ODX file corresponding to the second material number in the ODX information table;

[0032] If a second ODX file corresponding to the material number exists in the ODX information table, determining a second ODX file corresponding to the second material number;

[0033] The second ODX file is integrated to obtain an ODX file group corresponding to the material number list.

[0034] Optionally, the step of diagnosing a controller corresponding to the diagnostic instruction based on the diagnostic instruction to obtain a diagnostic result includes:

[0035] Based on the diagnostic instruction, obtaining preset diagnostic information in a controller corresponding to the diagnostic instruction;

[0036] Analyzing based on the preset diagnostic information, extracting a second ODX file corresponding to the controller from the ODX information table;

[0037] Parsing the second ODX file to obtain configuration information and fault codes of the vehicle to be diagnosed;

[0038] The diagnostic result includes at least one of configuration information and a fault code.

[0039] The present application also provides a vehicle fault diagnosis device, the vehicle fault diagnosis device comprising:

[0040] An analysis module, used for obtaining an identification code of a vehicle to be diagnosed, analyzing the identification code to obtain a material number list of the vehicle to be diagnosed, and determining an ODX file group corresponding to the material number list;

[0041] Wherein, the vehicle to be diagnosed includes a controller group for controlling the vehicle to be diagnosed and a controller in the controller group;

[0042] A parsing module, used for parsing the ODX file group to obtain diagnostic instructions of controllers in the controller group;

[0043] The diagnosis module is used to diagnose the controller corresponding to the diagnosis instruction based on the diagnosis instruction to obtain a diagnosis result.

[0044] Optionally, the vehicle fault diagnosis device further includes:

[0045] A first parsing submodule, configured to parse the preset diagnostic information in each of the controller groups to obtain a diagnostic service information table in a tabular format, wherein the preset diagnostic information is preset in the controller;

[0046] A first format conversion module, used for converting the diagnostic service information table into an ODX format to obtain an ODX information table in an ODX format;

[0047] The second format conversion module is used to convert the ODX information table into a Json format to obtain a Json file group used to generate the diagnostic instruction.

[0048] Optionally, the preset diagnostic information is a table format file;

[0049] The first parsing submodule includes:

[0050] A screening module, used for parsing and screening the preset diagnostic information, removing repeated first diagnostic information in the preset diagnostic information, and obtaining second diagnostic information without repeated data;

[0051] The integration module is used to integrate and classify the second diagnostic information to obtain a diagnostic service information table in a tabular format.

[0052] Optionally, the parsing module includes:

[0053] A parsing submodule, configured to parse the ODX file group to obtain a first ODX file in the ODX file group, and determine a controller in the detection vehicle that corresponds to the first ODX file and needs to be diagnosed;

[0054] a first analyzing unit, configured to analyze the controller and determine third diagnostic information in the controller;

[0055] An acquisition unit is used to acquire a first Json file in the Json file group corresponding to the third diagnostic information, and obtain a diagnostic instruction of the vehicle to be diagnosed based on the first Json file.

[0056] Optionally, the analysis module includes:

[0057] A second analysis unit is used to obtain an identification code of the vehicle to be diagnosed, analyze the identification code, and determine the model and production batch of the vehicle to be diagnosed;

[0058] A matching module, used for obtaining a list of material numbers of the vehicle to be diagnosed based on the production batch of the model;

[0059] The material number list includes the second material number of each component constituting the vehicle to be diagnosed;

[0060] A judging module, used for judging whether there is a second ODX file corresponding to the second material number in the ODX information table;

[0061] a determination module, configured to determine the second ODX file corresponding to the second material number if a second ODX file corresponding to the material number exists in the ODX information table;

[0062] The integration unit is used to integrate the second ODX file to obtain an ODX file group corresponding to the material number list.

[0063] Optionally, the diagnosis module includes:

[0064] A matching unit, configured to obtain, based on the diagnostic instruction, preset diagnostic information in a controller corresponding to the diagnostic instruction;

[0065] A third analyzing unit, configured to perform analysis based on the preset diagnostic information and extract a second ODX file corresponding to the controller from the ODX information table;

[0066] A parsing unit, used for parsing the second ODX file to obtain the configuration information and fault code of the vehicle to be diagnosed;

[0067] The diagnostic result includes at least one of configuration information and a fault code.

[0068] The present application also provides a vehicle fault diagnosis device, which is a physical node device, and includes: a memory, a processor, and a program of the vehicle fault diagnosis method stored in the memory and executable on the processor. When the program of the vehicle fault diagnosis method is executed by the processor, the steps of the vehicle fault diagnosis method as described above can be implemented.

[0069] The present application also provides a storage medium, on which is stored a program for implementing the above-mentioned vehicle fault diagnosis method. When the program of the vehicle fault diagnosis method is executed by a processor, the steps of the above-mentioned vehicle fault diagnosis method are implemented.

[0070] The present application provides a vehicle fault diagnosis method, apparatus, equipment and storage medium. Compared with the prior art which requires adapting the vehicle and the diagnostic equipment, and selecting the information of the vehicle to be diagnosed and the diagnostic file, etc., resulting in complicated operations during the vehicle fault diagnosis process, in the present application, an identification code of the vehicle to be diagnosed is obtained, the identification code is analyzed to obtain a material number list of the vehicle to be diagnosed, and an ODX file group corresponding to the material number list is determined; wherein, the vehicle to be diagnosed includes a controller group for controlling the vehicle to be diagnosed and a controller in the controller group; the ODX file group is parsed to obtain diagnostic instructions for the controller in the controller group; based on the diagnostic instructions, the controller corresponding to the diagnostic instructions is diagnosed to obtain a diagnostic result. In the present application, it is only necessary to obtain an ODX file group corresponding to the material number list of the vehicle to be diagnosed based on the identification code of the vehicle to be diagnosed, obtain a diagnostic instruction based on the ODX file group, diagnose the vehicle to be diagnosed based on the diagnostic instruction, and obtain a diagnostic result of the vehicle to be diagnosed. That is, in the present application, it is only necessary to obtain the vehicle identification code and the detection request to diagnose the vehicle, and no other diagnostic equipment is required, thereby reducing the use of diagnostic equipment and reducing the complexity of operations during vehicle fault diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0072] 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, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0073] Figure 1 This is a flow chart of the first embodiment of the vehicle fault diagnosis method of the present application;

[0074] Figure 2 This is a flow chart of a second embodiment of the vehicle fault diagnosis method of the present application;

[0075] Figure 3 This is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present application.

[0076] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0077] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0078] The present application provides a vehicle fault diagnosis method. In the first embodiment of the vehicle fault diagnosis method of the present application, refer to Figure 1 , the vehicle fault diagnosis method comprises:

[0079] Step S10, obtaining an identification code of the vehicle to be diagnosed, analyzing the identification code to obtain a material number list of the vehicle to be diagnosed, and determining an ODX file group corresponding to the material number list;

[0080] Wherein, the vehicle to be diagnosed includes a controller group for controlling the vehicle to be diagnosed and a controller in the controller group;

[0081] Step S20, parsing the ODX file group to obtain diagnostic instructions of the controllers in the controller group;

[0082] Step S30: based on the diagnostic instruction, diagnose the controller corresponding to the diagnostic instruction to obtain a diagnostic result.

[0083] The specific steps are as follows:

[0084] Step S10, obtaining an identification code of the vehicle to be diagnosed, analyzing the identification code to obtain a material number list of the vehicle to be diagnosed, and determining an ODX file group corresponding to the material number list;

[0085] Wherein, the vehicle to be diagnosed includes a controller group for controlling the vehicle to be diagnosed and a controller in the controller group;

[0086] In this embodiment, it should be noted that the vehicle fault diagnosis method can be applied to a vehicle fault diagnosis device, which belongs to a vehicle fault diagnosis equipment, and the vehicle fault diagnosis equipment belongs to a vehicle fault diagnosis system.

[0087] For the vehicle fault diagnosis system, a terminal, a management background, and an ODX (Open Diagnosticdata exchange) file tool are built in. It should be noted that the ODX file tool can be set in the management background.

[0088] Specifically, the terminal can obtain the user's request information, send the identification code of the vehicle to be diagnosed to the management background, and display the diagnosis result.

[0089] Specifically, the terminal can be but is not limited to a mobile phone, a computer, a tablet, etc.

[0090] Specifically, the management background includes a material number list, and the management background is used to generate a diagnosis instruction.

[0091] The ODX file tool is used to convert the diagnostic service information table in a table format into an ODX file group in an ODX format, and to convert the file group in the ODX format into a file group in a Json format.

[0092] The identification code may be, but is not limited to, a sequence of numbers, a sequence of letters, a mixed sequence of numbers and letters, and the like.

[0093] The material numbers in the material number list are the numbers of the parts in the vehicle, and the material number list is a list of the numbers of the parts.

[0094] In this embodiment, the identification code of the vehicle to be diagnosed is first obtained, wherein the method for obtaining the identification code of the vehicle to be diagnosed may be:

[0095] Method 1: It can be input through voice. If a voice command is detected, the voice information in the voice command is extracted and the identification code is obtained from the voice information.

[0096] Method 2: An inquiry interface may also be provided to obtain the identification code based on information input on the inquiry interface.

[0097] In this embodiment, the identification code of the vehicle to be diagnosed is obtained, and the identification code is analyzed to obtain a material number list of the vehicle to be diagnosed, and the diagnostic information corresponding to the second material number in the material number list is extracted from a preset ODX file tool, that is, the second ODX file, and the second ODX file is integrated to obtain an ODX file group corresponding to the material number list.

[0098] Specifically, the steps of obtaining the identification code of the vehicle to be diagnosed, analyzing the identification code, obtaining the material number list of the vehicle to be diagnosed, and determining the ODX file group corresponding to the material number list include:

[0099] Step S11, obtaining an identification code of the vehicle to be diagnosed, analyzing the identification code, and determining the model and production batch of the vehicle to be diagnosed;

[0100] Step S12 obtains a list of material numbers of the vehicle to be diagnosed based on the production batch of the model;

[0101] The material number list includes the second material number of each component constituting the vehicle to be diagnosed;

[0102] Step S13, determining whether there is a second ODX file corresponding to the second material number in the ODX information table;

[0103] Step S14, if there is a second ODX file corresponding to the material number in the ODX information table, determining the second ODX file corresponding to the second material number;

[0104] Step S15, integrating the second ODX files to obtain an ODX file group corresponding to the material number list.

[0105] Among them, the identification code can identify basic information such as the model, production batch, material number composition, etc. of the vehicle to be diagnosed.

[0106] It should be noted that vehicles of the same model in the same production batch use the same parts during production, and the material numbers of the same parts for each vehicle are also the same.

[0107] In this embodiment, the identification code of the diagnosed vehicle can be obtained through the terminal and sent to the management background. The management background analyzes the identification code to determine the model and production batch of the vehicle to be diagnosed. Based on the production batch of the model, the material number list of the vehicle to be diagnosed is obtained from the material library preset by the management background. The second material number in the material number list is matched with the ODX information table, and it is determined whether there is a second ODX file corresponding to the second material number in the ODX information table. If the second ODX file exists in the ODX information table, the second ODX file is integrated to obtain an ODX file group corresponding to the material number list.

[0108] In this embodiment, if the second ODX file does not exist in the ODX information table, the terminal prompts that the vehicle to be detected does not support diagnosis.

[0109] Step S20, parsing the ODX file group to obtain diagnostic instructions of the controllers in the controller group;

[0110] In an embodiment, the ODX file group is parsed through the management background to obtain a first ODX file parsed from the ODX file group for matching the corresponding controller group, and a diagnostic instruction of the corresponding controller group is obtained based on the first ODX file.

[0111] Specifically, the step of parsing the ODX file group to obtain the diagnostic instructions of the controllers in the controller group includes:

[0112] Step S21, parsing the ODX file group to obtain a first ODX file in the ODX file group, and determining a controller in the detection vehicle that corresponds to the first ODX file and needs to be diagnosed;

[0113] Step S22, analyzing the controller to determine third diagnostic information in the controller;

[0114] Step S23, obtaining a first Json file in the Json file group corresponding to the third diagnostic information, and obtaining a diagnostic instruction for the vehicle to be diagnosed based on the first Json file.

[0115] Among them, Json (JavaScript Object Notation, a lightweight data exchange format) can be used to write diagnostic instructions.

[0116] In this embodiment, the ODX file group is parsed by the management background to obtain a first ODX file for matching the controller, and the controller that needs to be diagnosed in the vehicle to be detected is determined based on the first ODX file. Since there is preset diagnostic information in the controller, the controller is analyzed to obtain the preset diagnostic information in the controller that needs to be diagnosed, that is, the third diagnostic information. Based on the third diagnostic information, the diagnostic service information in the Json format corresponding to the third diagnostic information is matched from the Json file group, that is, the first Json file. The management background writes the first Json file into instructions to obtain the diagnostic instructions of the vehicle to be diagnosed.

[0117] Specifically, the step of parsing the ODX file group to obtain the first ODX file in the ODX file group, and determining the controller in the detection vehicle corresponding to the first ODX file and requiring diagnosis includes:

[0118] Step A1, analyzing the ODX file group to obtain the first ODX file in the ODX file group;

[0119] Step A2, analyzing the material number list based on the first ODX file to determine the first material number corresponding to the first ODX file;

[0120] Step A3, based on the first material number, determining the component to be diagnosed corresponding to the first material number in the vehicle to be diagnosed;

[0121] Step A4, performing subordinate query processing on the components to be diagnosed, and determining the controller to be diagnosed corresponding to the first ODX file in the detected vehicle.

[0122] Among them, the preset diagnostic information in the controller of different configurations of each vehicle model constitutes an ODX file.

[0123] Among them, the ODX file has a layer that can distinguish different material numbers. The management background can match the material number of the part to be diagnosed through the ODX file based on the material number composition in the basic information of the vehicle to be diagnosed.

[0124] Among them, ODX can at least describe vehicle diagnostic data, communication parameters, vehicle interface, controller configuration, function-oriented diagnosis and controller tasks, that is, ODX files can be vehicle diagnostic data files, communication parameter files, vehicle interface files, control coordination files, function-oriented diagnosis files and controller task files.

[0125] In this embodiment, the first ODX file in the ODX file group is obtained by analyzing the ODX file group. Since each ODX file includes multiple material numbers, the first material number corresponding to the first ODX file in the material number list is analyzed through the first ODX file. Since each material number corresponds to a vehicle component, the component of the vehicle to be diagnosed can be determined through the first material number, that is, the component to be diagnosed corresponding to the first material number in the vehicle to be diagnosed is determined. Since different components in the vehicle are controlled by different controllers, the controller that controls the component to be diagnosed can be queried through the component to be diagnosed.

[0126] Among them, one controller can control multiple components or one component.

[0127] A component may be a part, such as a sheet metal part;

[0128] A component can also be a structure composed of parts, such as a camera, cylinder, etc.

[0129] In this embodiment, by parsing the ODX file group, the parts to be diagnosed corresponding to the first material number in the vehicle to be diagnosed are determined, and the controller to be diagnosed is queried through the parts to be diagnosed. The controller to be diagnosed is analyzed to obtain the third diagnostic information in the controller, and based on the third diagnostic information, the first Json file in the Json format corresponding to the third diagnostic information is matched in the Json file group, and the first Json file is written into instructions to obtain the diagnostic instructions of the vehicle to be diagnosed.

[0130] Step S30: based on the diagnostic instruction, diagnose the controller corresponding to the diagnostic instruction to obtain a diagnostic result.

[0131] In this embodiment, a diagnostic instruction is sent to a corresponding controller. Based on the diagnostic instruction, the controller turns on a self-check function, performs a self-check, obtains a diagnostic result, and sends the diagnostic result to a terminal so that the terminal can prompt the diagnostic result.

[0132] Among them, multiple controllers can be tested at the same time, or one controller can be tested one by one.

[0133] The terminal may prompt the diagnosis results of multiple controllers at one time, or may prompt the diagnosis result of only one controller at a time.

[0134] The diagnosis of the controller may be to test the whole vehicle controller or to test a specific controller.

[0135] Specifically, the step of diagnosing the controller corresponding to the diagnostic instruction based on the diagnostic instruction to obtain a diagnostic result includes:

[0136] Step S31, based on the diagnostic instruction, obtaining preset diagnostic information in the controller corresponding to the diagnostic instruction;

[0137] Step S32, performing analysis based on the preset diagnostic information, and extracting a second ODX file corresponding to the controller from the ODX information table;

[0138] Step S33, parsing the second ODX file to obtain the configuration information and fault code of the vehicle to be diagnosed;

[0139] The diagnostic result includes at least one of configuration information and a fault code.

[0140] In this embodiment, a diagnostic instruction is sent to the corresponding controller, preset diagnostic information in the controller is obtained, the preset diagnostic information is analyzed, a second ODX file corresponding to the controller is matched in the ODX information table, and a diagnostic result is obtained by parsing the second ODX file.

[0141] In this embodiment, the identification code of the vehicle to be diagnosed is obtained through the terminal, and it is determined whether the vehicle to be diagnosed can be diagnosed through identification code analysis. If it can be diagnosed, the ODX file group of the vehicle to be diagnosed is obtained, and the ODX file group is parsed to obtain the diagnostic instructions of the controller in the controller group. Based on the diagnostic instructions, the controller in the controller group corresponding to the diagnostic instructions is matched, and the diagnostic instructions are sent to the controller for the controller to perform self-test to obtain the diagnostic result of the diagnosed vehicle.

[0142] In this implementation, by pre-building the ODX file tool, there is no need to go to the location of the vehicle to be diagnosed when diagnosing the vehicle. Only the identification code needs to be entered on the terminal to access the management background. Based on the management background and the ODX file tool, the vehicle to be diagnosed can be remotely diagnosed, reducing the operation of the diagnostic equipment.

[0143] The present application provides a vehicle fault diagnosis method, apparatus, equipment and storage medium. Compared with the prior art which requires adapting the vehicle and the diagnostic equipment, and selecting the information of the vehicle to be diagnosed and the diagnostic file, etc., resulting in complicated operations during the vehicle fault diagnosis process, in the present application, an identification code of the vehicle to be diagnosed is obtained, the identification code is analyzed to obtain a material number list of the vehicle to be diagnosed, and an ODX file group corresponding to the material number list is determined; wherein, the vehicle to be diagnosed includes a controller group for controlling the vehicle to be diagnosed and a controller in the controller group; the ODX file group is parsed to obtain diagnostic instructions for the controller in the controller group; based on the diagnostic instructions, the controller corresponding to the diagnostic instructions is diagnosed to obtain a diagnostic result. In the present application, it is only necessary to obtain an ODX file group corresponding to the material number list of the vehicle to be diagnosed based on the identification code of the vehicle to be diagnosed, obtain a diagnostic instruction based on the ODX file group, diagnose the vehicle to be diagnosed based on the diagnostic instruction, and obtain a diagnostic result of the vehicle to be diagnosed. That is, in the present application, it is only necessary to obtain the vehicle identification code and the detection request to diagnose the vehicle, and no other diagnostic equipment is required, thereby reducing the use of diagnostic equipment and reducing the complexity of operations during vehicle fault diagnosis.

[0144] Further, based on the above embodiment of the present application, another embodiment of the present application is provided. In this embodiment, before the step of obtaining the identification code of the vehicle to be diagnosed, the method includes:

[0145] Step B10, parsing the preset diagnostic information in each of the controller groups to obtain a diagnostic service information table in a tabular format, wherein the preset diagnostic information is preset in the controller;

[0146] Step B20, converting the diagnostic service information table into an ODX format to obtain an ODX information table in an ODX format;

[0147] Step B30, converting the ODX information table into a Json format to obtain a Json file group for generating the diagnostic instruction;

[0148] In this embodiment, the preset diagnostic information in each controller group is collected through the ODX file tool, and each collected preset diagnostic information is parsed and integrated to obtain a diagnostic service information table in a tabular format. The diagnostic service information table in the tabular format is converted and processed through the ODX file tool to obtain an ODX information table in ODX format, and the diagnostic service information table in the tabular format is retained, and the ODX information table is then converted into a Json file group in Json format, and the ODX information table in ODX format is saved.

[0149] Specifically, the preset diagnostic information is a table format file;

[0150] The step of parsing the preset diagnostic information to obtain a diagnostic service information table in a tabular format includes:

[0151] Step B11, parsing and screening the preset diagnostic information, removing repeated first diagnostic information in the preset diagnostic information, and obtaining second diagnostic information without repeated data;

[0152] Step B12: Integrate and classify the second diagnostic information to obtain a diagnostic service information table in a tabular format.

[0153] In this embodiment, the preset diagnostic information is parsed and filtered, and repeated first diagnostic information in the preset information is removed by filtering, and each piece of first diagnostic information is retained to obtain second diagnostic information, which is integrated and classified to obtain a diagnostic service information table in a tabular format.

[0154] The diagnostic service information table may be modified, that is, the second diagnostic information may be added to the diagnostic service information table, or the second diagnostic information may be deleted.

[0155] In this embodiment, each preset diagnostic information collected is screened by the ODX file tool, and duplicate and redundant preset diagnostic information is removed to obtain the second diagnostic information. The second diagnostic information is integrated and classified to obtain a diagnostic service information table in a tabular format. The diagnostic service information table in a tabular format is converted into a Json file group in a Json format. In this embodiment, the pre-built ODX file tool can be used to quickly and automatically match the diagnostic file from the ODX file tool when diagnosing the vehicle to be diagnosed.

[0156] Further, based on the above embodiments in the present application, another embodiment of the present application is provided. In this embodiment,

[0157] The diagnostic operation steps for the vehicle to be diagnosed include:

[0158] Obtaining the identification code of the vehicle to be diagnosed, and selecting request information, and obtaining different diagnostic operations based on different request information;

[0159] If the requested information is basic information of the vehicle to be diagnosed, the vehicle information of the vehicle to be diagnosed is obtained based on the identification code;

[0160] If the requested information is a list of diagnostic functions, the vehicle to be diagnosed is diagnosed;

[0161] If the requested information is to read the fault code, the previous diagnosis result of the vehicle to be diagnosed is read;

[0162] In this embodiment, it should be noted that the basis for diagnosing the vehicle to be queried is the identification code of the vehicle to be diagnosed, that is, the vehicle to be diagnosed can be diagnosed with the identification code of the vehicle to be diagnosed, and there is no need to go to the location of the vehicle to be diagnosed. In this embodiment, remote operation can be performed only through the identification code of the vehicle to be diagnosed, saving time and equipment costs.

[0163] Reference Figure 3 , Figure 3 It is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present application.

[0164] like Figure 3 As shown, the vehicle fault diagnosis device may include: a processor 1001, such as a CPU, a memory 1005, and a communication bus 1002. The communication bus 1002 is used to realize the connection and communication between the processor 1001 and the memory 1005. The memory 1005 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0165] Optionally, the vehicle fault diagnosis device may also include a rectangular user interface, a network interface, a camera, an RF (Radio Frequency) circuit, a sensor, an audio circuit, a WiFi module, etc. The rectangular user interface may include a display screen (Display), an input submodule such as a keyboard (Keyboard), and the optional rectangular user interface may also include a standard wired interface and a wireless interface. The network interface may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).

[0166] Those skilled in the art will understand that Figure 3 The vehicle fault diagnosis device structure shown in the figure does not constitute a limitation on the vehicle fault diagnosis device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0167] like Figure 3 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module and a vehicle fault diagnosis program. The operating system is a program that manages and controls the hardware and software resources of the vehicle fault diagnosis device, and supports the operation of the vehicle fault diagnosis program and other software and / or programs. The network communication module is used to realize the communication between the components inside the memory 1005, and the communication with other hardware and software in the vehicle fault diagnosis system.

[0168] exist Figure 3In the vehicle fault diagnosis device shown, the processor 1001 is used to execute the vehicle fault diagnosis program stored in the memory 1005 to implement the steps of any of the above-mentioned vehicle fault diagnosis methods.

[0169] The specific implementation of the vehicle fault diagnosis device of the present application is basically the same as the various embodiments of the above-mentioned vehicle fault diagnosis method, and will not be repeated here.

[0170] The present application also provides a vehicle fault diagnosis device, the vehicle fault diagnosis device comprising:

[0171] An analysis module, used for obtaining an identification code of a vehicle to be diagnosed, analyzing the identification code to obtain a material number list of the vehicle to be diagnosed, and determining an ODX file group corresponding to the material number list;

[0172] Wherein, the vehicle to be diagnosed includes a controller group for controlling the vehicle to be diagnosed and a controller in the controller group;

[0173] A parsing module, used for parsing the ODX file group to obtain diagnostic instructions of controllers in the controller group;

[0174] The diagnosis module is used to diagnose the controller corresponding to the diagnosis instruction based on the diagnosis instruction to obtain a diagnosis result.

[0175] Optionally, the vehicle fault diagnosis device further includes:

[0176] A first parsing submodule, configured to parse the preset diagnostic information in each of the controller groups to obtain a diagnostic service information table in a tabular format, wherein the preset diagnostic information is preset in the controller;

[0177] A first format conversion module, used for converting the diagnostic service information table into an ODX format to obtain an ODX information table in an ODX format;

[0178] The second format conversion module is used to convert the ODX information table into a Json format to obtain a Json file group used to generate the diagnostic instruction.

[0179] Optionally, the preset diagnostic information is a table format file;

[0180] The first parsing submodule includes:

[0181] A screening module, used for parsing and screening the preset diagnostic information, removing repeated first diagnostic information in the preset diagnostic information, and obtaining second diagnostic information without repeated data;

[0182] The integration module is used to integrate and classify the second diagnostic information to obtain a diagnostic service information table in a tabular format.

[0183] Optionally, the parsing module includes:

[0184] A parsing submodule, configured to parse the ODX file group to obtain a first ODX file in the ODX file group, and determine a controller in the detection vehicle that corresponds to the first ODX file and needs to be diagnosed;

[0185] a first analyzing unit, configured to analyze the controller and determine third diagnostic information in the controller;

[0186] An acquisition unit is used to acquire a first Json file in the Json file group corresponding to the third diagnostic information, and obtain a diagnostic instruction of the vehicle to be diagnosed based on the first Json file.

[0187] Optionally, the analysis module includes:

[0188] A second analysis unit is used to obtain an identification code of the vehicle to be diagnosed, analyze the identification code, and determine the model and production batch of the vehicle to be diagnosed;

[0189] A matching module, used for obtaining a list of material numbers of the vehicle to be diagnosed based on the production batch of the model;

[0190] The material number list includes the second material number of each component constituting the vehicle to be diagnosed;

[0191] A judging module, used for judging whether there is a second ODX file corresponding to the second material number in the ODX information table;

[0192] a determination module, configured to determine the second ODX file corresponding to the second material number if a second ODX file corresponding to the material number exists in the ODX information table;

[0193] The integration unit is used to integrate the second ODX file to obtain an ODX file group corresponding to the material number list.

[0194] Optionally, the diagnosis module includes:

[0195] A matching unit, configured to obtain, based on the diagnostic instruction, preset diagnostic information in a controller corresponding to the diagnostic instruction;

[0196] A third analyzing unit, configured to perform analysis based on the preset diagnostic information and extract a second ODX file corresponding to the controller from the ODX information table;

[0197] A parsing unit, used for parsing the second ODX file to obtain the configuration information and fault code of the vehicle to be diagnosed;

[0198] The diagnostic result includes at least one of configuration information and a fault code.

[0199] The specific implementation of the vehicle fault diagnosis device of the present application is basically the same as the various embodiments of the above-mentioned vehicle fault diagnosis method, and will not be repeated here.

[0200] An embodiment of the present application provides a storage medium, and the storage medium stores one or more programs, and the one or more programs can also be executed by one or more processors to implement the steps of any of the above-mentioned vehicle fault diagnosis methods.

[0201] The specific implementation of the storage medium of the present application is basically the same as the various embodiments of the above-mentioned vehicle fault diagnosis method, and will not be repeated here.

[0202] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0203] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0204] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0205] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A vehicle fault diagnosis method, characterized in that: The vehicle fault diagnosis method comprises: Parsing the preset diagnostic information in each controller group to obtain a diagnostic service information table in a tabular format, wherein the preset diagnostic information is preset in the controller; Convert the diagnostic service information table into an ODX format to obtain an ODX information table in an ODX format; Convert the ODX information table into Json format to obtain a Json file group for generating diagnostic instructions; Obtaining an identification code of the vehicle to be diagnosed, analyzing the identification code to obtain a material number list of the vehicle to be diagnosed, and determining an ODX file group corresponding to the material number list; Wherein, the vehicle to be diagnosed includes a controller group for controlling the vehicle to be diagnosed and a controller in the controller group; Parsing the ODX file group to obtain diagnostic instructions of controllers in the controller group; Based on the diagnosis instruction, a controller corresponding to the diagnosis instruction is diagnosed to obtain a diagnosis result.

2. The vehicle fault diagnosis method according to claim 1, characterized in that: The preset diagnostic information is a table format file; The step of parsing the preset diagnostic information to obtain a diagnostic service information table in a tabular format includes: Parsing and screening the preset diagnostic information, removing repeated first diagnostic information in the preset diagnostic information, and obtaining second diagnostic information without repeated data; The second diagnostic information is integrated and classified to obtain a diagnostic service information table in a tabular format.

3. The vehicle fault diagnosis method according to claim 1, characterized in that: The step of parsing the ODX file group to obtain the diagnostic instructions of the controllers in the controller group includes: Parsing the ODX file group to obtain a first ODX file in the ODX file group, and determining a controller that needs to be diagnosed and corresponds to the first ODX file in the vehicle to be diagnosed; analyzing the controller to determine third diagnostic information in the controller; A first Json file in the Json file group corresponding to the third diagnostic information is obtained, and a diagnostic instruction of the vehicle to be diagnosed is obtained based on the first Json file.

4. The vehicle fault diagnosis method according to claim 3, characterized in that: The step of parsing the ODX file group to obtain the first ODX file in the ODX file group, and determining the controller that needs to be diagnosed and corresponds to the first ODX file in the vehicle to be diagnosed, comprises: Analyze the ODX file group to obtain the first ODX file in the ODX file group; Based on the first ODX file, analyzing the material number list to determine a first material number corresponding to the first ODX file; Based on the first material number, determining a component to be diagnosed in the vehicle to be diagnosed that corresponds to the first material number; A subordinate query process is performed on the components to be diagnosed to determine a controller that needs to be diagnosed and corresponds to the first ODX file in the vehicle to be diagnosed.

5. The vehicle fault diagnosis method according to claim 1, characterized in that: The steps of obtaining the identification code of the vehicle to be diagnosed, analyzing the identification code, obtaining the material number list of the vehicle to be diagnosed, and determining the ODX file group corresponding to the material number list include: Obtaining an identification code of the vehicle to be diagnosed, analyzing the identification code, and determining the model and production batch of the vehicle to be diagnosed; Based on the production batch of the model, a list of material numbers of the vehicle to be diagnosed is obtained; The material number list includes the second material number of each component constituting the vehicle to be diagnosed; Determine whether there is a second ODX file corresponding to the second material number in the ODX information table; If a second ODX file corresponding to the material number exists in the ODX information table, determining a second ODX file corresponding to the second material number; The second ODX file is integrated to obtain an ODX file group corresponding to the material number list.

6. The vehicle fault diagnosis method according to claim 1, characterized in that: The step of diagnosing the controller corresponding to the diagnostic instruction based on the diagnostic instruction to obtain a diagnostic result includes: Based on the diagnostic instruction, obtaining preset diagnostic information in a controller corresponding to the diagnostic instruction; Analyzing based on the preset diagnostic information, extracting a second ODX file corresponding to the controller from the ODX information table; Parsing the second ODX file to obtain configuration information and fault codes of the vehicle to be diagnosed; The diagnostic result includes at least one of configuration information and a fault code.

7. A vehicle fault diagnosis device, characterized in that: The vehicle fault diagnosis device comprises: A conversion module, used for parsing the preset diagnostic information in each controller group to obtain a diagnostic service information table in a tabular format, wherein the preset diagnostic information is preset in the controller, converting the diagnostic service information table into an ODX format to obtain an ODX information table in an ODX format, converting the ODX information table into a Json format to obtain a Json file group for generating diagnostic instructions; An analysis module, used for obtaining an identification code of a vehicle to be diagnosed, analyzing the identification code to obtain a material number list of the vehicle to be diagnosed, and determining an ODX file group corresponding to the material number list; Wherein, the vehicle to be diagnosed includes a controller group for controlling the vehicle to be diagnosed and a controller in the controller group; A parsing module, used for parsing the ODX file group to obtain diagnostic instructions of controllers in the controller group; The diagnostic information is used to diagnose the controller corresponding to the diagnostic instruction based on the diagnostic instruction to obtain a diagnostic result.

8. A vehicle fault diagnosis device, characterized in that: The vehicle fault diagnosis device comprises: a memory, a processor, and a program stored in the memory for implementing the vehicle fault diagnosis method. The memory is used to store a program for implementing a vehicle fault diagnosis method; The processor is used to execute a program for implementing the vehicle fault diagnosis method to implement the steps of the vehicle fault diagnosis method as claimed in any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium stores a program for implementing a vehicle fault diagnosis method, and the program for implementing a vehicle fault diagnosis method is executed by a processor to implement the steps of the vehicle fault diagnosis method as claimed in any one of claims 1 to 6.

Images