Diagnostic anomaly analysis method, apparatus, device, and computer program product

Abstract

This application discloses a diagnostic anomaly analysis method, apparatus, device, and computer program product, relating to the field of vehicle diagnostic technology. The diagnostic anomaly analysis method includes: responding to a diagnostic anomaly analysis command, acquiring pre-generated diagnostic anomaly process data, and generating a diagnostic process record request; generating a diagnostic equipment log file based on the diagnostic process record request and the diagnostic anomaly process data, and acquiring an electronic control unit (ECU) log file generated by the vehicle's electronic control unit; and comparing and analyzing the ECU log file and the diagnostic equipment log file to obtain a diagnostic anomaly analysis result. This application, by comparing and analyzing the ECU log file and the diagnostic equipment log file, can simultaneously compare diagnostic and debugging information from both the diagnostic equipment and the vehicle's electronic control unit, directly locating the anomaly problem. This solves the problem of low efficiency in existing vehicle diagnostic anomaly analysis technologies and significantly improves the efficiency of vehicle diagnostic anomaly analysis.

Description

Technical Field

[0001] This application relates to the field of vehicle diagnostic technology, and in particular to a diagnostic anomaly analysis method, apparatus, equipment, and computer program product. Background Technology

[0002] As vehicle functions become increasingly complex, the diagnostic functions supported by vehicle electronic control units (ECUs) are also expanding. During the development of vehicle diagnostic functions or after-sales fault diagnosis, errors frequently occur when using diagnostic equipment to perform diagnostic functions on the vehicle ECUs. In such cases, it is necessary to identify the source of the problem. Currently, diagnostic equipment logs request and response messages when communicating with the vehicle ECU to perform diagnostic functions. While these logs can be used to analyze the cause, relying solely on these logs is insufficient to truly pinpoint the anomaly, resulting in low efficiency in diagnostic anomaly analysis.

[0003] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main objective of this application is to provide a diagnostic anomaly analysis method, apparatus, equipment, and computer program product, which aims to solve the technical problem of low efficiency in vehicle diagnostic anomaly analysis.

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

[0006] In response to a diagnostic anomaly analysis command, retrieve pre-generated diagnostic anomaly process data and generate a diagnostic process record request;

[0007] Based on the diagnostic process record request and diagnostic anomaly process data, generate a diagnostic equipment log file and obtain the electronic control unit log file generated by the vehicle electronic control unit;

[0008] The diagnostic anomaly analysis results are obtained by comparing and analyzing the electronic control unit log file and the diagnostic equipment log file.

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

[0010] When a vehicle diagnostic error is detected, the diagnostic anomaly process data is generated based on the current vehicle diagnostic process data and the vehicle diagnostic error information, and the diagnostic anomaly analysis instruction is triggered.

[0011] In one embodiment, the steps of generating a diagnostic equipment log file based on the diagnostic process record request and diagnostic anomaly process data, and obtaining the electronic control unit log file generated by the vehicle electronic control unit, include:

[0012] The diagnostic process record request is sent to the vehicle electronic control unit;

[0013] Based on the diagnostic anomaly process data, the vehicle is diagnosed, and the log information of the diagnostic device is recorded according to the diagnostic process record request, generating the diagnostic device log file;

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

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

[0016] Based on the diagnostic process record request, create an initial diagnostic device log file;

[0017] The diagnostic anomaly process data is analyzed to obtain the set of diagnostic functions to be executed and the execution order data of the diagnostic functions;

[0018] According to the diagnostic function execution order data, vehicle diagnosis is performed sequentially based on the diagnostic function data to be executed in the set of diagnostic functions to be executed, generating device-side execution information and vehicle diagnostic instructions, and sending the vehicle diagnostic instructions to the vehicle electronic control unit;

[0019] Receive vehicle diagnostic command responses sent by the vehicle electronic control unit;

[0020] The device execution information, vehicle diagnostic command 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, before the step of performing vehicle diagnostics sequentially according to the diagnostic function execution order data and the diagnostic function data to be executed in the set of diagnostic function data 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 method further includes:

[0022] Receive the name of the initial electronic control unit log file sent by the vehicle electronic control unit, wherein the name of the initial electronic control unit log file is the same as the electronic control unit log file, and record the current time as the diagnostic start time;

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

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

[0025] Based on the name of the initial electronic control unit log file, generate an electronic control unit log file return instruction;

[0026] The command to send the electronic control unit log file back to the vehicle electronic control unit is sent.

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

[0028] Furthermore, to achieve the above objectives, this application also proposes a diagnostic anomaly analysis method, which is applied to a vehicle electronic control unit, and the method includes:

[0029] Receive diagnostic process record requests sent by diagnostic equipment;

