Vehicle fault diagnosis method, device and equipment and readable storage medium

Abstract

The application relates to the technical field of vehicle diagnosis, in particular to a vehicle fault diagnosis method, device and equipment and a readable storage medium. The vehicle fault diagnosis method comprises the following steps: acquiring vehicle model information of a current vehicle to be diagnosed; loading a pre-recorded diagnosis process file; the diagnosis process file records at least one diagnosis step; each diagnosis step comprises a function identifier and an ECU identifier; executing the loaded diagnosis process file; for each diagnosis step, based on the vehicle model information, the function identifier and the ECU identifier, corresponding diagnosis parameters are determined; according to the determined diagnosis parameters, corresponding diagnosis instructions are sent, and diagnosis result data returned by the vehicle to be diagnosed is acquired. In this way, the same diagnosis process file can be used when diagnosing different vehicle models; for different vehicle models, only corresponding diagnosis parameters need to be acquired, different diagnosis function processes need not be developed for different vehicle models, and therefore a large amount of development resources and later maintenance costs can be saved.

Description

Technical Field

[0001] This application relates to the field of vehicle diagnostic technology, specifically to a vehicle fault diagnosis method, apparatus, device, and readable storage medium. Background Technology

[0002] Currently, automobiles are electronic, and the application of automotive electronic technology will make automobiles more intelligent. Consequently, the complexity of vehicle maintenance has also increased significantly. Therefore, when repairing a vehicle, it is necessary to use diagnostic equipment to locate the fault, determine the technical condition of the vehicle, and identify the faulty part and the cause of the fault.

[0003] Diagnosing a car involves a series of steps, such as reading fault codes, acquiring data streams, and clearing fault codes. While the diagnostic process is similar across various car models, the diagnostic protocols differ, resulting in separate procedures for each model. Therefore, each time a vehicle needs diagnostics, technicians must individually set or write the corresponding diagnostic procedure and run it to complete the diagnosis. Such procedures are not universally applicable to other models, leading to significant manpower and time costs associated with current vehicle diagnostic methods. Summary of the Invention

[0004] The main technical problem addressed in this application is that existing vehicle diagnostic methods require significant time and manpower costs.

[0005] This application provides a vehicle fault diagnosis method, including:

[0006] Obtain the vehicle model information of the vehicle currently being diagnosed;

[0007] Load a pre-recorded diagnostic process file, which records at least one diagnostic step, each of which includes a function identifier and an ECU identifier;

[0008] The diagnostic process file is executed, and for each diagnostic step, the corresponding diagnostic parameters are determined based on the vehicle model information, function identifier, and ECU identifier; the corresponding diagnostic command is sent according to the determined diagnostic parameters, and the diagnostic result data returned by the vehicle to be diagnosed is obtained.

[0009] In one embodiment, sending a corresponding diagnostic command based on the determined diagnostic parameters and obtaining the diagnostic result data returned by the vehicle to be diagnosed includes:

[0010] Based on the vehicle model information, function identifier, and ECU identifier, the corresponding communication parameters are searched in the preset protocol library;

[0011] Generate communication instructions based on the communication parameters;

[0012] A request to establish a communication connection is initiated to the target ECU according to the communication instructions;

[0013] Obtain the communication connection establishment result data returned by the target ECU;

[0014] The diagnostic parameters include the communication parameters, the diagnostic instructions include the communication instructions, and the diagnostic result data includes the communication connection establishment result data.

[0015] In one embodiment, the step of determining corresponding diagnostic parameters based on the vehicle model information, function identifier, and ECU identifier; sending corresponding diagnostic commands according to the determined diagnostic parameters; and obtaining diagnostic result data returned by the vehicle to be diagnosed includes:

[0016] Based on the vehicle model information, function identifier, and ECU identifier, the corresponding reading parameters and the first parsing algorithm are searched in the preset protocol library;

[0017] Generate a read instruction based on the read parameters;

[0018] Send the read command to the target ECU;

[0019] Obtain the diagnostic result data returned by the target ECU;

