CN117112280A

CN117112280A - DID parameter verification method, system and medium based on ODX file analysis

Info

Publication number: CN117112280A
Application number: CN202311108615.1A
Authority: CN
Inventors: 王献辉; 戎春健; 王舒成
Original assignee: Zero Beam Technology Co ltd
Current assignee: Zero Beam Technology Co ltd
Priority date: 2023-08-31
Filing date: 2023-08-31
Publication date: 2023-11-24

Abstract

The application relates to a DID parameter verification method, a system and a medium based on ODX file analysis, and relates to the technical field of vehicle diagnosis, wherein the method comprises the steps of decompressing a file with a PDX suffix and loading the ODX file according to the hierarchical inheritance relation of the file; reading whole vehicle configuration information based on the ODX file, wherein the whole vehicle configuration information comprises vehicle type information, ECU information, DID information, DTC information and diagnosis service information; determining inheritance relation of DID parameters based on the whole vehicle configuration information, constructing a DID parameter model, traversing all nodes of the DID parameter model, and generating a basic verification unit; and verifying the basic verification unit based on a preset verification rule to obtain a verification result. The application has the effects of improving the coverage rate of the ODX file content, ensuring the correctness of DID parameters, improving the success rate of remote fault diagnosis and local fault diagnosis of the automobile and reducing the cost of the automobile enterprise and the automobile owner.

Description

DID parameter verification method, system and medium based on ODX file analysis

Technical Field

The application relates to the technical field of vehicle diagnosis, in particular to a DID parameter verification method, a DID parameter verification system and a DID parameter verification medium based on ODX file analysis.

Background

The ODX file (Open Diagnostic data eXchange) is a diagnostic database format defined by the ISO 22901 standard for describing diagnostic information and communication parameters of a vehicle Electronic Control Unit (ECU). The ODX file is critical to the failure diagnosis of modern automobiles because it contains important information about the vehicle system and failure.

DID stands for Data Identifier, which is an important element in ODX files. In the field of automotive diagnostics, DID is used to identify and describe specific data items on a vehicle Electronic Control Unit (ECU). The fault diagnosis tool can know available data items on each ECU through DID information in the ODX file, so that fault diagnosis, monitoring and control of the vehicle are realized. By reading and analyzing the data in the DID, the diagnostic tool can obtain status information of the vehicle, detect faults, assist the technician in locating the problem, and perform necessary repair and maintenance.

The accuracy of the DID parameters is critical to automobile diagnostics and repair. The method directly influences the accuracy and efficiency of fault diagnosis, the ODX file content is difficult to fully cover by the manual diagnosis test in the current stage, and then the accuracy of DID parameters is difficult to ensure to be sufficiently corrected, so that the failure rate of remote fault diagnosis and local fault diagnosis of the automobile is high, and the cost of an automobile enterprise and an automobile owner is increased.

Disclosure of Invention

In order to solve the problems, the application provides a DID parameter verification method, a DID parameter verification system and a DID parameter verification medium based on ODX file analysis, which are used for improving the coverage rate of ODX file contents, ensuring the correctness of DID parameters, improving the success rate of remote fault diagnosis and local fault diagnosis of an automobile and reducing the cost of an automobile enterprise and an automobile owner.

In order to achieve the above purpose, the application adopts the following technical scheme:

in a first aspect, the present application provides a DID parameter verification method based on ODX file parsing, which adopts the following technical scheme:

a DID parameter verification method based on ODX file analysis comprises the following steps:

decompressing the file with the suffix of PDX and loading the ODX file according to the hierarchical inheritance relation of the file;

reading whole vehicle configuration information based on the ODX file, wherein the whole vehicle configuration information comprises vehicle type information, ECU information, DID information, DTC information and diagnosis service information;

determining inheritance relation of DID parameters based on the whole vehicle configuration information, constructing a DID parameter model, traversing all nodes of the DID parameter model, and generating a basic verification unit;

and verifying the basic verification unit based on a preset verification rule to obtain a verification result.

Further, in the above method for checking the DID parameter based on the analysis of the ODX file, decompressing the file with the suffix PDX and loading the ODX file according to the hierarchical inheritance relationship of the file includes:

decompressing the PDX file and obtaining the file path of the ODX in the PDX file;

and sequentially loading an ECU-SHARED-DATA file, a PROTOCOL file, a FUNCTIONAL-GROUP file, a BASE-VARIANT file and an ECU-VARIANT file to obtain an ODX file according to the file path.

