Offline diagnostic data analysis method and device

Abstract

The invention relates to an offline diagnostic data analysis method, and the method comprises the following steps: receiving an analysis file which comprises one or more of the following items: a diagnostic request identifier, a diagnostic response identifier, a diagnostic protocol type and diagnostic channel information; based on the diagnosis protocol type, calling a diagnosis analysis function corresponding to the diagnosis protocol type; and receiving off-line diagnosis data, and analyzing the off-line diagnosis data by using the diagnosis analysis function to generate an analysis result.

Description

Technical Field

[0001] This application relates to the field of vehicle communication, and more specifically, to an offline diagnostic data parsing method and apparatus. Background Technology

[0002] With the increasing level of vehicle electronics, the complexity and diversity of vehicle electronic modules have led to a rise in vehicle electronic faults. Traditional application message collection can no longer meet the needs of problem solving, making the collection of diagnostic data from vehicle ECUs increasingly important. Engineers can collect variables not only within the ECU itself through diagnostics. When an ECU malfunctions, the data acquisition module can collect vehicle application messages and diagnostic data at the time of the problem, facilitating problem localization and analysis for engineers and improving problem-solving efficiency.

[0003] On the other hand, since the number of application messages is limited by the bus load, OEMs and suppliers have defined a large number of DID, PID, and Memory diagnostic services in order to locate ECU problems. When an ECU has a problem, sending diagnostic services can collect more information about the ECU at the time of the problem, which helps to locate the problem more efficiently.

[0004] However, current diagnostic tools only support real-time diagnostic data parsing. That is, when an ECU has a problem, engineers can only obtain diagnostic results by connecting the diagnostic tool on-site to send and receive real-time diagnostic data. Furthermore, they do not support the parsing of diagnostic data after it has been merged into memory. Currently, there are no tools that can support the parsing of offline diagnostic data. Summary of the Invention

[0005] The offline diagnostic data parsing method of this application includes the following steps: receiving a parsing file, wherein the parsing file includes one or more of the following: diagnostic request identifier, diagnostic response identifier, diagnostic protocol type, and diagnostic channel information; based on the diagnostic protocol type, calling a diagnostic parsing function corresponding to the diagnostic protocol type; receiving offline diagnostic data, and using the diagnostic parsing function to parse the offline diagnostic data to generate a parsing result.

[0006] Optionally, the method further includes writing the parsing result into an output result file.

[0007] Optionally, parsing the offline diagnostic data using the diagnostic parsing function further includes determining one or more of the following: data packaging order, parsing rules for multiple data identifiers, and memory address merging rules.

[0008] Optionally, the diagnostic protocol type includes one or more of the following: UDS protocol and GMLAN protocol.

[0009] Optionally, when the diagnostic protocol type is UDS protocol, the diagnostic parsing function includes one or more of the following: 0x2A parsing function, 0x22 parsing function, and 0x23 parsing function.

[0010] Optionally, when the diagnostic protocol type is GMLAN protocol, the diagnostic parsing function includes one or more of the following: 0xAA parsing function, 0x22 parsing function, 0x1A parsing function, and 0x23 parsing function.

[0011] The offline diagnostic data parsing device of this application includes: a file import module configured to receive a parsing file, wherein the parsing file includes one or more of the following: a diagnostic request identifier, a diagnostic response identifier, a diagnostic protocol type, and diagnostic channel information; a function call module configured to call a diagnostic parsing function corresponding to the diagnostic protocol type based on the diagnostic protocol type; and a data parsing module configured to receive offline diagnostic data and parse the offline diagnostic data using the diagnostic parsing function to generate a parsing result.

[0012] Optionally, the apparatus further includes a result output module configured to write the parsing result to an output result file.

[0013] Optionally, the data parsing module is further configured to determine one or more of the following: data packaging order, parsing rules for multiple data identifiers, and merging rules for memory addresses.

[0014] Optionally, the diagnostic protocol type includes one or more of the following: UDS protocol and GMLAN protocol.

[0015] Optionally, when the diagnostic protocol type is UDS protocol, the diagnostic parsing function includes one or more of the following: 0x2A parsing function, 0x22 parsing function, and 0x23 parsing function.

[0016] Optionally, when the diagnostic protocol type is GMLAN protocol, the diagnostic parsing function includes one or more of the following: 0xAA parsing function, 0x22 parsing function, 0x1A parsing function, and 0x23 parsing function.

[0017] The computer-readable storage medium of this application stores a computer program thereon, which, when executed by a processor, implements the above-described offline diagnostic data parsing method.

[0018] The computer device of this application includes a storage module, a processor, and a computer program stored on the storage module and executable on the processor. When the processor executes the computer program, it implements the above-described offline diagnostic data parsing method. Attached Figure Description