[0030] Based on the diagnostic process record request, an initial electronic control unit log file is created;

[0031] Receive the diagnostic start time and vehicle diagnostic command sent by the diagnostic device;

[0032] Perform vehicle diagnostics according to the vehicle diagnostic instructions to obtain vehicle-side execution information;

[0033] The vehicle-side execution information, diagnostic start time, and vehicle diagnostic instructions are written into the initial electronic control unit log file to obtain the electronic control unit log file.

[0034] The electronic control unit log file is sent to the diagnostic device for the diagnostic device to perform diagnostic anomaly analysis.

[0035] Furthermore, to achieve the above objectives, this application also proposes a diagnostic anomaly analysis device, which includes:

[0036] The first generation module is used to respond to the diagnostic anomaly analysis command, obtain pre-generated diagnostic anomaly process data, and generate a diagnostic process record request.

[0037] The second generation module is used to generate a diagnostic equipment log file based on the diagnostic process record request and diagnostic anomaly process data, and to obtain the electronic control unit log file generated by the vehicle electronic control unit.

[0038] The comparison and analysis module is used to perform comparative analysis based on the electronic control unit log file and the diagnostic equipment log file to obtain diagnostic anomaly analysis results.

[0039] In addition, to achieve the above objectives, this application also proposes a diagnostic anomaly analysis device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the diagnostic anomaly analysis method as described above.

[0040] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the diagnostic anomaly analysis method described above.

[0041] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the diagnostic anomaly analysis method described above.

[0042] This application provides a diagnostic anomaly analysis method. When a vehicle diagnostic anomaly occurs, the electronic control unit (ECU) log file and the diagnostic device log file are obtained based on the diagnostic process record request and diagnostic anomaly process data. By comparing and analyzing the ECU log file and the diagnostic device log file, the diagnostic debugging information at both ends of the diagnostic device and the vehicle's electronic control unit can be compared simultaneously, directly locating the anomaly. This solves the problem of low efficiency in vehicle diagnostic anomaly analysis in the prior art and significantly improves the efficiency of vehicle diagnostic anomaly analysis. Attached Figure Description

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

[0044] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a flowchart illustrating an embodiment of the diagnostic anomaly analysis method of this application.

[0046] Figure 2 This is a flowchart illustrating Embodiment 2 of the diagnostic anomaly analysis method of this application;

[0047] Figure 3This is a flowchart illustrating Embodiment 3 of the diagnostic anomaly analysis method of this application;

[0048] Figure 4 This is a schematic diagram of the module structure of the diagnostic anomaly analysis device according to an embodiment of this application;

[0049] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the diagnostic anomaly analysis method in this application embodiment.

[0050] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0051] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0052] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0053] The main solution in this application embodiment is:

[0054] In response to a diagnostic anomaly analysis command, retrieve pre-generated diagnostic anomaly process data and generate a diagnostic process record request;

[0055] Based on the diagnostic process record request and diagnostic anomaly process data, generate a diagnostic equipment log file and obtain the electronic control unit log file generated by the vehicle electronic control unit;

[0056] The diagnostic anomaly analysis results are obtained by comparing and analyzing the electronic control unit log file and the diagnostic equipment log file.

[0057] Because in the existing technology, the request and response message logs of diagnostic equipment are only recorded by the diagnostic equipment and do not include the ECU's logs, such as whether the ECU did not receive the request or received it but did not process it, it is impossible to directly locate the abnormal problem, resulting in low efficiency of vehicle diagnostic anomaly analysis.

[0058] This application provides a solution that, when a vehicle diagnostic anomaly occurs, obtains the electronic control unit (ECU) log file and the diagnostic device log file based on the diagnostic process record request and diagnostic anomaly process data. By comparing and analyzing the ECU log file and the diagnostic device log file, the diagnostic debugging information at both ends of the diagnostic device and the vehicle's electronic control unit can be compared simultaneously, directly locating the anomaly. This solves the problem of low efficiency in vehicle diagnostic anomaly analysis in the prior art and significantly improves the efficiency of vehicle diagnostic anomaly analysis.

[0059] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device or diagnostic anomaly analysis system capable of performing the above functions. The following description uses a diagnostic anomaly analysis system as an example to illustrate this embodiment and the subsequent embodiments, wherein the diagnostic anomaly analysis system includes diagnostic equipment and a vehicle electronic control unit.

[0060] Based on this, embodiments of this application provide a diagnostic anomaly analysis method, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the diagnostic anomaly analysis method of this application.

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

[0062] Step S01: In response to the diagnostic anomaly analysis command, obtain the pre-generated diagnostic anomaly process data and generate a diagnostic process record request;