Further, in the above method for checking the DID parameter based on the analysis of the ODX file, the reading of the entire vehicle configuration information based on the ODX file includes vehicle type information, ECU information, DID information, DTC information, and diagnostic service information, including:

analyzing the ODX file to obtain a corresponding file structure;

searching the whole vehicle configuration node according to the file structure to obtain vehicle type information and ECU information;

according to the file structure, searching the DID node to obtain DID information;

according to the file structure, searching a DTC node to obtain DTC information;

and searching the diagnosis service node according to the file structure to obtain diagnosis service information.

Further, in the above method for verifying the DID parameters based on the analysis of the ODX file, determining the inheritance relationship of the DID parameters based on the whole vehicle configuration information, constructing a DID parameter model, traversing all nodes of the DID parameter model, and generating a basic verification unit, including:

according to the read whole vehicle configuration information, determining a function group supported by each ECU, a DID parameter list contained in the function group and inheritance relation of the DID parameters;

based on the DID parameter list and inheritance relation of each DID parameter, organizing each DID parameter by using a tree structure to form a DID parameter model;

and traversing all nodes of the DID parameter model in a hierarchical manner, and generating a basic check unit, wherein the basic check unit consists of child nodes with the same father node.

Further, in the above method for checking the DID parameter based on ODX file parsing, the checking the basic check unit based on a preset check rule to obtain a check result includes:

defining a preset verification rule;

traversing all basic verification units in the DID parameter model;

and checking whether the attribute parameters of each basic check unit accord with the check rule according to the check rule.

Further, in the above method for checking the DID parameter based on the analysis of the ODX file, the defining a preset checking rule includes:

defining a verification rule of parameter names;

defining a byte start bit and a byte size check rule;

and defining a check rule of a bit start bit and a bit size.

In a second aspect, the present application provides a DID parameter verification system based on ODX file parsing, which adopts the following technical scheme:

an ODX file parsing-based DID parameter verification system, comprising:

an ODX file obtaining unit, configured to decompress a file with a suffix of PDX and load the ODX file according to a hierarchical inheritance relationship of the file;

the whole vehicle configuration information acquisition unit is used for reading whole vehicle configuration information based on the ODX file, wherein the whole vehicle configuration information comprises vehicle type information, ECU information, DID information, DTC information and diagnosis service information;

the DID parameter model construction unit is used for determining inheritance relation of DID parameters based on the whole vehicle configuration information, constructing a DID parameter model, traversing all nodes of the DID parameter model and generating a basic verification unit;

and the DID parameter verification unit is used for verifying the basic verification unit based on a preset verification rule to obtain a verification result.

In a third aspect, the present application provides a vehicle end diagnosis module, which adopts the following technical scheme:

a vehicle end diagnosis module provided in a vehicle, the vehicle end diagnosis module being configured with a DID parameter verification system based on ODX file parsing as described in the second aspect above.

In a fourth aspect, the present application provides a cloud diagnosis module, which adopts the following technical scheme:

a cloud diagnosis module disposed at the cloud, where the cloud diagnosis module is configured with a DID parameter verification system based on ODX file parsing as described in the second aspect.

In a fifth aspect, the present application provides a diagnostic apparatus, which adopts the following technical scheme:

a diagnostic apparatus in which a DID parameter verification system based on ODX file parsing as described in the second aspect is disposed.

In a sixth aspect, the present application provides a readable storage medium, which adopts the following technical scheme:

a readable storage medium storing computer instructions which, when executed by a processor, implement an ODX file parsing-based DID parameter verification method according to any one of the first aspects.

In summary, the present application includes at least one of the following beneficial technical effects:

1. the DID parameter verification method based on ODX file analysis can realize comprehensive verification of the DID parameters, can help ensure the correctness of the whole vehicle configuration information and the DID parameters, and improves the accuracy and reliability of a diagnosis tool, thereby reducing the failure rate of automobile fault diagnosis and reducing the cost of an automobile enterprise and an automobile owner;

2. the vehicle end diagnosis module can be used as a part of vehicle local diagnosis, and the accuracy and reliability of DID parameters are ensured by analyzing and checking the ODX file to ensure the accuracy of a diagnosis database. The method is beneficial to improving the accuracy and efficiency of fault diagnosis, and reduces the failure rate of fault diagnosis caused by error of a diagnosis database, thereby reducing the cost of a train enterprise and a train owner; 3. the cloud diagnosis module is used as a remote diagnosis tool, and can realize remote diagnosis of the vehicle by combining with a check system based on ODX file analysis, so that the efficiency and reliability of fault diagnosis are improved. Through remote diagnosis and verification, the problems of the vehicle are found and solved in time, and better services are provided for vehicle owners and maintenance service providers. Meanwhile, the cloud diagnosis module is beneficial to improving management and monitoring of the whole vehicle diagnosis database by vehicle manufacturers and improving vehicle quality and after-sales service level.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flow chart of an embodiment of a DID parameter verification method based on ODX file parsing according to the present application.