[0020] The diagnostic result data is analyzed based on the first parsing algorithm;

[0021] The diagnostic parameters include the reading parameters and the first parsing algorithm, and the diagnostic instructions include the reading instructions.

[0022] In one embodiment, the step of determining corresponding diagnostic parameters based on the vehicle model information, function identifier, and ECU identifier; sending corresponding diagnostic commands according to the determined diagnostic parameters; and obtaining diagnostic result data returned by the vehicle to be diagnosed includes:

[0023] Based on the vehicle model information, function identifier, and ECU identifier, the corresponding clearing parameters and clearing result determination algorithm are searched in the preset protocol library;

[0024] Based on the clearing parameters and the clearing result determination algorithm, clearing instructions and clearing result determination instructions are generated respectively;

[0025] Send the clear command to clear the fault codes of the vehicle to be diagnosed;

[0026] Send the clearing result determination instruction to obtain the clearing result of the fault code;

[0027] The diagnostic parameters include the clearing parameters and the clearing result determination parameters; the diagnostic instructions include the clearing instructions and the clearing result determination instructions; and the diagnostic result data includes the clearing result of the fault code.

[0028] In one embodiment, after obtaining the diagnostic result data returned by the vehicle to be diagnosed, the method further includes: recording the obtained diagnostic result data in a diagnostic log.

[0029] In one embodiment, a protocol library is pre-configured in the diagnostic device, the protocol library including diagnostic protocols for at least one vehicle model;

[0030] Match the corresponding diagnostic protocol from the protocol library based on the vehicle model information;

[0031] The corresponding diagnostic parameters are determined from the diagnostic protocol based on the function identifier and the ECU identifier.

[0032] This application also provides a vehicle fault diagnosis device, including:

[0033] The acquisition module is used to obtain the vehicle model information of the vehicle to be diagnosed.

[0034] A loading module is used to load a pre-recorded diagnostic process file, which records at least one diagnostic step, each of which includes a function identifier and an ECU identifier.

[0035] The execution module is used to execute the diagnostic process file, and for each diagnostic step, determine the corresponding diagnostic parameters based on the vehicle model information, function identifier, and ECU identifier; send the corresponding diagnostic command according to the determined diagnostic parameters, and obtain the diagnostic result data returned by the vehicle to be diagnosed.

[0036] This application also provides a vehicle fault diagnosis device, including:

[0037] Memory, used to store programs;

[0038] A processor is configured to implement the vehicle fault diagnosis method described above by executing a program stored in the memory.

[0039] A computer-readable storage medium storing a program that can be executed by a processor to implement the vehicle fault diagnosis method as described above.

[0040] According to the vehicle fault diagnosis method of the above embodiment, the vehicle model information of the vehicle to be diagnosed is first obtained, then a pre-recorded diagnostic process file is loaded and executed. For each diagnostic step, the corresponding diagnostic parameters are determined based on the vehicle model information, function identifier, and ECU identifier. The corresponding diagnostic command is sent according to the determined diagnostic parameters, and the diagnostic result data returned by the vehicle to be diagnosed is obtained. In this way, the same diagnostic process file can be used to diagnose different vehicle models. For different vehicle models, only the corresponding diagnostic parameters need to be obtained, eliminating the need to develop different diagnostic function processes for different vehicle models. This saves a significant amount of development resources and subsequent maintenance costs. Attached Figure Description

[0041] Figure 1 This is an overall flowchart of the vehicle fault diagnosis method according to an embodiment of this application;

[0042] Figure 2 A flowchart illustrating the communication connection establishment method according to an embodiment of this application;

[0043] Figure 3 This is a flowchart of a method for reading diagnostic result data according to an embodiment of this application;

[0044] Figure 4 This is a flowchart of a fault code clearing method according to an embodiment of this application;

[0045] Figure 5 This is a schematic diagram of the structure of a vehicle fault diagnosis device according to an embodiment of this application;

[0046] Figure 6 This is a schematic diagram of the structure of a vehicle fault diagnosis device according to another embodiment of this application. Detailed Implementation

