Abnormal diagnosis analysis method, device, equipment and computer program product

By comparing and analyzing the log files of the vehicle electronic control unit and diagnostic equipment, the problem of low efficiency in vehicle diagnostic abnormality analysis is solved, and the method of quickly positioning abnormality problems is realized, and the diagnostic efficiency is improved.

CN119087964AActive Publication Date: 2024-12-06LAUNCH TECH CO LTD

Patent Information

Application Number
CN202411184251.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-27
Publication Date
2024-12-06
Estimated Expiration
2044-08-27

AI Technical Summary

Technical Problem

Vehicle diagnostic abnormality analysis efficiency is low, and it is difficult for the prior art to record and locate abnormality problems through the communication log between the diagnostic equipment and the vehicle ECU.

Method used

By generating diagnostic process record requests and pre-generated diagnostic abnormal process data, the log files of the vehicle's electronic control unit and diagnostic equipment are obtained, and the abnormal problems are directly located.

Benefits of technology

It greatly improves the efficiency of vehicle diagnostic abnormality analysis, and can compare the debugging information at both ends of the diagnostic equipment and the vehicle electronic control unit at the same time, and directly locate abnormal problems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119087964A_ABST
    Figure CN119087964A_ABST
Patent Text Reader

Abstract

The invention discloses a diagnosis abnormity analysis method, device and equipment and a computer program product, and relates to the technical field of vehicle diagnos.The diagnosis abnormity analysis method comprises the steps that in response to a diagnosis abnormity analysis instruction, diagnosis abnormity process data generated in advance is obtained, and a diagnosis process recording request is generated; according to the diagnosis process recording request and the diagnosis abnormal process data, generating a diagnosis equipment log file, and obtaining an electronic control unit log file generated by a vehicle electronic control unit; and performing comparative analysis according to the electronic control unit log file and the diagnosis equipment log file to obtain a diagnosis abnormality analysis result. By comparing and analyzing the electronic control unit log file and the diagnosis equipment log file, the diagnosis debugging information at the two ends of the diagnosis equipment and the vehicle electronic control unit can be compared at the same time, the abnormal problem is directly positioned, the problem that in the prior art, the vehicle diagnosis abnormal analysis efficiency is low is solved, and the vehicle diagnosis abnormal analysis efficiency is improved. And the vehicle diagnosis abnormity analysis efficiency is greatly improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle diagnosis technology, and in particular to a diagnostic abnormality analysis method, device, equipment and computer program product. Background Art

[0002] As vehicle functions become more and more complex, the number of diagnostic functions supported by vehicle electronic control units (ECUs) is also increasing. During the development of vehicle diagnostic functions or after-sales fault diagnosis, it is common to encounter abnormal errors when using diagnostic equipment to perform diagnostic functions on vehicle ECUs. At this time, it is necessary to confirm where the problem occurred. Currently, when diagnostic equipment communicates with vehicle ECUs to perform diagnostic functions, there will be request and response message log records, and the cause can be analyzed through log records. However, it is impossible to truly locate abnormal problems based only on the request and response message log records of diagnostic equipment, and the efficiency of diagnostic abnormality analysis is low.

[0003] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0004] The main purpose of the present application is to provide a diagnostic abnormality analysis method, device, equipment and computer program product, aiming to solve the technical problem of low efficiency of vehicle diagnostic abnormality analysis.

[0005] To achieve the above objectives, the present application proposes a diagnostic abnormality analysis method, which is applied to a diagnostic device and includes:

[0006] In response to the diagnostic anomaly analysis instruction, obtaining pre-generated diagnostic anomaly process data and generating a diagnostic process record request;

[0007] Generate a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormality process data, and obtain an electronic control unit log file generated by the vehicle electronic control unit;

[0008] A comparative analysis is performed based on the electronic control unit log file and the diagnostic device log file to obtain a diagnostic abnormality analysis result.

[0009] In one embodiment, before the step of obtaining pre-generated diagnostic abnormality process data in response to the diagnostic abnormality analysis instruction and generating a diagnostic process record request, the step further includes:

[0010] When vehicle diagnosis error information is detected, the diagnosis abnormality process data is generated according to the current vehicle diagnosis process data and the vehicle diagnosis error information, and the diagnosis abnormality analysis instruction is triggered.

[0011] In one embodiment, the step of generating a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormality process data, and obtaining an electronic control unit log file generated by a vehicle electronic control unit includes:

[0012] sending the diagnostic process record request to the vehicle electronic control unit;

[0013] Diagnose the vehicle according to the abnormal diagnosis process data, and record the log information of the diagnostic device according to the diagnostic process record request to generate the diagnostic device log file;

[0014] Obtain the electronic control unit log file generated by the vehicle electronic control unit.

[0015] In one embodiment, the step of diagnosing the vehicle according to the abnormal diagnosis process data and recording the log information of the diagnostic device according to the diagnostic process record request, and generating the diagnostic device log file includes:

[0016] Creating an initial diagnostic device log file based on the diagnostic process record request;

[0017] Parsing the abnormal diagnosis process data to obtain a set of diagnostic function data to be executed and diagnostic function execution order data;