[0019] The above and / or other aspects and advantages of this application will become clearer and more readily understood from the following description taken in conjunction with the accompanying drawings, in which the same or similar elements are denoted by the same reference numerals. In the drawings: Figure 1 A schematic flowchart of an offline diagnostic data parsing method 100 according to an embodiment of this application is shown; and Figure 2 A schematic block diagram of an offline diagnostic data parsing apparatus 200 according to an embodiment of this application is shown. Detailed Implementation

[0020] The following detailed description is merely exemplary in nature and is not intended to limit the disclosed technology or its application and use. Furthermore, it is not intended to be bound by any express or implied theory presented in the foregoing technical fields, background art, or the following detailed description.

[0021] In the following detailed description of the embodiments, numerous specific details are set forth in order to provide a more thorough understanding of the disclosed technology. However, it will be apparent to those skilled in the art that the disclosed technology can be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.

[0022] Terms such as “comprising” and “including” indicate that, in addition to the units and steps that are directly and explicitly stated in the specification, the technical solution of this application does not exclude the presence of other units and steps that are not directly or explicitly stated.

[0023] In the following, exemplary embodiments according to this application will be described in detail with reference to the accompanying drawings.

[0024] Now for reference Figure 1 , Figure 1 This is a schematic flowchart of an offline diagnostic data parsing method 100 according to an embodiment of this application. Figure 1 As shown, the offline diagnostic data parsing method 200 includes the following steps: S110: Receive a parsing file, wherein the parsing file includes one or more of the following: a diagnostic request identifier, a diagnostic response identifier, a diagnostic protocol type, and diagnostic channel information. In some embodiments, the user can parse offline diagnostic data by importing the parsing file.

[0025] Users import a pre-configured parsing file through the interactive interface of the VBus desktop client. This file is the core configuration basis for the parsing process, defining the basic parameters and rules of diagnostic communication, including but not limited to: diagnostic request ID (Req ID) and diagnostic response ID (Rsp ID), used to accurately match and filter target diagnostic message frames in offline data; diagnostic protocol type (such as UDS or GMLAN), used to determine which parsing logic system to use subsequently; and diagnostic channel information, used to identify the data source in multi-channel data acquisition. By importing this file, users can associate general parsing functions with specific diagnostic needs, providing a prerequisite for flexible and accurate offline parsing.

[0026] S120: Based on the diagnostic protocol type, invoke the diagnostic parsing function corresponding to the diagnostic protocol type. Specifically, the diagnostic protocol type may include one or more of the following: UDS protocol and GMLAN protocol.

[0027] Upon receiving the parsed file, the Signal Log Engine module in the system kernel first extracts the diagnostic protocol type field. Based on the value of this field, the system dynamically calls the corresponding diagnostic parsing function set from the pre-built function library. For example, if the protocol is UDS, the parsing function set applicable to the UDS protocol is called, including the 0x2A service function for parsing periodic data (PDID), the 0x22 service function for reading data identifiers (DID), and the 0x23 service function for reading memory; if the protocol is GMLAN, its corresponding function set is called, such as the 0xAA (PDID), 0x22 (PID), 0x1A (DID), and 0x23 (memory read) service parsing functions. This step ensures that subsequent parsing work follows the correct protocol specifications.

[0028] S130: Receive offline diagnostic data, and parse the offline diagnostic data using the diagnostic parsing function to generate a parsing result. In some embodiments, parsing the offline diagnostic data using the diagnostic parsing function may further include determining one or more of the following: data packing order, parsing rules for multiple data identifiers, and memory address merging rules.

[0029] The parsing process officially begins, with the system reading the recorded offline diagnostic data source file. For each frame of the diagnostic response message, the previously invoked specific parsing function decodes it according to the detailed rules defined in the parsing file. This process is far more complex than a simple format conversion; it requires handling various intricate situations: determining the packing order and arrangement of multiple data values ​​within the message based on rules; judging whether a response message contains multiple DIDs / PIDs and extracting the values ​​of each data item accordingly; and, especially for memory data pieced together from multiple reads, the parsing function reassembles scattered data blocks into complete, meaningful, continuous data based on preset memory address merging rules. Ultimately, the original hexadecimal message is converted into engineering values ​​with clear physical meaning, forming the parsing result.

[0030] S140: Write the parsing results into the output file.

[0031] After parsing is complete, the system calls a file writing function to output the generated parsing results in a pre-defined standard format (such as CSV, TXT, etc.) and save it to a specified result file. This result file is typically presented in a structured table format, containing key information such as timestamps, original messages, parsed parameter names, values, and units. This allows engineers to clearly and efficiently browse and analyze historical fault data, thus completing the closed-loop process of offline diagnostic data parsing.

[0032] Now for reference Figure 2 , Figure 2 A schematic block diagram of an offline diagnostic data parsing apparatus 200 according to an embodiment of this application is shown. Figure 2 As shown, the offline diagnostic data parsing device 200 includes: a file import module 210, a function call module 220, and a data parsing module 230.