[0047] The present application will now be described in further detail with reference to the accompanying drawings and specific embodiments. Similar elements in different embodiments are referred to by related similar element reference numerals. In the following embodiments, many details are described to facilitate a better understanding of the present application. However, those skilled in the art will readily recognize that some features may be omitted in different situations, or may be replaced by other elements, materials, or methods. In some cases, certain operations related to the present application are not shown or described in the specification. This is to avoid obscuring the core parts of the present application with excessive description. For those skilled in the art, detailed description of these related operations is not necessary; they can fully understand the related operations based on the description in the specification and general technical knowledge in the art.

[0048] Furthermore, the features, operations, or characteristics described in the specification can be combined in any suitable manner to form various embodiments. At the same time, the steps or actions in the method description can be rearranged or adjusted in a manner obvious to those skilled in the art. Therefore, the various orders in the specification and drawings are only for the clear description of a particular embodiment and do not imply a necessary order, unless otherwise stated that a particular order must be followed.

[0049] The serial numbers assigned to components in this article, such as "first" and "second", are used only to distinguish the objects being described and have no sequential or technical meaning.

[0050] This application provides a vehicle fault diagnosis method. First, the vehicle model information of the vehicle to be diagnosed is obtained. Then, a pre-recorded diagnostic process file is loaded and executed. The diagnostic process file records at least one diagnostic step, each of which includes a function identifier and an ECU identifier. For each diagnostic step, based on the vehicle model information, function identifier, and ECU identifier, corresponding diagnostic parameters are determined. Based on the determined diagnostic parameters, a corresponding diagnostic command is sent, and diagnostic result data returned by the vehicle to be diagnosed is obtained.

[0051] In vehicle diagnostics, different vehicle models use different diagnostic protocols, thus requiring different diagnostic parameters to perform specific diagnostic functions. This application, when executing specific diagnostic steps in the diagnostic process file, obtains corresponding diagnostic parameters based on vehicle model information, function identifiers, and ECU identifiers. Then, it generates corresponding diagnostic instructions based on these parameters to diagnose the vehicle. Therefore, the same diagnostic process file can be used to diagnose different vehicle models. For subsequent additions to different vehicle models, only the diagnostic parameters need to be modified or added, eliminating the need to develop a new diagnostic process file. This saves significant development resources and subsequent maintenance costs. Furthermore, for those skilled in the art, all function identifiers and ECU identifiers corresponding to a specific vehicle model are unique and have clear physical meanings.

[0052] The diagnostic process document of this application includes multiple diagnostic steps, which are executed sequentially to complete the diagnosis of the vehicle. For example, a diagnostic process document includes: first, diagnostic step A is used to diagnose the vehicle's engine; then, diagnostic step B is used to diagnose the vehicle's audio system; and finally, diagnostic step C is used to diagnose the vehicle's air conditioning system.

[0053] To further enhance the flexibility of the diagnostic method, this application allows several vehicle models that can use a single diagnostic workflow file to share this file. This means the order in which different vehicle components or systems are diagnosed is the same. However, since the data communication protocols of different vehicle components or systems may differ, when diagnosing a particular component or system, the corresponding diagnostic parameters for that vehicle model can be retrieved from a pre-defined protocol library. This allows for the use of a single diagnostic workflow file, with the corresponding diagnostic parameters called at each diagnostic step to complete the diagnosis. This saves on editing the diagnostic workflow file, reducing labor and time costs, and improving vehicle diagnostic efficiency.

[0054] Example 1:

[0055] Please refer to Figure 1 This embodiment provides a vehicle fault diagnosis method, applied to diagnostic equipment, the method comprising:

[0056] 101: Obtain the vehicle model information of the vehicle to be diagnosed. In this embodiment, the vehicle model information is determined based on the vehicle's VIN code. Specifically, after establishing a communication connection with the vehicle, the VIN code of the vehicle to be diagnosed is obtained. The VIN code is a unified road vehicle identification system (i.e., a car's ID card) established worldwide to simplify vehicle identification information retrieval and improve the accuracy and efficiency of vehicle fault information feedback. The Vehicle Identification Number (VIN code) consists of 17 characters, hence the common name "17-digit code".