Fig. 2 is a flow chart of another embodiment of a DID parameter verification method based on ODX file parsing according to the present application.

Fig. 3 is a flowchart of another embodiment of a DID parameter verification method based on ODX file parsing according to the present application.

Fig. 4 is a flowchart of another embodiment of a DID parameter verification method based on ODX file parsing according to the present application.

Fig. 5 is a tree structure diagram of one embodiment of the DID parametric model in the present application.

Fig. 6 is a flowchart of another embodiment of a DID parameter verification method based on ODX file parsing according to the present application.

Fig. 7 is a flowchart of another embodiment of a DID parameter verification method based on ODX file parsing according to the present application.

Fig. 8 is a block diagram of an embodiment of a DID parameter verification system based on ODX file parsing according to the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to fall within the scope of the application. Furthermore, it should be understood that the detailed description is presented herein for purposes of illustration and description only, and is not intended to limit the application. In the present application, unless otherwise indicated, terms of orientation such as "upper", "lower", "left", "right", "front", "rear" are generally used to refer to the directions of the upper, lower, left and right sides of the device in actual use or operation, and are specifically shown in the drawings.

It should be noted that the following description order of the embodiments is not intended to limit the preferred order of the embodiments of the present application. In the following embodiments, the descriptions of the embodiments are focused on, and for the part that is not described in detail in a certain embodiment, reference may be made to the related descriptions of other embodiments.

The execution sequence of the method steps in the embodiments of the present application may be performed according to the sequence described in the specific embodiments, or the execution sequence of each step may be adjusted according to actual needs on the premise of solving the technical problem, which is not listed here.

The application is described in further detail below with reference to fig. 1-8.

The embodiment of the application discloses a DID parameter verification method based on ODX file analysis, and referring to FIG. 1, the method comprises the following steps:

s1, decompressing a file with a suffix of PDX and loading the ODX file according to the hierarchical inheritance relation of the file;

s2, reading whole vehicle configuration information based on the ODX file, wherein the whole vehicle configuration information comprises vehicle type information, ECU information, DID information, DTC information and diagnosis service information;

s3, determining inheritance relation of DID parameters based on the whole vehicle configuration information, constructing a DID parameter model, traversing all nodes of the DID parameter model, and generating a basic verification unit;

and S4, checking the basic check unit based on a preset check rule to obtain a check result.

Specifically, firstly, a file with a suffix of PDX is decompressed, and the content in the file is extracted into a temporary directory. And loading the ODX files in turn according to the hierarchical inheritance relation of the files. During loading, it is ensured that the lower level files can inherit and overlay the contents of the higher level files. And then, reading various parameter information of the whole vehicle configuration from the loaded ODX file, wherein the parameter information comprises vehicle type information, ECU information, DID information, DTC information and diagnosis service information. And determining the inheritance relation of each DID parameter according to the information of the vehicle type, the ECU, the DID and the like, and constructing the inheritance relation into a DID parameter model with a tree structure. Next, an algorithm is used to traverse all nodes of the model, generating a basic check unit, with child nodes having the same parent node as a set of check parameters. And finally, checking each basic checking unit by using a preset checking rule, and checking whether the DID parameter in each basic checking unit meets the specified attribute requirement. And recording the verification result, wherein the verification result comprises a basic verification unit passing verification and a basic verification unit not passing verification. For basic check units which do not pass the check, relevant error or warning information is recorded.

Through the steps, the DID parameter verification method based on ODX file analysis can realize comprehensive verification of the DID parameters. The method can help ensure the correctness of the configuration information and DID parameters of the whole vehicle, and improve the accuracy and reliability of the diagnosis tool, thereby reducing the failure rate of the fault diagnosis of the vehicle and reducing the cost of the vehicle enterprise and the vehicle owners.

Further, referring to fig. 2 as an embodiment of the present application, step S1, decompressing a file with a suffix PDX and loading the ODX file according to a hierarchical inheritance relationship of the file, includes:

s11, decompressing the PDX file and acquiring a file path of the ODX in the PDX file;

s12, sequentially loading an ECU-SHARED-DATA file, a PROTOCOL file, a FUNCTIONAL-GROUP file, a BASE-VARIANT file and an ECU-VARIANT file to obtain an ODX file according to the file path.