[0018] According to the diagnostic function execution order data, perform vehicle diagnosis in sequence according to the diagnostic function data to be executed in the diagnostic function data set to be executed, generate device-side execution information and vehicle diagnostic instructions, and send the vehicle diagnostic instructions to the vehicle electronic control unit;

[0019] receiving a vehicle diagnostic command reply sent by the vehicle electronic control unit;

[0020] The device-side execution information, vehicle diagnostic instruction response and pre-generated diagnostic start time are written into the initial diagnostic device log file until the set of diagnostic function data to be executed is traversed to obtain the diagnostic device log file.

[0021] In one embodiment, the step of performing vehicle diagnosis in sequence according to the diagnostic function execution order data and the diagnostic function data to be executed in the diagnostic function data set to be executed, generating device-side execution information and vehicle diagnostic instructions, and sending the vehicle diagnostic instructions to the vehicle electronic control unit also includes:

[0022] Receiving the name of an initial ECU log file sent by the vehicle ECU, wherein the name of the initial ECU log file is the same as the ECU log file, and recording the current time as the diagnosis start time;

[0023] The diagnosis start time is sent to the vehicle electronic control unit to synchronize the start time recorded in the electronic control unit log file and the diagnostic device log file.

[0024] In one embodiment, the step of obtaining the electronic control unit log file generated by the vehicle electronic control unit includes:

[0025] generating an electronic control unit log file return instruction according to the name of the initial electronic control unit log file;

[0026] Sending the electronic control unit log file return instruction to the vehicle electronic control unit;

[0027] Receive the electronic control unit log file sent by the vehicle electronic control unit.

[0028] In addition, to achieve the above purpose, the present application also proposes a diagnostic abnormality analysis method, which is applied to a vehicle electronic control unit, and the method includes:

[0029] Receiving a diagnostic process record request sent by a diagnostic device;

[0030] Creating an initial ECU log file according to the diagnostic process record request;

[0031] Receiving the diagnosis start time and vehicle diagnosis instruction sent by the diagnostic device;

[0032] Execute vehicle diagnosis according to the vehicle diagnosis instruction to obtain vehicle-side execution information;

[0033] Writing the vehicle-side execution information, the diagnosis start time and the vehicle diagnosis command into the initial ECU log file to obtain an ECU log file;

[0034] The electronic control unit log file is sent to the diagnostic device so that the diagnostic device can perform diagnostic abnormality analysis.

[0035] In addition, to achieve the above-mentioned purpose, the present application also proposes a diagnostic abnormality analysis device, the diagnostic abnormality analysis device comprising:

[0036] A first generating module, configured to obtain pre-generated diagnostic abnormality process data in response to a diagnostic abnormality analysis instruction, and generate a diagnostic process record request;

[0037] A second generating module, configured to generate a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormality process data, and obtain an electronic control unit log file generated by the vehicle electronic control unit;

[0038] The comparison and analysis module is used to perform comparison and analysis based on the electronic control unit log file and the diagnostic device log file to obtain a diagnostic abnormality analysis result.

[0039] In addition, to achieve the above-mentioned purpose, the present application also proposes a diagnostic anomaly analysis device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the diagnostic anomaly analysis method as described above.

[0040] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the diagnostic abnormality analysis method described above are implemented.

[0041] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the diagnostic abnormality analysis method described above are implemented.

[0042] The present application provides a diagnostic anomaly analysis method. When an abnormality occurs in vehicle diagnosis, an electronic control unit log file and a diagnostic device log file are obtained according to the diagnostic process record request and the diagnostic anomaly process data. By comparing and analyzing the electronic control unit log file and the diagnostic device log file, the diagnostic debugging information at both ends of the diagnostic device and the vehicle electronic control unit can be compared at the same time, and the abnormal problem can be directly located. The problem of low efficiency of vehicle diagnostic anomaly analysis in the prior art is solved, and the efficiency of vehicle diagnostic anomaly analysis is greatly improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] 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.

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present application or 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.

[0045] Figure 1 A schematic diagram of a process flow provided for the first embodiment of the abnormality analysis method of the present application;

[0046] Figure 2 A schematic diagram of a process flow provided for Embodiment 2 of the diagnostic abnormality analysis method of the present application;

[0047] Figure 3A flowchart of the third embodiment of the abnormality analysis method of the present application is provided;

[0048] Figure 4 This is a schematic diagram of the module structure of the abnormality diagnosis and analysis device according to an embodiment of the present application;

[0049] Figure 5 Schematic diagram of the device structure of the hardware operating environment involved in the diagnostic abnormality analysis method in the embodiment of the present application.

[0050] 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

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

[0052] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0053] The main solutions of the embodiments of this application are:

[0054] In response to the diagnostic anomaly analysis instruction, obtaining pre-generated diagnostic anomaly process data and generating a diagnostic process record request;

[0055] Generate a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormality process data, and obtain an electronic control unit log file generated by the vehicle electronic control unit;

[0056] A comparative analysis is performed based on the electronic control unit log file and the diagnostic device log file to obtain a diagnostic abnormality analysis result.