[0063] In response to a diagnostic anomaly analysis command, the diagnostic device acquires pre-generated diagnostic anomaly process data and generates a diagnostic process record request.

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

[0065] In one possible implementation, step S04 may be included before step S01:

[0066] Step S04: When a vehicle diagnostic error message is detected, the diagnostic anomaly process data is generated based on the current vehicle diagnostic process data and the vehicle diagnostic error message, and the diagnostic anomaly analysis instruction is triggered.

[0067] When a vehicle diagnostic error is detected, the diagnostic equipment generates diagnostic anomaly process data based on the current vehicle diagnostic process data and the vehicle diagnostic error information, and triggers a diagnostic anomaly analysis command.

[0068] In this embodiment, when a vehicle diagnostic error is detected, the system generates diagnostic anomaly process data based on the current vehicle diagnostic process data and the vehicle diagnostic error, and triggers the diagnostic anomaly analysis command. This ensures that when a vehicle diagnostic error is detected, the system can promptly generate the corresponding anomaly process data and automatically initiate the relevant diagnostic anomaly analysis process to quickly respond to and locate possible diagnostic anomalies.

[0069] Step S02: Based on the diagnostic process record request and diagnostic anomaly process data, generate a diagnostic equipment log file and obtain the electronic control unit log file generated by the vehicle electronic control unit;

[0070] Step S03: Compare and analyze the electronic control unit log file and the diagnostic device log file to obtain the diagnostic anomaly analysis results.

[0071] The diagnostic equipment sends a diagnostic process recording request to the vehicle's electronic control unit (ECU). The ECU records the subsequent vehicle diagnostic process, resulting in an ECU log file. Simultaneously, the equipment performs vehicle diagnostics based on the diagnostic process recording request and diagnostic anomaly data, recording the results to obtain a diagnostic equipment log file. The ECU log file and the diagnostic equipment log file are then compared and analyzed to obtain diagnostic anomaly analysis results.

[0072] This embodiment provides a diagnostic anomaly analysis method. When a vehicle diagnostic anomaly occurs, the electronic control unit (ECU) log file and the diagnostic device log file are obtained based on the diagnostic process record request and diagnostic anomaly process data. By comparing and analyzing the ECU log file and the diagnostic device log file, the diagnostic debugging information at both ends of the diagnostic device and the vehicle's electronic control unit can be compared simultaneously, directly locating the anomaly. This solves the problem of low efficiency in vehicle diagnostic anomaly analysis in the prior art and significantly improves the efficiency of vehicle diagnostic anomaly analysis.

[0073] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 Step S02 may also include steps S021 to S023:

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

[0075] Step S022: Based on the diagnostic anomaly process data, diagnose the vehicle and record the log information of the diagnostic device according to the diagnostic process record request, and generate the diagnostic device log file;

[0076] Step S023: Obtain the electronic control unit log file generated by the vehicle electronic control unit.

[0077] The diagnostic equipment first sends a diagnostic process recording request to the vehicle's electronic control unit (ECU), typically via the vehicle's internal data bus or a dedicated communication protocol, ensuring the request is accurately and promptly received and executed. The diagnostic process recording request usually includes specific data and information types to be recorded, ensuring coverage of all critical aspects required for diagnosis. Then, based on the diagnostic anomaly process data, the system determines how to diagnose the vehicle. This data may include fault codes, abnormal sensor data states, and the response speed of system components. During the diagnostic process, the diagnostic equipment's log information is recorded synchronously, generating a diagnostic equipment log file. This log file can include timestamps of each step of the diagnostic process accurate to milliseconds, descriptions of the executed diagnostic functions (reading fault codes, writing configurations, etc.), the system IDs of the communicating ECUs (request and response IDs), and information on sent and received diagnostic data. Finally, the system obtains the electronic control unit (ECU) log file generated by the ECU based on the received diagnostic process recording request. This file can include information such as the diagnostic data received by the ECU, the reception time, internal processing procedures, and the sent diagnostic data and transmission time.

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

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

[0080] Step S0222: Parse the diagnostic anomaly process data to obtain the data set of diagnostic functions to be executed and the execution order data of diagnostic functions;

[0081] Step S0223: According to the diagnostic function execution order data, perform vehicle diagnosis sequentially based on the diagnostic function data to be executed in the set of diagnostic function data 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: Receive the vehicle diagnostic command response sent by the vehicle electronic control unit;