Specifically, in step S11, first, a file with a suffix PDX is obtained, and the file is a compressed file, including the ODX file and other related information. And (3) decompressing the PDX file, and extracting the content in the PDX file into a temporary directory for subsequent processing. And searching a path containing the ODX file in the decompressed temporary directory. The PDX file typically contains a plurality of ODX files that are interrelated according to the hierarchical inheritance of the files. And finding a corresponding ODX file path according to the information in the PDX file.

In step S12, the ECU-SHARED-DATA file, the pro col file, the functonal-GROUP file, the BASE-variable file, and the ECU-variable file are sequentially loaded according to the file path to obtain the ODX file.

Specifically, the ECU-SHARED-DATA file is found and loaded according to the file path in the PDX file. The ECU-SHARED-DATA file contains vehicle overall configuration information. Such information may be applicable to a plurality of ECUs (Electronic Control Unit, electronic control units) and is therefore referred to as "shared data". The ECU-SHARED-DATA file defines information at the level of the whole vehicle, such as the vehicle model, manufacturer, vehicle Identification Number (VIN), hardware information, etc. The information plays an important role in diagnosis and communication of the whole vehicle.

And finding and loading the PROTOCOL file according to the file path in the PDX file. The ProTOCOL file defines information about the communication PROTOCOL of the vehicle. The communication protocol is a rule and format for communication between the vehicle diagnostic tool and the vehicle ECU. The file contains communication rate, data format, diagnostic session control information, etc., ensuring that the diagnostic tool is able to properly communicate and exchange data with the ECU of the vehicle.

And finding and loading the FUNCTIONAL-GROUP file according to the file path in the PDX file. The FUNCTIONAL-GROUP file defines a FUNCTIONAL GROUP of vehicle ECUs. A function group is a group of related functions and data that are divided by logic and function. An ECU may include a plurality of function groups, each corresponding to a specific vehicle function, such as engine control, body control, air conditioning control, and the like. The definition of these functional groups enables the diagnostic tool to diagnose and control for different functions.

And finding and loading the BASE-VARIANT file according to the file path in the PDX file. The BASE-variance file contains basic configuration information for the vehicle. It describes the basic model and configuration of the vehicle, such as the vehicle model, engine model, date of manufacture of the vehicle, etc. These basic configuration information assist the diagnostic tool in knowing the basic features and attributes of the vehicle.

And finding and loading the ECU-VARIANT file according to the file path in the PDX file. The ECU-VARIANT file defines specific configuration information of the vehicle ECU. One vehicle model may have different ECU configurations, each corresponding to a particular hardware or software discrepancy. The ECU-VARIANT document describes the differences and features between different ECUs, helping diagnostic tools to distinguish and identify different ECU configurations.

In general, the CU-SHARED-DATA file, PROTOCOL file, FUNCTIONAL-GROUP file, BASE-VARIANT file and ECU-VARIANT file collectively constitute an ODX file for describing the entire vehicle configuration information, communication PROTOCOL, function GROUP and configuration information of each ECU of the vehicle. Such data is important for vehicle diagnostics and troubleshooting, and provides the necessary information for the diagnostic tool to enable effective communication with the vehicle and accurate troubleshooting.

Through the steps, the ECU-SHARED-DATA file, the PROTOCOL file, the FUNCTIONAL-GROUP file, the BASE-VARIANT file and the ECU-VARIANT file can be sequentially loaded according to the file paths in the PDX file, and finally the ODX file is obtained. Therefore, the information in the ODX file can be loaded according to the correct hierarchical inheritance relationship, and an accurate data source is provided for the subsequent whole vehicle configuration information and DID parameter verification.

Further, as an embodiment of the present application, referring to fig. 3, step S2, reading the configuration information of the whole vehicle based on the ODX file includes:

s21, analyzing the ODX file to obtain a corresponding file structure;

s22, searching a whole vehicle configuration node according to the file structure to obtain vehicle type information and ECU information;

s23, searching the DID nodes according to the file structure to obtain DID information;

s24, searching a DTC node according to the file structure to obtain DTC information;

and S25, searching for diagnosis service nodes according to the file structure to obtain diagnosis service information.

In particular, most ODX files are stored in XML format, so in this embodiment, an XML parser may be used to parse the file. The XML parser may parse an XML document into a tree file structure in which each node represents an XML element, thereby facilitating access to and processing of the file content. In yet other embodiments, if the ODX file is stored in JSON format, the file may be parsed using a JSON parser. Similar to an XML parser, the JSON parser parses a JSON document into a file structure in the form of key-value pairs, facilitating subsequent operations.