[0057] 102: Load the pre-recorded diagnostic process file. The diagnostic process file records at least one diagnostic step, and each diagnostic step includes a function identifier and an ECU identifier. Generally, the diagnostic process file includes multiple diagnostic steps, each of which diagnoses a different system or component of the vehicle. Different systems or components correspond to different ECU identifiers, or different diagnostic functions correspond to different function identifiers. For example, entering the ECU function identifier is 02. Each function identifier and ECU identifier is unique.

[0058] 103: Execute the diagnostic process document. For each diagnostic step, determine the corresponding diagnostic parameters based on vehicle model information, function identifiers, and ECU identifiers. Send the corresponding diagnostic instructions according to the determined diagnostic parameters and obtain the diagnostic result data returned by the vehicle to be diagnosed.

[0059] When executing the diagnostic process document, the vehicle is diagnosed sequentially according to each diagnostic step in the document. Since different vehicle models, different ECUs are used to diagnose different systems or components of different vehicles, and different diagnostic functions correspond to different function identifiers, the corresponding diagnostic parameters are also different. This application first determines the corresponding diagnostic parameters based on the vehicle model information, function identifiers, and ECU identifiers. Then, it sends the corresponding diagnostic commands according to the determined diagnostic parameters, diagnoses the vehicle using the diagnostic commands, and returns the diagnostic result data.

[0060] Using the diagnostic method of this application, the same diagnostic process file can be used to diagnose different vehicle models. For different vehicle models, only the corresponding diagnostic parameters need to be obtained. There is no need to develop different diagnostic function processes for different vehicle models. When adding new vehicle models, only the corresponding diagnostic parameters need to be modified or added. There is no need to redevelop a new diagnostic process file. This can save a lot of development resources and later maintenance costs.

[0061] Example 2:

[0062] like Figure 2 In this embodiment, based on vehicle model information, function identifiers, and ECU identifiers, corresponding diagnostic parameters are determined; according to the determined diagnostic parameters, corresponding diagnostic commands are sent, and the diagnostic result data returned by the vehicle to be diagnosed is obtained, specifically including:

[0063] Step 201: Search for the corresponding communication parameters in the preset protocol library based on the vehicle model information, function identifier, and ECU identifier;

[0064] Step 202: Generate communication commands based on communication parameters;

[0065] Step 203: Initiate a communication connection establishment request to the target ECU according to the communication command;

[0066] Step 204: Obtain the communication connection establishment result data returned by the target ECU.

[0067] In this embodiment, the diagnostic parameters include communication parameters, the diagnostic instructions include communication instructions, and the diagnostic result data includes communication connection establishment result data, such as successful communication connection establishment.

[0068] For example, the diagnostic steps for an engine ECU first involve searching the protocol library of the diagnostic equipment for the communication parameters of the engine ECU for the current vehicle model to generate a communication command. For example, the communication parameters are: communication baud rate 500K, communication pins 6 and 14, and the communication ID of the engine ECU (the request ID is used to send data to the engine ECU, and the reply ID is used to receive data from the engine ECU). Then, the diagnostic equipment generates a communication command based on the communication parameters and runs the command to establish a communication connection with the engine ECU.

[0069] Generally, before diagnosing a vehicle system (such as the engine system), diagnostic equipment first needs to establish a communication connection with the system's ECU. According to the communication establishment method provided in this embodiment, when diagnosing a system of any vehicle model, the corresponding communication parameters can be first searched in a preset protocol library based on the vehicle model information, function identifier, and ECU identifier. Then, communication commands are generated to establish the communication connection. This eliminates the need to establish a separate communication connection method for different vehicle models, functions, and ECUs. The diagnostic equipment can search for the corresponding communication parameters according to different needs, saving time and manpower costs and improving diagnostic efficiency.

[0070] Example 3:

[0071] like Figure 3 In this embodiment, based on vehicle model information, function identifiers, and ECU identifiers, corresponding diagnostic parameters are determined; according to the determined diagnostic parameters, corresponding diagnostic commands are sent, and the diagnostic result data returned by the vehicle to be diagnosed is obtained, specifically including:

[0072] Step 301: Based on the vehicle model information, function identifier, and ECU identifier, search for the corresponding reading parameters and the first parsing algorithm in the preset protocol library;

[0073] Step 302: Generate a reading command based on the reading parameters; the reading command is used to read the parameter information of each sensor or component of the target ECU;

[0074] Step 303: Send a read command to the target ECU;

[0075] Step 304: Obtain the diagnostic result data returned by the target ECU; in this embodiment, the diagnostic result data includes fault codes or other data streams.

[0076] Step 305: Parse the diagnostic result data based on the first parsing algorithm. Since the diagnostic result data returned by the ECU is primarily in binary format or encrypted or compressed using the first parsing algorithm, the corresponding first parsing algorithm is used to parse the returned diagnostic result data to obtain the diagnostic result. In this embodiment, the diagnostic parameters include read parameters and the first parsing algorithm, and the diagnostic instructions include read instructions.

[0077] For example, when a diagnostic operation is required to read fault codes from the engine ECU, the system retrieves the reading parameters and the first parsing algorithm corresponding to the current vehicle model's engine ECU from the protocol library. A reading command is generated based on the reading parameters and sent to the engine ECU. The system then receives the fault code information returned by the engine ECU based on the reading command. Finally, the first parsing algorithm is used to parse the fault code to obtain the specific fault number and fault content, which is then added to the diagnostic log. The first parsing algorithm includes the starting byte position, the number of bytes representing a fault code, and the fault content corresponding to each fault code number.

[0078] For example, when it's necessary to read a specific data stream from the engine ECU, the corresponding data stream to be read is determined based on the data stream identifier recorded in the diagnostic steps of the diagnostic process document. Then, the reading parameters and the first parsing algorithm corresponding to reading that data stream from the engine ECU for that vehicle model are searched in the protocol library. A reading command is generated based on the reading parameters and sent to the engine ECU. The engine ECU's response data is obtained, and the first parsing algorithm is used to parse the response data to obtain the value of the data stream. Then, the value of the data stream is recorded in the diagnostic log. Taking reading engine speed as an example, since the engine speed value returned by the engine ECU is encrypted using an agreed protocol, the corresponding first parsing algorithm is needed to parse the returned diagnostic result data to obtain the name of the data stream item and the corresponding parameter value. For example, after parsing, the DID of the engine speed is obtained as 0x0801, which means the engine speed is 801. Finally, the DID: 0x0801 is output, which means that the collected engine speed is 801.

[0079] According to the diagnostic method provided in this embodiment, when diagnosing vehicle faults, technicians do not need to write corresponding diagnostic parameters (i.e., configure diagnostic strategies) for different vehicle models, different function identifiers, or ECU identifiers. They only need to find the corresponding reading parameters in the protocol library based on the current vehicle model information, the function identifier of the function to be tested, and the ECU identifier, and then generate a reading command based on the reading parameters to read the diagnostic result data from the target ECU. This saves time and manpower costs and improves diagnostic efficiency.

[0080] In one embodiment, after reading the diagnostic result data, for example after performing the corresponding repairs based on the fault codes and confirming that the fault has been resolved, it is also necessary to clear the vehicle's fault codes. Specifically, such as... Figure 4 In one embodiment, based on the vehicle model information, function identifier, and ECU identifier, corresponding diagnostic parameters are determined; sending corresponding diagnostic commands according to the determined diagnostic parameters and obtaining diagnostic result data returned by the vehicle to be diagnosed further includes:

[0081] Step 401: Based on the vehicle model information, function identifier, and ECU identifier, search for the corresponding clearing parameters and clearing result determination algorithm in the preset protocol library;