[0083] Step S0225: Write the device execution information, vehicle diagnostic command 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 equipment first creates an initial diagnostic equipment log file based on the diagnostic process record request. Then, it parses the diagnostic anomaly process data to obtain a set of diagnostic function data to be executed and a data sequence for the execution order of diagnostic functions. These data are crucial steps in the vehicle diagnostic process, ensuring that diagnostic functions are executed in the correct order and relevant data is collected. Next, according to the diagnostic function execution order data, the equipment retrieves data for each diagnostic function to be executed from the set of data in a predetermined order. This data typically includes the name of the diagnostic function, parameter settings, execution conditions, etc. Based on each diagnostic function data to be executed, the equipment generates corresponding vehicle diagnostic instructions. These instructions are operation commands for the vehicle's electronic control unit (ECU) to execute specific diagnostic functions, such as reading sensor data or executing self-test programs. Simultaneously, based on the set of diagnostic function data to be executed, the equipment prepares execution information, which may include the start time of the diagnostic task, equipment identification, and log records of the executed operations. Finally, the equipment sends the vehicle diagnostic instructions to the ECU. The sub-control unit then receives vehicle diagnostic command responses from the vehicle electronic control unit. These responses can include a timestamp, specific content, any diagnostic results, or status information. Finally, the device opens or accesses an existing initial diagnostic device log file and writes the pre-generated diagnostic start time into the log file. This timestamp marks the start of the diagnostic process, aiding in subsequent analysis and timeline tracking. For each executed diagnostic function, relevant device-side execution information is recorded, including the name of the diagnostic function, execution start time, relevant device identifiers or other identifiers, and log entries during execution. For each received vehicle diagnostic command response, relevant information is recorded, which may include the timestamp of the response, specific response content, whether the response was successfully received, execution results, or status information. After traversing all pending diagnostic function data sets, the diagnostic device log file is obtained and closed, ensuring that all recording operations are completed and the file content is preserved intact.

[0085] It should be noted that the diagnostic functions to be performed may depend on the specific problems of the vehicle or the predetermined diagnostic process, such as performing specific sensor detections, electronic control unit self-tests, etc. The execution order of diagnostic functions can be sorted and determined based on the diagnostic function execution order data.

[0086] In this embodiment, the vehicle is diagnosed based on the diagnostic anomaly process data, and the diagnostic equipment log information during the diagnostic process is recorded according to the diagnostic process record request, generating a diagnostic equipment log file. This ensures that the diagnostic equipment can record and manage various key data and events during the diagnostic process, providing necessary support and basis for subsequent analysis and problem solving.

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

[0088] Step S02261: Receive the name of the initial electronic control unit log file sent by the vehicle electronic control unit, wherein the name of the initial electronic control unit log file is the same as the electronic control unit log file, and record the current time as the diagnostic start time;

[0089] Step S02262: The diagnostic start time is sent to the vehicle electronic control unit so that the start time recorded in the electronic control unit log file and the diagnostic device log file is synchronized.

[0090] The diagnostic device receives the name of the initial ECU log file from the vehicle's electronic control unit (ECU). This name is the same as the actual log file recorded by the ECU in the vehicle; it may be a filename or an identifier used to identify a specific ECU log. Upon receiving the log file name, the device immediately records the current time as the diagnostic start time. This time point will be used as the start time of the diagnostic process for subsequent timestamps and time recording in the log file. Finally, the diagnostic start time is sent to the ECU. After receiving the diagnostic start time, the ECU confirms that time synchronization has been successfully completed. This means that the time base recorded by the ECU and the device is the same. From this time point, both begin recording diagnostic-related log information.

[0091] In this embodiment, the name of the initial ECU log file sent by the vehicle's electronic control unit (ECU) is received. The name of the initial ECU log file is the same as the ECU log file, and the current time is recorded as the diagnostic start time. This diagnostic start time is then sent to the vehicle ECU to synchronize the start times recorded in the ECU log file and the diagnostic device log file. This ensures that the preparation work 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 begins. This is crucial for timeline management and data analysis during subsequent diagnostic processes.

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

[0093] Step S0231: Generate an electronic control unit log file return instruction based on the name of the initial electronic control unit log file;

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

[0095] Step S0233: Receive the electronic control unit log file sent by the vehicle electronic control unit.

[0096] The diagnostic equipment generates an electronic control unit (ECU) log file return instruction based on the name of the initial ECU log file. This instruction is used to instruct the vehicle's electronic control unit (ECU) to send the specific log file back to the diagnostic equipment. The diagnostic equipment then sends the ECU log file return instruction to the ECU and finally receives the ECU log file sent by the ECU.

[0097] It should be noted that the electronic control unit log file return instruction may include information such as the name or identifier of the log file, a request instructing the electronic control unit to send the log file to the diagnostic equipment, and the timestamp or time range requested for sending (if a specific time period of log is required).

[0098] In this embodiment, an electronic control unit log file return instruction is generated based on 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's electronic control unit is acquired and saved during the diagnostic process for subsequent analysis or troubleshooting. In this way, the device can obtain real-time or historical electronic control unit operation data to help diagnose potential vehicle problems or optimize its performance.

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