And searching nodes related to the whole vehicle configuration in the file structure obtained by analysis. These nodes typically contain model information, ECU information, and association of model and ECU. Vehicle model information and ECU information are identified and extracted. The vehicle model information may include a vehicle model number, a year of production, a vehicle configuration, and the like. The ECU information may include the name of the ECU, hardware version, software version, and the like. The DID parameters are typically associated with a particular model, so correcting the correctness of the DID parameters requires ensuring that the selected model matches model information described in the ODX file to avoid data inconsistencies or errors. Also, correction of the DID parameter correctness requires confirmation that the selected ECU matches the ECU information defined in the ODX file to ensure that the read DID parameter is associated with the correct ECU information.

In the file structure obtained by the analysis, a node related to the DID (Data Identifier) is searched. DID is a unique identifier for representing vehicle parameters and status. DID information is identified and extracted. The DID information includes data type, data length, data name, data parsing rule, parameter attribute information (e.g., name, byte start bit, byte size, bit start bit, bit size, etc.), etc. The core of correcting the correctness of the DID parameters is to verify whether each DID parameter defined by the DID information is correct. The correction process needs to check the parameter information in the DID information one by one to ensure that it matches and is legal with the actual data of the vehicle.

In the parsed file structure, nodes related to the DTCs (Diagnostic Trouble Code, diagnostic trouble codes) are searched. The DTC is an identifier for indicating a vehicle failure. DTC information is identified and extracted. The DTC information may include an identifier of the DTC, a fault description, a fault type, etc. Although the DTC is generally a parameter for describing the fault code, parameter information related to the DTC may also need to be considered in correcting the DID parameter correctness. For example, certain DID parameters may be associated with the DTC to provide fault diagnosis and fault code information. Therefore, in correcting the correctness of the DID parameters, it may be necessary to confirm whether the definition of the relevant DTC is correct and consistent with the DID parameter association.

In the file structure obtained by the parsing, nodes related to the diagnosis service are searched. Diagnostic services contain definitions of diagnostic functions and services. Diagnostic service information is identified and extracted. Diagnostic service information may include service names, service descriptions, service types, etc. When correcting the correctness of the DID parameters, it is necessary to confirm whether the used diagnostic service supports reading, parsing, and processing of the DID parameters to ensure that the diagnostic tool can correctly use the DID data.

To sum up, the correction of the DID parameter correctness requires the use of the parameter information such as model, ECU, DID, DTC, diagnostic service, etc. in the ODX file. The information ensures that the read and analyzed DID data are consistent with the actual configuration and state of the vehicle, thereby ensuring that the fault diagnosis tool can accurately read and use the related data of the vehicle and improving the accuracy and efficiency of fault diagnosis.

Further, referring to fig. 4, step S3, determining an inheritance relationship of a DID parameter based on the whole vehicle configuration information, constructing a DID parameter model, traversing all nodes of the DID parameter model, and generating a basic verification unit, including:

s31, determining a function group supported by each ECU and a DID parameter list contained in the function group and inheritance relation of the DID parameters according to the read whole vehicle configuration information;

s32, organizing each DID parameter by using a tree structure based on the DID parameter list and the inheritance relation of each DID parameter to form a DID parameter model;

and S33, traversing all nodes of the DID parameter model in a hierarchical manner, and generating a basic check unit, wherein the basic check unit consists of child nodes with the same father node.

Specifically, in step S31, according to the read configuration information of the whole vehicle, a functional group supported by each ECU is found. Each ECU may support multiple functional groups, with each functional group containing a set of related functions and data, including respective DID parameters. A list of DID parameters contained in each function group is determined. And (3) the DID parameters contained in each function group are found from the whole vehicle configuration information, and identifiers or other relevant information of the DID parameters are recorded. The inheritance relationship of the DID parameters is determined, and in the whole vehicle configuration information, some DID parameters may have the inheritance relationship, that is, some DID parameters are derived based on other DID parameters, and are not independently defined.

In step S32, a tree-structured data model is constructed according to the read DID parameter list to organize inheritance relationships among the DID parameters. Referring to fig. 5, for the DID parameters having the inheritance relationship, a corresponding parent-child relationship is established so that the inherited DID parameters can inherit properties from their parent DID parameters. And adding the function groups supported by each ECU and the DID parameters contained in the function groups into the tree structure to form a complete DID parameter model.