[0057] In the prior art, the diagnostic device request and reply message logs are only unilaterally recorded by the diagnostic device and do not include the ECU logs, such as whether the ECU did not receive the request or the ECU received but did not process it. It is impossible to directly locate the abnormal problem, and the efficiency of vehicle diagnostic abnormality analysis is low.

[0058] The present application provides a solution. When an abnormality occurs in vehicle diagnosis, an electronic control unit log file and a diagnostic device log file are obtained according to the diagnostic process record request and the diagnostic abnormality process data. By comparing and analyzing the electronic control unit log file and the diagnostic device log file, the diagnostic debugging information at both ends of the diagnostic device and the vehicle electronic control unit can be compared at the same time, and the abnormal problem can be directly located. The problem of low efficiency of vehicle diagnostic abnormality analysis in the prior art is solved, and the efficiency of vehicle diagnostic abnormality analysis is greatly improved.

[0059] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a diagnostic abnormality analysis system, etc. The following takes the diagnostic abnormality analysis system as an example to illustrate this embodiment and the following embodiments, wherein the diagnostic abnormality analysis system includes a diagnostic device and a vehicle electronic control unit.

[0060] Based on this, the present application embodiment provides a method for diagnosing abnormality analysis, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the abnormality diagnosis analysis method of the present application.

[0061] In this embodiment, the diagnostic abnormality analysis method is applied to a diagnostic device, including steps S01 to S03:

[0062] Step S01, in response to a diagnosis abnormality analysis instruction, obtaining pre-generated diagnosis abnormality process data and generating a diagnosis process record request;

[0063] The diagnostic device responds to the diagnostic abnormality analysis instruction, obtains the pre-generated diagnostic abnormality process data, and generates a diagnostic process record request

[0064] It should be noted that the diagnostic exception analysis instruction is triggered when a diagnostic exception occurs. The diagnostic exception process data is the diagnostic process data that the diagnostic device is currently performing when the diagnostic exception occurs. The diagnostic process record request contains the detailed steps, data or events that the device needs to record during the exception analysis process for subsequent analysis and backtracking.

[0065] In a feasible implementation manner, step S04 may be further included before step S01:

[0066] Step S04, when vehicle diagnosis error information is detected, the diagnosis abnormality process data is generated according to the current vehicle diagnosis process data and the vehicle diagnosis error information, and the diagnosis abnormality analysis instruction is triggered.

[0067] When vehicle diagnostic error information is detected, the diagnostic device generates diagnostic abnormality process data based on the current vehicle diagnostic process data and the vehicle diagnostic error information, and triggers a diagnostic abnormality analysis instruction.

[0068] In this embodiment, when vehicle diagnostic error information is detected, the diagnostic abnormality process data is generated according to the current vehicle diagnostic process data and the vehicle diagnostic error information, and the diagnostic abnormality analysis instruction is triggered, thereby ensuring that when vehicle diagnostic error information is detected, the system can generate corresponding abnormal process data in a timely manner and automatically start the relevant diagnostic abnormality analysis process, so as to quickly respond to and locate possible diagnostic abnormality problems.

[0069] Step S02, generating a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormality process data, and obtaining an electronic control unit log file generated by the vehicle electronic control unit;

[0070] Step S03: performing comparative analysis based on the ECU log file and the diagnostic device log file to obtain a diagnostic abnormality analysis result.

[0071] The diagnostic device sends a diagnostic process record request to the vehicle electronic control unit, which records the subsequent vehicle diagnostic process to obtain an electronic control unit log file. At the same time, the device performs vehicle diagnosis and records according to the diagnostic process record request and diagnostic abnormality process data to obtain a diagnostic device log file. A comparative analysis is then performed between the electronic control unit log file and the diagnostic device log file to obtain a diagnostic abnormality analysis result.

[0072] The present embodiment provides a diagnostic anomaly analysis method. When an abnormality occurs in vehicle diagnosis, an electronic control unit log file and a diagnostic device log file are obtained according to the diagnostic process record request and the diagnostic anomaly process data. By comparing and analyzing the electronic control unit log file and the diagnostic device log file, the diagnostic debugging information at both ends of the diagnostic device and the vehicle electronic control unit can be compared at the same time, and the abnormal problem can be directly located. The problem of low efficiency of vehicle diagnostic anomaly analysis in the prior art is solved, and the efficiency of vehicle diagnostic anomaly analysis is greatly improved.

[0073] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 2 , step S02 may further include steps S021 to S023:

[0074] Step S021, sending the diagnostic process record request to the vehicle electronic control unit;

[0075] Step S022, diagnosing the vehicle according to the abnormal diagnosis process data, and recording the log information of the diagnostic device according to the diagnostic process record request to generate the diagnostic device log file;

[0076] Step S023, obtaining the electronic control unit log file generated by the vehicle electronic control unit.