[0082] Step 402: Generate a clearing instruction and a clearing result determination instruction based on the clearing parameters and the clearing result determination algorithm, respectively;

[0083] Step 403: Send a clear command to clear the fault codes of the vehicle to be diagnosed;

[0084] Step 404: Send a clearing result determination command to obtain the clearing result of the fault code;

[0085] In this embodiment, the diagnostic parameters include clearing parameters and clearing result determination parameters, the diagnostic instructions include clearing instructions and clearing result determination instructions, and the diagnostic result data includes the clearing result of the fault code.

[0086] According to the diagnostic method of this embodiment, the corresponding clearing parameters and clearing result determination algorithm can be found based on vehicle model information, function identifier, and ECU identifier, thereby realizing fault code clearing and clearing result determination. This eliminates the need to write fault code clearing instructions for different vehicle models, different function identifiers, or different ECU identifiers, saving time and manpower costs and improving diagnostic efficiency.

[0087] In another embodiment, after obtaining the diagnostic result data returned by the vehicle to be diagnosed, the method further includes: recording the obtained diagnostic result data in a diagnostic log. For example, after obtaining a fault code, the fault code is recorded in the diagnostic log, along with information such as the time of diagnosis, device number, and diagnostic result, to facilitate review by technicians.

[0088] In another embodiment, after the diagnostic process is detected to be complete, a diagnostic log is acquired, and a corresponding diagnostic result is generated and displayed based on the log. For example, after the diagnostic process is detected to be complete, a diagnostic result indicating that the vehicle is fault-free is generated and displayed on a monitor to facilitate technicians' understanding of the vehicle's diagnostic results.

[0089] In one embodiment, a protocol library is pre-configured in the memory of the diagnostic device. This library includes diagnostic protocols for at least one vehicle model. When diagnosing a vehicle, the system first matches the corresponding diagnostic protocol from the library based on the determined vehicle model information. This diagnostic protocol includes multiple diagnostic parameters corresponding to that vehicle model. Then, the system determines the corresponding diagnostic parameters from the diagnostic protocol based on the function identifier and ECU identifier, thereby generating the corresponding diagnostic command to complete the diagnosis. Each time a technician diagnoses a different vehicle model, function identifier, and ECU identifier, they only need to write the diagnostic parameters once and save them in the protocol library. Subsequent diagnoses only require searching and retrieving these parameters from the library, thus saving the technician's workload.

[0090] Example 4:

[0091] This embodiment provides a vehicle fault diagnosis device, such as... Figure 5 The diagnostic device includes: an acquisition module 501, a loading module 502, and an execution module 503.

[0092] The acquisition module 501 is used to acquire the vehicle model information of the vehicle to be diagnosed; the loading module 502 is used to load a pre-recorded diagnostic process file, which records at least one diagnostic step, each diagnostic step including a function identifier and an ECU identifier. The execution module 503 is used to execute the diagnostic process file, and for each diagnostic step, determines the corresponding diagnostic parameters based on the vehicle model information, function identifier, and ECU identifier; sends the corresponding diagnostic command according to the determined diagnostic parameters, and acquires the diagnostic result data returned by the vehicle to be diagnosed.

[0093] In one embodiment, the diagnostic device further includes an output module 504, which is used to output corresponding diagnostic results. For example, the output module 504 can be a display for displaying diagnostic logs.

[0094] In one embodiment, the vehicle fault diagnosis device further includes an editing module 506 and a storage module 507. The editing module 506 is used by staff to edit or modify diagnostic process files, such as modifying diagnostic parameters in the protocol library. The storage module 507 is used to store relevant data information, such as storing diagnostic parameters and diagnostic process file related data.

[0095] In another embodiment, the vehicle fault diagnosis device further includes a communication module 508, which can wirelessly communicate with the cloud server 509. The diagnostic process files, as well as the aforementioned instruction data and algorithm data, can also be stored in the cloud server 509, and the corresponding data can be retrieved from the cloud server during diagnosis. Alternatively, the obtained diagnostic logs and results can be uploaded to the cloud server 509 for storage, allowing users to view the diagnostic results at any time via a mobile device (such as a mobile phone).