In step S33, hierarchical traversal is performed on the DID parameter model using the breadth-first search algorithm, starting from the root node (the DID parameter at the whole vehicle level). In the traversing process, a group of check parameters are formed for child nodes (DID parameters) with the same father node, and a basic check unit is formed. In this way, all child nodes with the same parent node are organized together, facilitating subsequent verification. And recording each generated basic verification unit for the subsequent parameter verification process.

Through the steps, the inheritance relation of the DID parameters can be determined according to the whole vehicle configuration information, the DID parameter model is constructed, basic verification units are generated, the basic verification units are used as basic units for subsequent parameter verification, and the accuracy and the high efficiency of the verification process are ensured.

Further, as an embodiment of the present application, referring to fig. 6, step S4 of verifying the basic verification unit based on a preset verification rule to obtain a verification result includes:

s41, defining a preset check rule;

s42, traversing all basic check units in the DID parameter model;

s43, checking whether the attribute parameters of the basic check units accord with the check rule according to the check rule.

Specifically, in the implementation of the method of the present application, a set of verification rules needs to be defined in advance, so as to check whether the attribute parameters of the basic verification unit meet the requirements. These check rules may cover the specification of the name of the DID parameter, byte start bit, byte size, bit start bit, bit size, etc. It should be noted that the calibration rules should be based on ODX standards and related specifications of the automotive industry to ensure the accuracy and precision of the calibration. And then traversing the DID parameter model by using a breadth-first search algorithm level to acquire all basic verification units. Finally, for each basic verification unit, checking whether the attribute parameters of each basic verification unit accord with the regulations according to the preset verification rules. When the check rule check is performed, the values, sizes, ranges, association relationships with other parameters, and the like of the parameters may be compared. If the attribute parameters of the basic verification unit are found to be not in accordance with the verification rule, corresponding error information or warning information is recorded. For the basic verification unit passing the verification, the related information is also recorded for subsequent processing and display.

Through the steps, all basic check units can be checked, and whether the attribute parameters of the basic check units accord with preset check rules or not is checked. The verification result can be fed back to a related system or user, so that errors or non-normative positions in the ODX file can be found and corrected, the correctness and reliability of the DID parameters are ensured, and the accuracy and usability of the diagnostic tool are improved.

Further, as an embodiment of the present application, the defining a preset verification rule includes: a check rule defining a parameter name, a check rule defining a byte start bit and a byte size, and a check rule defining a bit start bit and a bit size.

Specifically, a check rule of parameter names is defined: the parameter NAME (short_name) should be globally unique, i.e. the NAME of each DID parameter should be unique throughout the ODX file and must not be repeated. If two or more DID parameters are found to have the same parameter name during the traversal, it is indicated that the parameter name does not conform to the rule and error information should be recorded.

Check rules defining byte start bits and byte sizes: the byte start bit (byte_start) of the first parameter should be 0, indicating that its start position in the entire data structure is the first byte. For the subsequent parameters, the byte start bit should be less than or equal to the byte start bit of the previous parameter plus the byte size of the previous parameter, ensuring that the parameters do not overlap in the data structure. The byte start bit of the last parameter plus its byte size (byte_size) should be less than or equal to the total byte size of its parent node parameters to ensure that the parameters do not exceed the range in which its parent node is located. That is, the following formulas are satisfied at the same time:

P ₀ (byte_start) =0, (formula 1);

P _n (byte_start)≤P _n-1 (byte_start)+P _n-1 (byte_size), N > 0, N ε N, (equation 2);

P _n (byte_start)+P _n (byte_size)≤P _parent (byte_size), (formula 3).

Wherein P is _parent As parent parameter, P0 is the first parameter in the child parameters if and only if P _n For the last parameter of the subparameters, equation 3 takes the equal sign.

Check rules defining a bit start bit and a bit size: the bit start bit (bit_start) of the first parameter should be 0, indicating that its start position in the byte is the first bit. For the subsequent parameters, the bit start bit is larger than or equal to the bit start bit of the previous parameter plus the bit size of the previous parameter, so that the parameters are ensured not to overlap in the bytes. The bit start bit of each parameter plus its bit size should be less than or equal to the total bit size (bit_size) of the byte in which its parent node parameter resides, ensuring that the parameter does not exceed the range of the byte in which its parent node resides. I.e. simultaneously satisfying the following formula:

P ₀ (bit_start) =0, (formula 4);

P _n (bit_start)≥P _n-1 (bit_start)+P _n-1 (bit_size), N > 0, N ε N, (equation 5);

P _n (bit_start)+P _n (bit_size)≤P _parent (bit_size), (formula 6).

Wherein P is _parent As parent parameter, P0 is the first parameter in the child parameters if and only if P _n For the last parameter of the subparameters, equation 6 takes the equal sign.