[0033] The file import module 210 can be configured to receive parsed files, wherein the parsed files include one or more of the following: diagnostic request identifier, diagnostic response identifier, diagnostic protocol type, and diagnostic channel information; The function call module 220 can be configured to call a diagnostic parsing function corresponding to the diagnostic protocol type. The diagnostic protocol type may include one or more of the following: UDS protocol and GMLAN protocol. When the diagnostic protocol type is UDS protocol, the diagnostic parsing function may include one or more of the following: 0x2A parsing function, 0x22 parsing function, and 0x23 parsing function. When the diagnostic protocol type is GMLAN protocol, the diagnostic parsing function may include one or more of the following: 0xAA parsing function, 0x22 parsing function, 0x1A parsing function, and 0x23 parsing function.

[0034] The data parsing module 230 can be configured to receive offline diagnostic data and parse the offline diagnostic data using the diagnostic parsing function to generate parsing results. The data parsing module 230 can be further configured to determine one or more of the following: data packaging order, parsing rules for multiple data identifiers, and memory address merging rules.

[0035] The offline diagnostic data parsing device 200 may also include a result output module 240, which can be configured to write the parsing results into an output result file.

[0036] This application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the offline diagnostic data parsing method of this application described above.

[0037] This application also provides a computer device, including a storage module, a processor, and a computer program stored on the storage module and executable on the processor, wherein the processor executes the computer program to implement the offline diagnostic data parsing method of this application described above.

[0038] The specific embodiments described above are merely for the purpose of more clearly illustrating the principles of this application, wherein the various components are clearly shown or described to make the principles of this application easier to understand. Various modifications or variations can be easily made to this application by those skilled in the art without departing from the scope of this application. Therefore, it should be understood that all such modifications or variations should be included within the patent protection scope of this application.

Claims

1. An offline diagnostic data parsing method, characterized in that, The method includes the following steps: Receive a parsing file, wherein the parsing file includes one or more of the following: diagnostic request identifier, diagnostic response identifier, diagnostic protocol type, and diagnostic channel information; Based on the diagnostic protocol type, invoke the diagnostic parsing function corresponding to the diagnostic protocol type; Receive offline diagnostic data, and use the diagnostic parsing function to parse the offline diagnostic data to generate parsing results.

2. The method as described in claim 1, characterized in that, The method further includes writing the parsing results into an output file.

3. The method as described in claim 1, characterized in that, Parsing the offline diagnostic data using the diagnostic parsing function further includes determining one or more of the following: data packing order, parsing rules for multiple data identifiers, and memory address merging rules.

4. The method as described in claim 1, characterized in that, The diagnostic protocol type includes one or more of the following: UDS protocol and GMLAN protocol.

5. The method as described in claim 4, characterized in that, When the diagnostic protocol type is UDS protocol, the diagnostic parsing function includes one or more of the following: 0x2A parsing function, 0x22 parsing function, and 0x23 parsing function.

6. The method as described in claim 4, characterized in that, When the diagnostic protocol type is GMLAN protocol, the diagnostic parsing function includes one or more of the following: 0xAA parsing function, 0x22 parsing function, 0x1A parsing function, and 0x23 parsing function.

7. An offline diagnostic data parsing device, characterized in that, The device includes: The file import module is configured to receive parsed files, wherein the parsed files include one or more of the following: diagnostic request identifier, diagnostic response identifier, diagnostic protocol type, and diagnostic channel information; The function call module is configured to call the diagnostic parsing function corresponding to the diagnostic protocol type based on the diagnostic protocol type; and The data parsing module is configured to receive offline diagnostic data and use the diagnostic parsing function to parse the offline diagnostic data to generate parsing results.

8. The apparatus as claimed in claim 7, characterized in that, The device further includes a result output module configured to write the parsing result into an output result file.

9. The apparatus as claimed in claim 7, characterized in that, The data parsing module is further configured to determine one or more of the following: data packaging order, parsing rules for multiple data identifiers, and memory address merging rules.

10. The apparatus as claimed in claim 7, characterized in that, The diagnostic protocol type includes one or more of the following: UDS protocol and GMLAN protocol.

11. The apparatus as claimed in claim 10, characterized in that, When the diagnostic protocol type is UDS protocol, the diagnostic parsing function includes one or more of the following: 0x2A parsing function, 0x22 parsing function, and 0x23 parsing function.

12. The apparatus as claimed in claim 10, characterized in that, When the diagnostic protocol type is GMLAN protocol, the diagnostic parsing function includes one or more of the following: 0xAA parsing function, 0x22 parsing function, 0x1A parsing function, and 0x23 parsing function.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the offline diagnostic data parsing method according to any one of claims 1-6.

14. A computer device comprising a storage module, a processor, and a computer program stored on the storage module and executable on the processor, characterized in that, When the processor executes the computer program, it implements the offline diagnostic data parsing method according to any one of claims 1-6.

Images