[0100] Furthermore, embodiments of this application provide a diagnostic anomaly analysis method, referring to... Figure 3 , Figure 3 This is a flowchart illustrating the third embodiment of the diagnostic anomaly analysis method of this application.

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

[0102] Step S05: Receive a diagnostic process record request sent by the diagnostic device;

[0103] Step S06: Create an initial electronic control unit log file according to the diagnostic process record request;

[0104] Step S07: Receive the diagnostic start time and vehicle diagnostic command sent by the diagnostic device;

[0105] Step S08: Perform vehicle diagnostics according to the vehicle diagnostic command to obtain vehicle-side execution information;

[0106] Step S09: Write the vehicle-side execution information, diagnostic start time, and vehicle diagnostic instructions into the initial electronic control unit log file to obtain the electronic control unit log file;

[0107] Step S10: Send the electronic control unit log file to the diagnostic device for the diagnostic device to perform diagnostic anomaly analysis.

[0108] It should be noted that the Electronic Control Unit (ECU) is also known as the "vehicle computer" of a car. Its purpose is to control the driving status of the car and realize its various functions. It mainly uses data acquisition and exchange from various sensors and buses to determine the vehicle status and the driver's intentions, and controls the car through actuators. Current vehicles are equipped with multiple ECUs, such as the engine ECU, transmission ECU, etc.

[0109] When diagnostic equipment needs to perform diagnostic anomaly analysis, the vehicle's electronic control unit (ECU) receives a diagnostic process recording request from the diagnostic equipment. Based on this request, it begins creating an initial ECU log file. This file records important information during the subsequent diagnostic process. Then, it receives the diagnostic start time and vehicle diagnostic commands from the diagnostic equipment. Following these commands, it executes corresponding vehicle diagnostic operations, which may include reading sensor data and performing specific control operations to obtain vehicle-side execution information. During the diagnostic process, the ECU writes the obtained vehicle-side execution information, diagnostic start time, and vehicle diagnostic commands into the previously created initial ECU log file. This process records key information from the entire diagnostic process, resulting in the ECU log file. Finally, after the vehicle diagnostic is complete, the ECU sends this file to the diagnostic equipment. The diagnostic equipment uses these log files for diagnostic anomaly analysis to determine if any abnormalities occurred during the diagnostic process and how to resolve them.

[0110] For example, in one implementation, recording is not required under normal diagnostic conditions, and execution information is not recorded by default. If an anomaly is detected during vehicle diagnostics, it is necessary to record the execution information at both ends of the diagnostic device and the vehicle ECU throughout the entire diagnostic process. When recording execution information is required, the information recording function at both ends of the diagnostic device and the ECU needs to be activated before vehicle diagnostics. Therefore, the process of realizing diagnostic anomaly analysis through the interaction between the diagnostic device and the vehicle electronic control unit is as follows:

[0111] 1. First, activate the diagnostic device's information logging function and create a new information logging log file F1. Enable the information logging flag. Once enabled, the diagnostic device will write information for each step of each diagnostic function to the information logging log file. The contents written to the information logging log file by the diagnostic device include: timestamps of each step execution accurate to milliseconds, descriptions of the executed diagnostic functions (reading fault codes, writing configurations, etc.), the system IDs (request and response IDs) of the communicating ECUs, and the sent and received diagnostic data.

[0112] 2. Then the diagnostic equipment sends a command to the ECU to be diagnosed to activate the ECU's information recording function. The ECU will also create an ECU log file F2 to record information such as the diagnostic data received by the ECU, the receiving time, the internal processing process, the diagnostic data sent and the sending time.

[0113] 3. After the ECU successfully creates the log file, it will send the log file name back to the diagnostic equipment for reading after the diagnostic is completed.

[0114] 4. After receiving the log file name from the ECU, the diagnostic device will send its current time to the ECU for synchronization, ensuring that the time of the information recorded on the diagnostic device and the ECU is synchronized, so as to facilitate the comparison and analysis of the two log files after the diagnosis is completed.

[0115] 5. Once the diagnostic equipment and ECU's information recording functions are successfully activated, the diagnostic equipment can be used to diagnose the vehicle. Select and execute diagnostic functions on the diagnostic equipment, such as reading fault codes, firmware flashing, configuration code writing, data stream reading, etc. The diagnostic equipment will write the execution information to F1 in real time, and the ECU will record the information to F2.

[0116] 6. After the diagnostic is complete, the diagnostic equipment sends a command to the ECU to return the ECU log file, which includes the ECU log file name. The ECU will then send the file with this name back to the diagnostic equipment via F2.