The check rule ensures that the attribute of the DID parameter is legal under the constraint of the whole vehicle configuration information, and the conditions of repetition, out-of-range or out-of-range cannot occur. Through validity verification on the attribute of the DID parameter, the DID parameter in the ODX file can be ensured to be correct and effective, and a reliable basis is provided for subsequent fault diagnosis and parameter use. According to the verification result, the problems in the ODX file can be found and corrected in time, and the accuracy and efficiency of the automobile diagnosis work are improved.

In summary, referring to fig. 7, an implementation procedure of an embodiment of the DID parameter verification method based on ODX file parsing of the present application is as follows:

step 1: and loading the ODX file, decompressing the file with the suffix of PDX, and loading the ODX file according to the hierarchical inheritance relation of the file to obtain the content of the ODX file.

Step 2: and reading the whole vehicle configuration information, and reading various parameter information of the whole vehicle configuration from the ODX file, wherein the parameter information comprises vehicle type information, ECU information, DID information, DTC information and diagnosis service information.

Step 3: and constructing a DID parameter model, determining inheritance relation of DID parameters based on the read whole vehicle configuration information, constructing the DID parameter information into a tree structure, traversing all nodes of the tree structure by using a graph search algorithm level, and generating a basic verification unit.

Step 4: and checking parameter attribute information, wherein the basic checking unit is checked according to a preset checking rule, and the basic checking unit comprises whether the NAME (short_name) of the checking parameter is unique, whether the BYTE START BIT (byte_start) and the BYTE SIZE (byte_size) are legal, and whether the BIT START BIT (bit_start) and the BIT SIZE (bit_size) are legal.

So far, the implementation steps of the DID parameter verification method based on ODX file analysis are completed. According to the method, the whole vehicle configuration information is obtained by analyzing the ODX file, and the DID parameter model is constructed according to the configuration information. And then, checking the DID parameters, ensuring the correctness and legality of the parameters, and improving the accuracy and usability of the diagnostic tool. By the method, failure diagnosis failure caused by error or non-standardization of the ODX file can be effectively avoided, costs of a vehicle enterprise and a vehicle owner are reduced, and success rate and accuracy of remote and local diagnosis of the vehicle are improved.

Based on the DID parameter verification method based on ODX file analysis, the embodiment of the application also discloses a DID parameter verification system based on ODX file analysis.

Referring to fig. 8, a DID parameter verification system based on ODX file parsing includes an ODX file obtaining unit 1, a whole vehicle configuration information obtaining unit 2, a DID parameter model building unit 3, and a DID parameter verification unit 4.

The ODX file obtaining unit 1 is configured to decompress a file with a suffix PDX and load the ODX file according to a hierarchical inheritance relationship of the file. The unit is responsible for processing a file with a PDX suffix, decompressing, loading the ODX file according to the hierarchical inheritance relation of the file, namely decompressing the PDX file and acquiring a path of the ODX file, and then sequentially loading an ECU-SHARED-DATA file, a PROTOCOL file, a FUNCTIONAL-GROUP file, a BASE-VARIANT file and an ECU-VARIANT file to obtain the ODX file.

The whole vehicle configuration information obtaining unit 2 is configured to read whole vehicle configuration information based on the ODX file, including vehicle type information, ECU information, DID information, DTC information, and diagnostic service information. This step may require parsing the contents of the ODX file and extracting the desired vehicle configuration information therefrom.

The DID parameter model building unit 3 is configured to determine an inheritance relationship of the DID parameter based on the entire vehicle configuration information, build a DID parameter model, and traverse all nodes of the DID parameter model to generate a basic verification unit. The unit determines inheritance relation of DID parameters according to the acquired whole vehicle configuration information, builds a DID parameter model, traverses all nodes of the DID parameter model and generates a basic verification unit. This process involves organizing the DID parameters according to the relationship between the functional groups and the ECU, forming a data model of the tree structure, and then traversing the model to generate the basic verification units.

The DID parameter checking unit 4 is configured to check the basic checking unit based on a preset checking rule to obtain a checking result. The unit is used for checking the basic check unit based on a preset check rule to obtain a check result. In this step, each basic verification unit is verified, and whether the attribute parameters of the basic verification unit accord with a preset verification rule is checked. The verification result may include basic verification units that pass the verification and basic verification units that fail the verification, as well as associated error or warning information.

The whole system realizes the flow of analyzing and checking the DID parameters in the ODX file through the cooperative work of the four units. The system can help a diagnosis tool to accurately identify and process parameters and fault conditions of the vehicle, and improves the accuracy and efficiency of vehicle diagnosis.