[0096] During operation, the vehicle fault diagnosis device is connected to the vehicle's OBD communication interface, and then the diagnostic program is started. The diagnostic equipment can automatically identify the vehicle model and complete the diagnostic process, outputting a diagnostic log. This eliminates the need for technicians to write diagnostic strategies for each vehicle model, saving manpower and time costs.

[0097] Example 5:

[0098] This embodiment provides a vehicle fault diagnosis device, such as... Figure 6 The diagnostic device includes a memory 601 and a processor 602; the memory 601 is used to store programs; the processor 602 is used to implement the diagnostic method provided in Embodiment 1 above by executing the programs stored in the memory.

[0099] The vehicle fault diagnosis equipment may be a desktop computer, laptop, handheld computer, or cloud server, etc. This electronic device may include, but is not limited to, a processor 602 and a memory 601. Those skilled in the art will understand that... Figure 6 This is merely an example of vehicle fault diagnosis equipment and does not constitute a limitation on vehicle fault diagnosis equipment. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components, such as input / output devices, network access devices, etc.

[0100] The processor 602 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0101] In some embodiments, the memory 601 may be an internal storage unit of the vehicle fault diagnosis device, such as a hard drive or memory. In other embodiments, the memory 601 may be an external storage device of the vehicle fault diagnosis device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the vehicle fault diagnosis device. Furthermore, the memory 601 may include both internal and external storage units of the vehicle fault diagnosis device. The memory 601 is used to store the operating system, applications, bootloader, data, and other programs, such as the program code of the computer program. The memory 601 can also be used to temporarily store data that has been output or will be output.

[0102] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0103] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0104] Example 6:

[0105] This embodiment provides a computer-readable storage medium storing a program that can be executed by a processor to implement the diagnostic method provided in Embodiment 1 above.

[0106] Those skilled in the art will understand that all or part of the functions of the various methods in the above embodiments can be implemented by hardware or by computer programs. When all or part of the functions in the above embodiments are implemented by computer programs, the program can be stored in a computer-readable storage medium, which may include: read-only memory, random access memory, disk, optical disk, hard disk, etc., and the program is executed by a computer to achieve the above functions. For example, the program can be stored in the memory of a device, and when the program in the memory is executed by the processor, all or part of the above functions can be achieved. In addition, when all or part of the functions in the above embodiments are implemented by computer programs, the program can also be stored in a server, another computer, disk, optical disk, flash drive, or external hard drive, etc., and can be downloaded or copied to the memory of a local device, or the system of the local device can be updated. When the program in the memory is executed by the processor, all or part of the functions in the above embodiments can be achieved. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium may include at least: any entity or device capable of carrying computer program code to a photographic device / terminal device, recording media, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media. Examples include USB flash drives, portable hard drives, magnetic disks, or optical discs. In some jurisdictions, according to legislation and patent practice, computer-readable media may not be electrical carrier signals or telecommunication signals.

[0107] The above examples illustrate this application only to aid understanding and are not intended to limit its scope. Those skilled in the art to which this application pertains can make various simple deductions, modifications, or substitutions based on the ideas presented.

Claims

1. A vehicle malfunction diagnosis method characterized by comprising: The vehicle fault diagnosis method includes: Obtain the vehicle model information of the vehicle currently being diagnosed; Load a pre-recorded diagnostic process file, which records at least one diagnostic step, each of which includes a function identifier and an ECU identifier; Execute the diagnostic process file, and for each diagnostic step, determine the corresponding diagnostic parameters based on the vehicle model information, function identifier, and ECU identifier; A protocol library is pre-configured in the diagnostic equipment, and the protocol library includes diagnostic protocols for at least one vehicle model; Match the corresponding diagnostic protocol from the protocol library based on the vehicle model information; The corresponding diagnostic parameters are determined from the diagnostic protocol based on the function identifier and the ECU identifier; Based on the determined diagnostic parameters, send the corresponding diagnostic command and obtain the diagnostic result data returned by the vehicle to be diagnosed.