[0117] 7. Then the diagnostic equipment displays the log information from both the diagnostic equipment end and the ECU end. By comparing the information records at both ends according to the timeline, the cause of the error can be quickly located.

[0118] 8. After the analysis is complete, 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 the F2 file to free up storage space.

[0119] In this embodiment, when a diagnostic anomaly is encountered, the diagnostic device initiates diagnostic debugging information recording and also sends a command to the ECU to initiate ECU diagnostic debugging information recording, synchronizing the recording time. The ECU's diagnostic debugging information is recorded and stored internally as a debugging file. After the diagnostic function is completed, the diagnostic device sends a command to read the debugging file from the ECU. Therefore, it is possible to simultaneously compare the diagnostic debugging information from both the diagnostic device and the vehicle's electronic control unit, directly pinpointing the anomaly and improving the efficiency of vehicle diagnostic anomaly analysis.

[0120] In this embodiment, the vehicle electronic control unit (ECU) generates an ECU log file based on the received diagnostic process record request, diagnostic start time, and vehicle diagnostic instructions, and sends it to the diagnostic device. By comparing and analyzing the ECU log file and the diagnostic device log file, the diagnostic device can simultaneously compare diagnostic and debugging information from both ends of the diagnostic device and the vehicle ECU, directly locating the anomaly. This solves the problem of low efficiency in vehicle diagnostic anomaly analysis in existing technologies and significantly improves the efficiency of vehicle diagnostic anomaly analysis.

[0121] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the diagnostic anomaly analysis method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0122] This application also provides a diagnostic anomaly analysis device; please refer to [reference needed]. Figure 4 The diagnostic anomaly analysis device includes:

[0123] The first generation module 10 is used to respond to the diagnostic anomaly analysis command, obtain pre-generated diagnostic anomaly process data, and generate a diagnostic process record request.

[0124] The second generation module 20 is used to generate a diagnostic equipment log file based on the diagnostic process record request and diagnostic anomaly process data, and to obtain the electronic control unit log file generated by the vehicle electronic control unit.

[0125] The comparison and analysis module 30 is used to perform a comparison and analysis based on the electronic control unit log file and the diagnostic equipment log file to obtain the diagnostic anomaly analysis results.

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

[0127] When a vehicle diagnostic error is detected, the diagnostic anomaly process data is generated based on the current vehicle diagnostic process data and the vehicle diagnostic error information, and the diagnostic anomaly analysis instruction is triggered.

[0128] Optionally, the second generation module 20 is further configured to:

[0129] The diagnostic process record request is sent to the vehicle electronic control unit;

[0130] Based on the diagnostic anomaly process data, the vehicle is diagnosed, and the log information of the diagnostic device is recorded according to the diagnostic process record request, generating the diagnostic device log file;

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

[0132] Optionally, the step of diagnosing the vehicle based on the diagnostic anomaly process data, and recording the diagnostic device's log information according to the diagnostic process record request, and generating the diagnostic device log file includes:

[0133] Based on the diagnostic process record request, create an initial diagnostic device log file;

[0134] The diagnostic anomaly process data is analyzed to obtain the set of diagnostic functions to be executed and the execution order data of the diagnostic functions;

[0135] According to the diagnostic function execution order data, vehicle diagnosis is performed sequentially based on the diagnostic function data to be executed in the set of diagnostic functions to be executed, generating device-side execution information and vehicle diagnostic instructions, and sending the vehicle diagnostic instructions to the vehicle electronic control unit;

[0136] Receive vehicle diagnostic command responses sent by the vehicle electronic control unit;

[0137] The device execution information, vehicle diagnostic command 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 diagnostics sequentially according to the diagnostic function execution order data and the diagnostic function data to be executed in the set of diagnostic functions 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 method further includes:

[0139] Receive the name of the initial electronic control unit log file sent by the vehicle electronic control unit, wherein the name of the initial electronic control unit log file is the same as the electronic control unit log file, and record the current time as the diagnostic start time;

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

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

[0142] Based on the name of the initial electronic control unit log file, generate an electronic control unit log file return instruction;

[0143] The command to send the electronic control unit log file back to the vehicle electronic control unit is sent.

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

[0145] The diagnostic anomaly analysis device provided in this application, employing the diagnostic anomaly analysis method in the above embodiments, can solve the technical problem of low efficiency in vehicle diagnostic anomaly analysis. Compared with the prior art, the beneficial effects of the diagnostic anomaly analysis device provided in this application are the same as those of the diagnostic anomaly analysis method provided in the above embodiments, and other technical features in the diagnostic anomaly analysis device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0146] This 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 to enable the at least one processor to perform the diagnostic anomaly analysis method in Embodiment 1 above.