[0077] The diagnostic device first sends a diagnostic process record request to the vehicle electronic control unit, which is usually completed through the vehicle's internal data bus or a dedicated communication protocol to ensure that the request can be accurately and timely received and executed. The diagnostic process record request usually includes specific data and information types that need to be recorded to ensure that all key aspects required for diagnosis are covered. Then, based on the diagnostic abnormal process data, it is determined how to diagnose the vehicle. These data may include fault codes, abnormal states of sensor data, response speeds of system components, etc. During the diagnostic process, the log information of the diagnostic device is synchronously recorded to generate a diagnostic device log file, where the diagnostic device log file may include the timestamp of each step of the diagnostic process executed to milliseconds, a description of the diagnostic function executed (reading fault codes, writing configurations, etc.), the system ID of the communicating ECU (request and reply ID), the diagnostic data sent and received, and other information. Finally, the electronic control unit log file generated by the vehicle electronic control unit is obtained. The electronic control unit log file is generated by the vehicle electronic control unit based on the received diagnostic process record request, and may include information such as the diagnostic data received by the ECU, the reception time, the internal processing process, the diagnostic data sent, and the sending time.

[0078] In a feasible implementation, step S022 may include steps S0221 to S0225:

[0079] Step S0221, creating an initial diagnostic device log file according to the diagnostic process record request;

[0080] Step S0222, parsing the abnormal diagnosis process data to obtain a set of diagnostic function data to be executed and diagnostic function execution order data;

[0081] Step S0223, according to the diagnostic function execution order data, perform vehicle diagnosis in sequence according to the diagnostic function data to be executed in the diagnostic function data set to be executed, generate device-side execution information and vehicle diagnostic instructions, and send the vehicle diagnostic instructions to the vehicle electronic control unit;

[0082] Step S0224, receiving a vehicle diagnostic instruction reply sent by the vehicle electronic control unit;

[0083] Step S0225, writing the device-side execution information, vehicle diagnostic instruction response and pre-generated diagnostic start time into the initial diagnostic device log file until the set of diagnostic function data to be executed is traversed to obtain the diagnostic device log file.

[0084] The diagnostic device first creates an initial diagnostic device log file according to the diagnostic process record request, then parses the diagnostic abnormality process data, obtains the set of diagnostic function data to be executed and the diagnostic function execution order data, which are key steps in the vehicle diagnostic process, ensuring that the diagnostic functions are executed in the correct order and collecting relevant data, and then the device obtains each diagnostic function data to be executed from the set of diagnostic function data to be executed in a predetermined order according to the diagnostic function execution order data, which generally includes the name of the diagnostic function, parameter settings, execution conditions and other information, and generates corresponding vehicle diagnostic instructions according to each diagnostic function data to be executed. These instructions are operation commands for the vehicle electronic control unit, which are used to execute specific diagnostic functions, such as reading sensor data, executing self-test programs, etc. At the same time, according to the set of diagnostic function data to be executed, prepare the device-side execution information, which may include the start time of the diagnostic task, device identification, log records of execution operations, etc., and send the vehicle diagnostic instructions to the vehicle electronic control unit. The sub-control unit then receives the vehicle diagnostic command reply sent by the vehicle electronic control unit. The vehicle diagnostic command reply may include the timestamp of the reply, the specific content, any diagnostic results or status information. Finally, the device opens or accesses the existing initial diagnostic device log file and writes the pre-generated diagnostic start time into the log file. This time marks the beginning of the diagnostic process, which helps with subsequent analysis and timeline tracking. For each executed diagnostic function, the relevant device-side execution information is recorded. This information includes the name of the diagnostic function, the execution start time, the relevant device identification or other identifiers, the log records during the execution process, etc. For each received vehicle diagnostic command reply, the relevant information is recorded, which may include the timestamp of the reply, the specific reply content, whether the reply is successfully received, the result or status information of the execution, etc. After completing the traversal of all the diagnostic function data sets to be executed, the diagnostic device log file is obtained and closed, which ensures that all recording operations have been completed and the file content has been saved intact.

[0085] It should be noted that the diagnostic function to be executed may be determined according to the specific problem of the vehicle or the predetermined diagnostic process, such as executing specific sensor detection, self-test of the electronic control unit, etc. The execution order of the diagnostic functions can be sorted and determined according to the diagnostic function execution order data.

[0086] In this implementation, the vehicle is diagnosed based on the diagnostic abnormality process data, and the log information of the diagnostic device during the diagnostic process is recorded according to the diagnostic process record request, and a diagnostic device log file is generated, ensuring that the diagnostic device can record and manage various key data and events in the diagnostic process when executing the diagnostic process, providing necessary support and basis for subsequent analysis and problem solving.

[0087] In another feasible implementation manner, before step S0223, steps S02261 to S02262 may also be included:

[0088] Step S02261, receiving the name of the initial ECU log file sent by the vehicle ECU, wherein the name of the initial ECU log file is the same as the ECU log file, and recording the current time as the diagnosis start time;

[0089] Step S02262, sending the diagnosis start time to the vehicle electronic control unit to synchronize the start time recorded in the electronic control unit log file and the diagnostic device log file.

[0090] The diagnostic device receives the name of the initial ECU log file sent from the vehicle ECU. This name is the same as the log file recorded by the actual ECU in the vehicle. It may be a file name or identifier used to identify a specific ECU log. After receiving the log file name, the current time is immediately recorded as the diagnostic start time. This time point will be used as the start time of the diagnostic process for subsequent timestamps and time records of log files. Finally, the diagnostic start time is sent to the vehicle ECU. After receiving the diagnostic start time, the vehicle ECU confirms that the time synchronization has been successfully completed, which means that the time base recorded by the vehicle ECU and the device end is the same. From this time point, both begin to record log information related to the diagnosis.