2. The vehicle malfunction diagnosis method according to claim 1, characterized by The corresponding diagnostic parameters are determined based on the vehicle model information, function identifier, and ECU identifier. Based on the determined diagnostic parameters, send the corresponding diagnostic command and obtain the diagnostic result data returned by the vehicle to be diagnosed, including: Based on the vehicle model information, function identifier, and ECU identifier, the corresponding communication parameters are searched in the preset protocol library; Generate communication instructions based on the communication parameters; A request to establish a communication connection is initiated to the target ECU according to the communication instructions; Obtain the communication connection establishment result data returned by the target ECU; The diagnostic parameters include the communication parameters, the diagnostic instructions include the communication instructions, and the diagnostic result data includes the communication connection establishment result data.

3. The vehicle malfunction diagnosis method according to claim 1, characterized by The corresponding diagnostic parameters are determined based on the vehicle model information, function identifier, and ECU identifier. Based on the determined diagnostic parameters, send the corresponding diagnostic command and obtain the diagnostic result data returned by the vehicle to be diagnosed, including: Based on the vehicle model information, function identifier, and ECU identifier, the corresponding reading parameters and the first parsing algorithm are searched in the preset protocol library; Generate a read instruction based on the read parameters; Send the read command to the target ECU; Obtain the diagnostic result data returned by the target ECU; The diagnostic result data is analyzed based on the first parsing algorithm; The diagnostic parameters include the reading parameters and the first parsing algorithm, and the diagnostic instructions include the reading instructions.

4. The vehicle malfunction diagnosis method according to claim 1, characterized by The corresponding diagnostic parameters are determined based on the vehicle model information, function identifier, and ECU identifier. Based on the determined diagnostic parameters, send the corresponding diagnostic command and obtain the diagnostic result data returned by the vehicle to be diagnosed, including: Based on the vehicle model information, function identifier, and ECU identifier, the corresponding clearing parameters and clearing result determination algorithm are searched in the preset protocol library; Based on the clearing parameters and the clearing result determination algorithm, clearing instructions and clearing result determination instructions are generated respectively; Send the clear command to clear the fault codes of the vehicle to be diagnosed; Send the clearing result determination instruction to obtain the clearing result of the fault code; The diagnostic parameters include the clearing parameters and the clearing result determination parameters; the diagnostic instructions include the clearing instructions and the clearing result determination instructions; and the diagnostic result data includes the clearing result of the fault code.

5. The vehicle malfunction diagnosing method according to any one of claims 2 to 4, characterized in that, The method further comprises, after obtaining the diagnosis result data returned by the vehicle to be diagnosed, recording the obtained diagnosis result data in a diagnosis log.

6. The vehicle malfunction diagnosis method according to claim 5, characterized by The method further comprises: After detecting that the diagnosis process ends, obtaining the diagnosis log, and generating and displaying a corresponding diagnosis result according to the diagnosis log.

7. A vehicle malfunction diagnosing apparatus characterized by comprising: The vehicle fault diagnosis device is applied to the vehicle fault diagnosis method as claimed in any one of claims 1-6. An obtaining module is configured to obtain vehicle model information of a vehicle to be diagnosed. A loading module is configured to load a pre-recorded diagnosis process file, the diagnosis process file recording at least one diagnosis step, each diagnosis step including a function identifier and an ECU identifier. An executing module is configured to execute the diagnosis process file, for each diagnosis step, determine a corresponding diagnosis parameter based on the vehicle model information, the function identifier, and the ECU identifier, send a corresponding diagnosis instruction according to the determined diagnosis parameter, and obtain diagnosis result data returned by the vehicle to be diagnosed.

8. A vehicle malfunction diagnosing apparatus characterized by comprising: The method further comprises: A memory is configured to store a program. A processor is configured to execute the program stored in the memory to implement the method as claimed in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The medium has a program stored thereon, and the program can be executed by a processor to implement the method as claimed in any one of claims 1-6.

Images