[0147] The following is for reference. Figure 5 The diagram illustrates a structural schematic suitable for implementing the diagnostic anomaly analysis device of the embodiments of this application. The diagnostic anomaly analysis device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Detection), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The diagnostic anomaly analysis device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0148] like Figure 5As shown, the diagnostic anomaly analysis device may include a processing unit 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) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the diagnostic anomaly analysis device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the diagnostic anomaly analysis device to communicate wirelessly or wiredly with other devices to exchange data. Although a diagnostic anomaly analysis device with various systems is shown in the figure, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems may be implemented alternatively.

[0149] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

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

[0151] It should be understood that the various parts disclosed in this application can be implemented using 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 suitable manner in one or more embodiments or examples.

[0152] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0153] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the diagnostic anomaly analysis method in the above embodiments.

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

[0155] The aforementioned computer-readable storage medium may be included in the diagnostic anomaly analysis device; or it may exist independently and not assembled into the diagnostic anomaly analysis device.

[0156] The aforementioned computer-readable storage medium carries one or more programs that, when executed by the diagnostic anomaly analysis device, cause the diagnostic anomaly analysis device to:

[0157] In response to a diagnostic anomaly analysis command, retrieve pre-generated diagnostic anomaly process data and generate a diagnostic process record request;

[0158] Based on the diagnostic process record request and diagnostic anomaly process data, generate a diagnostic equipment log file and obtain the electronic control unit log file generated by the vehicle electronic control unit;

[0159] The diagnostic anomaly analysis results are obtained by comparing and analyzing the electronic control unit log file and the diagnostic equipment log file.

[0160] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—and conventional procedural programming languages—such as the "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 a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via 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., via the Internet using an Internet service provider).

[0161] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0162] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0163] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described diagnostic anomaly analysis method, thereby solving the technical problem of low efficiency in vehicle diagnostic anomaly analysis. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the diagnostic anomaly analysis method provided in the above embodiments, and will not be repeated here.

[0164] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the diagnostic anomaly analysis method described above.

[0165] The computer program product provided in this application can solve the technical problem of low efficiency in vehicle diagnostic anomaly analysis. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the diagnostic anomaly analysis method provided in the above embodiments, and will not be repeated here.

[0166] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A diagnostic abnormality analysis method characterized by comprising: The method is applied to a diagnostic device, and the method comprises: In response to a diagnostic exception analysis instruction, pre-generated diagnostic exception process data is acquired, and a diagnostic process record request is generated; According to the diagnostic process record request and the diagnostic exception process data, a diagnostic device log file is generated, and an electronic control unit log file generated by a vehicle electronic control unit is acquired; According to the electronic control unit log file and the diagnostic device log file, comparative analysis is performed to obtain a diagnostic exception analysis result; The step of generating the diagnostic device log file according to the diagnostic process record request and the diagnostic exception process data, and acquiring the electronic control unit log file generated by the vehicle electronic control unit comprises: The diagnostic process record request is sent to the vehicle electronic control unit; The vehicle is diagnosed according to the diagnostic exception process data, and log information of the diagnostic device is recorded according to the diagnostic process record request to generate the diagnostic device log file; The electronic control unit log file generated by the vehicle electronic control unit is acquired; The step of diagnosing the vehicle according to the diagnostic exception process data and recording log information of the diagnostic device according to the diagnostic process record request to generate the diagnostic device log file comprises: An initial diagnostic device log file is created according to the diagnostic process record request; The diagnostic exception process data is parsed to obtain a set of to-be-executed diagnostic function data and diagnostic function execution sequence data; The vehicle is diagnosed according to the to-be-executed diagnostic function data in the set of to-be-executed diagnostic function data in sequence according to the diagnostic function execution sequence data, device-side execution information and vehicle diagnosis instructions are generated, and the vehicle diagnosis instructions are sent to the vehicle electronic control unit; Vehicle diagnosis instruction replies sent by the vehicle electronic control unit are received; The device-side execution information, the vehicle diagnosis instruction replies and a pre-generated diagnostic start time are written into the initial diagnostic device log file until the set of to-be-executed diagnostic function data is traversed, and the diagnostic device log file is obtained.

2. The method of claim 1, wherein, The step of acquiring pre-generated diagnostic exception process data and generating a diagnostic process record request in response to a diagnostic exception analysis instruction further comprises: When vehicle diagnostic error information is detected, the diagnostic exception process data is generated according to current vehicle diagnostic process data and the vehicle diagnostic error information, and the diagnostic exception analysis instruction is triggered.