[0091] In this embodiment, the name of the initial ECU log file sent by the vehicle ECU is received, wherein the name of the initial ECU log file is the same as the ECU log file, and the current time is recorded as the diagnosis start time; the diagnosis start time is sent to the vehicle ECU to synchronize the start time of the ECU log file and the diagnostic device log file. This ensures that the preparation and time synchronization of the ECU log file and the diagnostic device log file are complete and consistent before the actual execution of the diagnostic function. This is crucial for timeline management and data analysis in the subsequent diagnostic process.

[0092] In another feasible implementation, step S023 may include steps S0231 to S0233:

[0093] Step S0231, generating an ECU log file return instruction according to the name of the initial ECU log file;

[0094] Step S0232, sending the electronic control unit log file return instruction to the vehicle electronic control unit;

[0095] Step S0233, receiving the electronic control unit log file sent by the vehicle electronic control unit.

[0096] The diagnostic device generates an ECU log file return instruction based on the name of the initial ECU log file, which is used to instruct the vehicle ECU to send the specific log file back to the diagnostic device, and then sends the ECU log file return instruction to the vehicle ECU, and finally receives the ECU log file sent by the vehicle ECU.

[0097] It should be noted that the ECU log file return instruction may include the name or identifier of the log file, a request instructing the ECU to send the log file to the diagnostic device, a timestamp or time range of the request to send (if a log for a specific time period is required), and other information.

[0098] In this embodiment, the electronic control unit log file return instruction is generated according to the name of the initial electronic control unit log file, the electronic control unit log file is received, and the log file of the vehicle electronic control unit is obtained and saved during the diagnosis process for subsequent analysis or troubleshooting. In this way, the device side can obtain real-time or historical electronic control unit operation data to help diagnose possible problems with the vehicle or optimize its performance.

[0099] In this embodiment, the electronic control unit log file and the diagnostic device log file are obtained based on the diagnostic process record request and the diagnostic abnormality process data, which provides support for the subsequent comparative analysis of the electronic control unit log file and the diagnostic device log file, and at the same time compares the diagnostic debugging information at both ends of the diagnostic device and the vehicle electronic control unit to locate the abnormal problem.

[0100] In addition, the present application embodiment provides a method for diagnosing abnormality analysis, referring to Figure 3 , Figure 3 This is a flowchart of the third embodiment of the abnormality diagnosis analysis method of the present application.

[0101] In this embodiment, the diagnostic abnormality analysis method is applied to a vehicle electronic control unit, including steps S05 to S10:

[0102] Step S05, receiving a diagnostic process record request sent by a diagnostic device;

[0103] Step S06, creating an initial ECU log file according to the diagnostic process record request;

[0104] Step S07, receiving the diagnosis start time and vehicle diagnosis instruction sent by the diagnostic device;

[0105] Step S08, executing vehicle diagnosis according to the vehicle diagnosis instruction to obtain vehicle-side execution information;

[0106] Step S09, writing the vehicle-side execution information, diagnosis start time and vehicle diagnosis instruction into the initial ECU log file to obtain an ECU log file;

[0107] Step S10, sending the ECU log file to the diagnostic device so that the diagnostic device can perform abnormality diagnosis analysis.

[0108] It should be noted that the Electronic Control Unit (ECU) is also called the car's "on-board computer". Its purpose is to control the car's driving status and realize its various functions. It mainly uses various sensors and bus data collection and exchange to judge the vehicle status and the driver's intentions and control the car through actuators. Currently, vehicles are equipped with multiple ECUs, such as engine ECU, gearbox ECU, etc.

[0109] When the diagnostic device needs to perform diagnostic abnormality analysis, the vehicle electronic control unit receives the diagnostic process record request sent by the diagnostic device, and starts to create an initial electronic control unit log file according to the received diagnostic process record request. This file will be used to record important information in the following diagnostic process, and then receives the diagnostic start time and vehicle diagnostic instructions sent by the diagnostic device, and then starts to perform corresponding vehicle diagnostic operations according to the received vehicle diagnostic instructions. These operations may include reading sensor data, performing specific control operations, etc., and obtaining vehicle-side execution information. Then, during the execution of the diagnosis, the electronic control unit writes the obtained vehicle-side execution information, diagnostic start time and vehicle diagnostic instructions into the previously created initial electronic control unit log file. In this way, the key information of the entire diagnostic process can be recorded to obtain the electronic control unit log file. Finally, after the vehicle diagnosis is completed, the electronic control unit sends this file to the diagnostic device, and the diagnostic device will use these log files to perform diagnostic abnormality analysis to determine whether the vehicle has abnormal conditions during the diagnostic process and how to solve these abnormalities.

[0110] For example, in one implementation, no recording is required under normal diagnostic conditions, and the default is not to record execution information. If an abnormality occurs in the vehicle diagnosis, it is necessary to record the execution information of the diagnostic device and the vehicle ECU during the entire diagnostic process. When it is necessary to record execution information, the information recording function of the diagnostic device and the ECU needs to be started before the vehicle is diagnosed. Therefore, the process of implementing diagnostic abnormality analysis through the interaction between the diagnostic device and the vehicle electronic control unit is as follows:

[0111] 1. First, start the information recording function of the diagnostic device and create a new information recording log file F1. Turn on the information recording flag. After turning it on, the diagnostic device will write the information of each step into the information recording log file when executing each diagnostic function. The contents written into the information recording log file by the diagnostic device include: the timestamp of each step execution accurate to milliseconds, the description of the executed diagnostic function (reading fault codes, writing configurations, etc.), the system ID of the communicating ECU (request and reply ID), and the diagnostic data sent and received.

[0112] 2. The diagnostic device then sends a command to the ECU to be diagnosed to start the ECU's information recording function. An ECU log file F2 is also created inside the ECU to record the diagnostic data received by the ECU, the reception time, the internal processing process, the diagnostic data sent and the sending time, etc.

[0113] 3. After the ECU successfully creates the log file, it will reply the log file name to the diagnostic device for reading after the diagnosis is completed.

[0114] 4. After the diagnostic device receives the log file name replied by the ECU, it will send the current time of the diagnostic device to the ECU for synchronization to ensure that the time of recording information on the diagnostic device and the ECU is synchronized, so as to facilitate the comparative analysis of the two log files after the diagnosis is completed.

[0115] 5. After the diagnostic device and ECU information recording functions are successfully started, you can use the diagnostic device to diagnose the vehicle, select and execute diagnostic functions on the diagnostic device, such as reading fault codes, flashing firmware, writing configuration codes, reading data streams, etc. The diagnostic device will write the execution information to F1 in real time, and the ECU will record the information to F2.

[0116] 6. After the diagnosis is completed, the diagnostic device sends a command to the ECU to send back the ECU log file, which contains the name of the ECU log file. The ECU will send the file F2 with this name back to the diagnostic device.

[0117] 7. The diagnostic device then displays the log information of the diagnostic device and the ECU at the same time, and compares the information records at both ends according to the timeline to quickly locate the cause of the error.

[0118] 8. After the analysis is completed, the diagnostic device can choose whether to clear the log file. If yes, the F1 file on the diagnostic device will be deleted, and a command will be sent to the ECU to clear F2 to free up storage space.

[0119] In this embodiment, when a diagnostic anomaly is encountered, after the diagnostic device starts recording the diagnostic debugging information, it also sends an instruction to the ECU to start recording the diagnostic debugging information of the ECU, and records the time synchronously. The diagnostic debugging information of the ECU is recorded in the ECU to form a debugging file, and after the diagnostic function is executed. The diagnostic device sends an instruction to read the debugging file inside the ECU to the diagnostic device. Therefore, the diagnostic debugging information at both ends of the diagnostic device and the vehicle electronic control unit can be compared at the same time, and the abnormal problem point can be directly located, thereby improving the efficiency of vehicle diagnostic abnormality analysis.

[0120] In this embodiment, the vehicle electronic control unit generates an electronic control unit log file and sends it to the diagnostic device according to the received diagnostic process record request, diagnostic start time and vehicle diagnostic instruction. The diagnostic device can compare the diagnostic debugging information at both ends of the diagnostic device and the vehicle electronic control unit by comparing and analyzing the electronic control unit log file and the diagnostic device log file, and directly locate the abnormal problem, which solves the problem of low efficiency of vehicle diagnostic abnormality analysis in the prior art and greatly improves the efficiency of vehicle diagnostic abnormality analysis.

[0121] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the abnormality diagnosis analysis method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0122] This application also provides a diagnostic abnormality analysis device, please refer to Figure 4 , the abnormality diagnosis and analysis device comprises:

[0123] The first generating module 10 is used to obtain the pre-generated diagnostic abnormality process data in response to the diagnostic abnormality analysis instruction, and generate a diagnostic process record request;

[0124] A second generating module 20, for generating a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormal process data, and obtaining an electronic control unit log file generated by the vehicle electronic control unit;

[0125] The comparison and analysis module 30 is used to perform comparison and analysis based on the ECU log file and the diagnostic device log file to obtain a diagnostic abnormality analysis result.

[0126] Optionally, before the step of obtaining pre-generated diagnostic abnormality process data in response to the diagnostic abnormality analysis instruction and generating a diagnostic process record request, the step further includes:

[0127] When vehicle diagnosis error information is detected, the diagnosis abnormality process data is generated according to the current vehicle diagnosis process data and the vehicle diagnosis error information, and the diagnosis abnormality analysis instruction is triggered.

[0128] Optionally, the second generating module 20 is further used for:

[0129] sending the diagnostic process record request to the vehicle electronic control unit;

[0130] Diagnose the vehicle according to the abnormal diagnosis process data, and record the log information of the diagnostic device according to the diagnostic process record request to generate the diagnostic device log file;

[0131] Obtain the electronic control unit log file generated by the vehicle electronic control unit.

[0132] Optionally, the step of diagnosing the vehicle according to the abnormal diagnosis process data, and recording the log information of the diagnostic device according to the diagnostic process record request, and generating the diagnostic device log file includes:

[0133] Creating an initial diagnostic device log file based on the diagnostic process record request;

[0134] Parsing the abnormal diagnosis process data to obtain a set of diagnostic function data to be executed and diagnostic function execution order data;

[0135] According to the diagnostic function execution order data, perform vehicle diagnosis in sequence according to the diagnostic function data to be executed in the diagnostic function data set to be executed, generate device-side execution information and vehicle diagnostic instructions, and send the vehicle diagnostic instructions to the vehicle electronic control unit;

[0136] receiving a vehicle diagnostic command reply sent by the vehicle electronic control unit;

[0137] The device-side execution information, vehicle diagnostic instruction response and pre-generated diagnostic start time are written into the initial diagnostic device log file until the set of diagnostic function data to be executed is traversed to obtain the diagnostic device log file.

[0138] Optionally, before the step of performing vehicle diagnosis in sequence according to the diagnostic function execution order data and the diagnostic function data to be executed in the diagnostic function data set to be executed, generating device-side execution information and vehicle diagnostic instructions, and sending the vehicle diagnostic instructions to the vehicle electronic control unit, the step further includes:

[0139] Receiving the name of an initial ECU log file sent by the vehicle ECU, wherein the name of the initial ECU log file is the same as the ECU log file, and recording the current time as the diagnosis start time;

[0140] The diagnosis start time is sent to the vehicle electronic control unit to synchronize the start time recorded in the electronic control unit log file and the diagnostic device log file.

[0141] Optionally, the step of obtaining the electronic control unit log file generated by the vehicle electronic control unit includes:

[0142] generating an electronic control unit log file return instruction according to the name of the initial electronic control unit log file;

[0143] Sending the electronic control unit log file return instruction to the vehicle electronic control unit;

[0144] Receive the electronic control unit log file sent by the vehicle electronic control unit.

[0145] The diagnostic abnormality analysis device provided by the present application adopts the diagnostic abnormality analysis method in the above embodiment, which can solve the technical problem of low efficiency of vehicle diagnostic abnormality analysis. Compared with the prior art, the beneficial effects of the diagnostic abnormality analysis device provided by the present application are the same as the beneficial effects of the diagnostic abnormality analysis method provided by the above embodiment, and other technical features in the diagnostic abnormality analysis device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0146] The present application provides a diagnostic anomaly analysis device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the diagnostic anomaly analysis method in the above-mentioned embodiment one.

[0147] Reference below Figure 5 , which shows a schematic diagram of the structure of a diagnostic abnormality analysis device suitable for implementing an embodiment of the present application. The diagnostic abnormality analysis device in the embodiment of the present application may include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The diagnostic abnormality analysis device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0148] like Figure 5As shown, the diagnostic abnormality analysis device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. Various programs and data required for the operation of the diagnostic abnormality analysis device are also stored in the RAM 1004. The processing device 1001, the ROM 1002, and the RAM 1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems may be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 may allow the diagnostic anomaly analysis device to communicate wirelessly or wired with other devices to exchange data. Although the figure shows a diagnostic anomaly analysis device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have alternatively.

[0149] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0150] The diagnostic abnormality analysis device provided by the present application adopts the diagnostic abnormality analysis method in the above embodiment, which can solve the technical problem of low efficiency of vehicle diagnostic abnormality analysis. Compared with the prior art, the beneficial effects of the diagnostic abnormality analysis device provided by the present application are the same as the beneficial effects of the diagnostic abnormality analysis method provided by the above embodiment, and the other technical features in the diagnostic abnormality analysis device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0151] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0152] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0153] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the diagnostic abnormality analysis method in the above-mentioned embodiment.

[0154] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.

[0155] The computer-readable storage medium may be included in the diagnostic abnormality analysis device; or may exist independently without being assembled into the diagnostic abnormality analysis device.

[0156] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the diagnostic abnormality analysis device, the diagnostic abnormality analysis device:

[0157] In response to the diagnostic anomaly analysis instruction, obtaining pre-generated diagnostic anomaly process data and generating a diagnostic process record request;

[0158] Generate a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormality process data, and obtain an electronic control unit log file generated by the vehicle electronic control unit;

[0159] A comparative analysis is performed based on the electronic control unit log file and the diagnostic device log file to obtain a diagnostic abnormality analysis result.

[0160] Computer program code for performing the operation of the present application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).

[0161] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0162] The modules involved in the embodiments of the present application may be implemented by software or hardware, wherein the name of the module does not limit the unit itself in some cases.

[0163] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned diagnostic abnormality analysis method, and can solve the technical problem of low efficiency of vehicle diagnostic abnormality analysis. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the diagnostic abnormality analysis method provided by the above-mentioned embodiment, and will not be repeated here.

[0164] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned diagnostic abnormality analysis method when executed by a processor.

[0165] The computer program product provided by the present application can solve the technical problem of low efficiency of vehicle diagnostic abnormality analysis. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the diagnostic abnormality analysis method provided by the above embodiment, which will not be repeated here.