Further, the embodiment of the application also discloses a vehicle end diagnosis module which is arranged on the vehicle and is configured with the DID parameter verification system based on ODX file analysis.

The vehicle end diagnosis module can be used as a part of vehicle local diagnosis, and the accuracy and reliability of DID parameters are ensured by analyzing and checking the ODX file to ensure the accuracy of a diagnosis database. The method is beneficial to improving the accuracy and efficiency of fault diagnosis, and reduces the failure rate of fault diagnosis caused by error of a diagnosis database, thereby reducing the cost of a train enterprise and a train owner.

Further, the embodiment of the application also discloses a cloud diagnosis module which is arranged at the cloud and is configured with the DID parameter verification system based on ODX file analysis.

The cloud diagnosis module is used as a remote diagnosis tool, and can realize remote diagnosis of the vehicle by combining with a check system based on ODX file analysis, so that the efficiency and reliability of fault diagnosis are improved. Through remote diagnosis and verification, the problems of the vehicle are found and solved in time, and better services are provided for vehicle owners and maintenance service providers. Meanwhile, the cloud diagnosis module is beneficial to improving management and monitoring of the whole vehicle diagnosis database by vehicle manufacturers and improving vehicle quality and after-sales service level.

Further, the embodiment of the application also discloses a diagnostic device, and the device is internally provided with the DID parameter verification system based on ODX file analysis.

According to the diagnosis device provided by the embodiment of the application, the functional diversity of the third-party diagnosis equipment is increased and the accuracy and reliability of fault diagnosis are improved through the internal configuration of the ODX file analysis-based verification system. This will make the maintenance and trouble diagnosis of vehicle more convenient high-efficient, bring better diagnosis experience and quality of service for car owner and maintenance service provider.

The embodiment of the application also discloses a readable storage medium storing a computer program which when executed by a processor realizes the steps of the DID parameter verification method based on ODX file analysis. The computer readable storage medium may include: any entity or device capable of carrying a computer program, a recording medium, a USB flash disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a Read-only memory (ROM), a random access memory (RAM, random Access Memory), a software distribution medium, and so forth. The computer program comprises computer program code. The computer program code may be in the form of source code, object code, executable files, or in some intermediate form, among others. The computer readable storage medium may include: any entity or device capable of carrying computer program code, a recording medium, a USB flash disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a Read-only memory (ROM), a random access memory (RAM, random Access Memory), a software distribution medium, and so forth.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.

Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, system that includes a processing module, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.

The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. The DID parameter verification method based on ODX file analysis is characterized by comprising the following steps of:

2. The method for checking the DID parameters based on the analysis of the ODX file according to claim 1, wherein decompressing the file with the suffix PDX and loading the ODX file according to the hierarchical inheritance relationship of the file comprises:

3. The method for checking the DID parameter based on the ODX file parsing according to claim 1, wherein the reading the entire vehicle configuration information based on the ODX file includes vehicle type information, ECU information, DID information, DTC information, and diagnostic service information, and includes:

analyzing the ODX file to obtain a corresponding file structure;

4. The method for checking the DID parameters based on the ODX file parsing according to claim 1, wherein determining the inheritance relation of the DID parameters based on the whole vehicle configuration information, constructing a DID parameter model, traversing all nodes of the DID parameter model, and generating a basic checking unit includes:

5. The method for checking the DID parameter based on the ODX file parsing according to claim 1, wherein the checking the basic check unit based on the preset check rule to obtain the check result includes:

defining a preset verification rule;

traversing all basic verification units in the DID parameter model;

6. The method for checking the DID parameters based on the ODX file parsing according to claim 5, wherein defining the preset checking rule includes:

defining a verification rule of parameter names;

defining a byte start bit and a byte size check rule;

and defining a check rule of a bit start bit and a bit size.

7. An ODX file parsing-based DID parameter verification system, comprising:

8. The vehicle-end diagnosis module provided in a vehicle, wherein the vehicle-end diagnosis module is configured with the DID parameter verification system based on ODX file parsing as set forth in claim 7.

9. The cloud diagnosis module disposed at the cloud, wherein the cloud diagnosis module is configured with the DID parameter verification system based on ODX file parsing as set forth in claim 7.

10. A diagnostic device, wherein the device is configured with a DID parameter verification system based on ODX file parsing as described in claim 7.

11. A readable storage medium storing computer instructions which, when executed by a processor, implement a DID parameter verification method based on ODX file parsing as claimed in any one of claims 1 to 6.