3. The method of claim 1, wherein, The step of diagnosing the vehicle according to the to-be-executed diagnostic function data in the set of to-be-executed diagnostic function data in sequence according to the diagnostic function execution sequence data, generating device-side execution information and vehicle diagnosis instructions, and sending the vehicle diagnosis instructions to the vehicle electronic control unit further comprises: The name of an initial electronic control unit log file sent by the vehicle electronic control unit is received, wherein the name of the initial electronic control unit log file is the same as that of the electronic control unit log file, and the current time is recorded as the diagnostic start time; sending the diagnosis start time to the vehicle electronic control unit to synchronize the start time recorded by the electronic control unit log file and the diagnosis equipment log file.

4. The method of claim 3, wherein, 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; receiving the electronic control unit log file sent by the vehicle electronic control unit.

5. A diagnostic abnormality analysis method characterized by comprising: The method is applied to a vehicle electronic control unit, and the method comprises: receiving a diagnosis process record request sent by a diagnosis equipment; creating an initial electronic control unit log file according to the diagnosis process record request; receiving a diagnosis start time and a vehicle diagnosis instruction sent by the diagnosis equipment; obtaining vehicle-side execution information by performing vehicle diagnosis according to the vehicle diagnosis instruction; writing the vehicle-side execution information, the diagnosis start time and the vehicle diagnosis instruction into the initial electronic control unit log file to obtain an electronic control unit log file; sending the electronic control unit log file to the diagnosis equipment, so that the diagnosis equipment performs diagnosis abnormality analysis according to the electronic control unit log file and a diagnosis equipment log file, wherein the diagnosis equipment diagnoses a vehicle according to diagnosis abnormality process data, and generates the diagnosis equipment log file by recording log information of the diagnosis equipment according to a diagnosis process request; The step of diagnosing a vehicle according to diagnosis abnormality process data by the diagnosis equipment, and generating a diagnosis equipment log file by recording log information of the diagnosis equipment according to a diagnosis process request comprises: creating an initial diagnosis equipment log file according to the diagnosis process record request by the diagnosis equipment; obtaining a to-be-executed diagnosis function data set and diagnosis function execution sequence data by analyzing the diagnosis abnormality process data; performing vehicle diagnosis according to to-be-executed diagnosis function data in the to-be-executed diagnosis function data set in sequence according to the diagnosis function execution sequence data, generating equipment-side execution information and a vehicle diagnosis instruction, and sending the vehicle diagnosis instruction to the vehicle electronic control unit; receiving a vehicle diagnosis instruction reply sent by the vehicle electronic control unit; writing the equipment-side execution information, the vehicle diagnosis instruction reply and the pre-generated diagnosis start time into the initial diagnosis equipment log file until the to-be-executed diagnosis function data set is traversed, and obtaining the diagnosis equipment log file.

6. An abnormality diagnosis analysis device characterized by comprising: The device comprises: a first generation module configured to obtain pre-generated diagnosis abnormality process data and generate a diagnosis process record request in response to a diagnosis abnormality analysis instruction; a second generation module configured to generate a diagnosis equipment log file according to the diagnosis process record request and the diagnosis abnormality process data, and obtain an electronic control unit log file generated by a vehicle electronic control unit; a comparative analysis module configured to perform comparative analysis according to the electronic control unit log file and the diagnosis equipment log file, and obtain a diagnosis abnormality analysis result. The second generation module is further configured to send the diagnostic procedure record request to the vehicle electronic control unit. According to the diagnostic abnormal procedure data, the vehicle is diagnosed, and log information of the diagnostic device is recorded according to the diagnostic procedure record request to generate the diagnostic device log file. The electronic control unit log file generated by the vehicle electronic control unit is acquired. The second generation module is further configured to create an initial diagnostic device log file according to the diagnostic procedure record request. The diagnostic abnormal procedure data is parsed to obtain a set of to-be-executed diagnostic function data and diagnostic function execution sequence data. According to the diagnostic function execution sequence data, the vehicle is diagnosed according to the to-be-executed diagnostic function data in the set of to-be-executed diagnostic function data in sequence, device-side execution information and vehicle diagnostic instructions are generated, and the vehicle diagnostic instructions are sent to the vehicle electronic control unit. The vehicle diagnostic instruction reply sent by the vehicle electronic control unit is received. The device-side execution information, the vehicle diagnostic instruction reply and the pre-generated diagnostic start time are written into the initial diagnostic device log file until the set of to-be-executed diagnostic function data is traversed, and the diagnostic device log file is obtained.

7. A diagnostic abnormality analysis apparatus characterized by comprising: The device comprises a memory, a processor and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the diagnostic abnormal analysis method according to any one of claims 1 to 5.

8. A computer program product, characterised in that, The computer program product comprises a computer program, and the computer program is executed by the processor to implement the steps of the diagnostic abnormal analysis method according to any one of claims 1 to 5.

Images