[0166] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A diagnostic abnormality analysis method, characterized in that: The method is applied to a diagnostic device, and the method comprises: In response to the diagnostic anomaly analysis instruction, obtaining pre-generated diagnostic anomaly process data and generating a diagnostic process record request; Generate a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormality process data, and obtain an electronic control unit log file generated by the vehicle electronic control unit; A comparative analysis is performed based on the electronic control unit log file and the diagnostic device log file to obtain a diagnostic abnormality analysis result.

2. The method according to claim 1, characterized in that Before the step of obtaining pre-generated diagnostic abnormality process data in response to the diagnostic abnormality analysis instruction and generating a diagnostic process record request, the step also includes: When vehicle diagnosis error information is detected, the diagnosis abnormality process data is generated according to the current vehicle diagnosis process data and the vehicle diagnosis error information, and the diagnosis abnormality analysis instruction is triggered.

3. The method according to claim 1, characterized in that The step of generating a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormal process data, and obtaining an electronic control unit log file generated by the vehicle electronic control unit comprises: sending the diagnostic process record request to the vehicle electronic control unit; Diagnose the vehicle according to the abnormal diagnosis process data, and record the log information of the diagnostic device according to the diagnostic process record request to generate the diagnostic device log file; Obtain the electronic control unit log file generated by the vehicle electronic control unit.

4. The method according to claim 3, characterized in that The step of diagnosing the vehicle according to the abnormal diagnosis process data, and recording the log information of the diagnostic device according to the diagnostic process record request, and generating the diagnostic device log file comprises: Creating an initial diagnostic device log file based on the diagnostic process record request; Parsing the abnormal diagnosis process data to obtain a set of diagnostic function data to be executed and diagnostic function execution order data; According to the diagnostic function execution order data, perform vehicle diagnosis in sequence according to the diagnostic function data to be executed in the diagnostic function data set to be executed, generate device-side execution information and vehicle diagnostic instructions, and send the vehicle diagnostic instructions to the vehicle electronic control unit; receiving a vehicle diagnostic command reply sent by the vehicle electronic control unit; The device-side execution information, vehicle diagnostic instruction response and pre-generated diagnostic start time are written into the initial diagnostic device log file until the set of diagnostic function data to be executed is traversed to obtain the diagnostic device log file.

5. The method according to claim 4, characterized in that Before the step of performing vehicle diagnosis in sequence according to the diagnostic function execution order data and the diagnostic function data to be executed in the diagnostic function data set to be executed, generating device-side execution information and vehicle diagnostic instructions, and sending the vehicle diagnostic instructions to the vehicle electronic control unit, the step further includes: Receiving the name of an initial ECU log file sent by the vehicle ECU, wherein the name of the initial ECU log file is the same as the ECU log file, and recording the current time as the diagnosis start time; The diagnosis start time is sent to the vehicle electronic control unit to synchronize the start time recorded in the electronic control unit log file and the diagnostic device log file.

6. The method according to claim 5, characterized in that The step of obtaining the electronic control unit log file generated by the vehicle electronic control unit comprises: generating an electronic control unit log file return instruction according to the name of the initial electronic control unit log file; Sending the electronic control unit log file return instruction to the vehicle electronic control unit; Receive the electronic control unit log file sent by the vehicle electronic control unit.

7. A method for diagnosing abnormality analysis, characterized in that: The method is applied to a vehicle electronic control unit, and the method comprises: Receiving a diagnostic process record request sent by a diagnostic device; Creating an initial ECU log file according to the diagnostic process record request; Receiving the diagnosis start time and vehicle diagnosis instruction sent by the diagnostic device; Execute vehicle diagnosis according to the vehicle diagnosis instruction to obtain vehicle-side execution information; Writing the vehicle-side execution information, the diagnosis start time and the vehicle diagnosis command into the initial ECU log file to obtain an ECU log file; The electronic control unit log file is sent to the diagnostic device so that the diagnostic device can perform diagnostic abnormality analysis.

8. A diagnostic abnormality analysis device, characterized in that: The device comprises: A first generating module, configured to obtain pre-generated diagnostic abnormality process data in response to a diagnostic abnormality analysis instruction, and generate a diagnostic process record request; A second generating module, configured to generate a diagnostic device log file according to the diagnostic process record request and the diagnostic abnormality process data, and obtain an electronic control unit log file generated by the vehicle electronic control unit; The comparison and analysis module is used to perform comparison and analysis based on the electronic control unit log file and the diagnostic device log file to obtain a diagnostic abnormality analysis result.

9. A diagnostic abnormality analysis device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the diagnostic abnormality analysis method according to any one of claims 1 to 7.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the diagnostic abnormality analysis method according to any one of claims 1 to 7 are implemented.

Citation Information

Patent Citations

  • Vehicle communications

    CN109388123A

  • Remote diagnosis system and method, electronic equipment and storage medium

    CN115903758A

  • Real-time online fault monitoring method and related system

    CN117193253A

  • Diagnostic program execution system and log information display system to be used for the execution system

    JP1993143395A

  • Apparatus, log recording control method, and program

    JP2010134705A

Cited By

  • Abnormal positioning method and device for diagnostic equipment, equipment and storage medium

    CN119575955A

  • A method, device and storage medium for diagnosing and locating equipment abnormalities

    CN119575955B