A method for standardizing automobile DTC data

Abstract

The present invention provides a method for standardizing automobile DTC data, including format standardization and basic information extraction from DTC original data to form a standard dictionary table; extracting basic information of each field from the DTC data of the vehicle model to be developed to form a business data meta-information table; creating a comparison rule, comparing the business data meta-information table with the DTC elements in the standard dictionary table to determine the standardization task; based on the standardization task, creating a standardized operation rule to respectively complete the creation of information such as reporting factor, signal deviation meaning, signal source information, reporting subject, signal deviation level, severity, etc. The present invention forms a standard dictionary table by format standardization of DTC original data, and can quickly obtain unmatched DTC data by comparing the DTC data of the vehicle model to be developed with the standard dictionary table, and then, according to the needs, automatic matching or new development is performed to achieve rapid development and correspondence of the DTC data of the vehicle model to be developed, so as to reduce the development cost.

Description

Technical Field

[0001] The present invention relates to the technical field of automobile fault diagnosis, and more specifically, to a method for standardizing automobile DTC data. Background Art

[0002] In the field of automobile fault diagnosis, DTC technology can guide maintenance personnel to quickly locate the fault part and take corresponding maintenance measures by reading the fault code stored in the automobile control unit. With the development of automobile intelligence and networking, DTC technology is also constantly improving and improving, and DTC reference materials are also constantly iterating, and some problems are derived at the same time, such as:

[0003] 1. For the same supplier, DTC codes or meaning descriptions are frequently iterated, which is not easy for DTC to understand;

[0004] 2. Even if the DTC codes or meanings of products from different suppliers are different, the actual internal reporting logic is the same and the diagnostic methods are the same or similar. However, during actual fault diagnosis, due to the different DTC codes or meanings, the diagnostic personnel need to carefully analyze the differences and it is difficult to directly borrow historical experience.

[0005] 3. For fault diagnosis manuals developed based on DTC reference materials, developers need to spend more time analyzing DTC reference materials to confirm whether the DTC fault diagnosis process developed in the past can be borrowed.

[0006] Therefore, how to provide an intelligent, efficient and lower-cost method for standardizing automobile DTC data is an urgent problem that technicians in this field need to solve. Summary of the invention

[0007] The invention provides a method for standardizing automobile DTC data, so as to solve the problem that the existing automobile DTC data code description is disordered, resulting in high development cost.

[0008] According to one aspect of the present invention, a method for standardizing automobile DTC data is provided, comprising the following steps:

[0009] Step 1: Standardize the format and extract basic information from the DTC original data to form a standard dictionary table;

[0010] Step 2, extracting basic information of each field from the DTC data of the vehicle model to be developed to form a business data meta-information table;

[0011] Step 3: Create comparison rules, compare the business data metadata table with the DTC elements in the standard dictionary table, and determine the standardization tasks;

[0012] Step 4: Based on the standardized tasks, create standardized operating rules to complete the creation of reporting factors, signal deviation meaning, signal source information, reporting subject, signal deviation level, severity and other information to complete the DTC data standardization.

[0013] Preferably, based on the above solution, the data element information in the standard dictionary table includes: DTC code, sub-product system to which the DTC code belongs, controller name, controller supplier, controller version, and fault code.

[0014] Based on the above solution, step 3 specifically includes comparing the DTC elements in the business data element information table with the standard dictionary table.

[0015] When the controller name and fault code meaning are the same, the DTC standard meaning information in the matching DTC standard data in the standard dictionary table is referenced and marked as "referenced";

[0016] When the controller name and DTC code are the same, the DTC standard meaning information in the matching DTC standard data in the standard dictionary table is borrowed and marked as "pending confirmation";

[0017] When at least one of the controller names, DTC codes or fault code meaning elements is the same, the DTC standard meaning information in the matching DTC standard data in the standard dictionary table is borrowed and marked as "to be modified";

[0018] When the data metadata information is different, the DTC data is marked as "newly developed".

[0019] Based on the above scheme, the standardized operation rule in step 4 is preferably:

[0020] The DTC standard meaning information marked as "reference" does not need to be modified and can be submitted for review directly;

[0021] For DTC standard meaning information marked as "to be confirmed" or "to be modified", the recommended DTC standard meaning information shall be confirmed or modified according to the DTC information processing standard;

[0022] For those marked as "Newly Developed", create DTC standard meaning information such as reporting factor, signal deviation meaning, signal source information (parts, areas), reporting subject, signal deviation level, severity, etc. based on the basic information of DTC data extracted in step 1.

[0023] The present invention provides a method for standardizing automobile DTC data, which forms a standard dictionary table by formatting DTC original data, and quickly obtains unmatched DTC data by comparing the DTC data of a vehicle model to be developed with the standard dictionary table. Then, automatic matching or new development is performed as needed to achieve rapid development and correspondence of the DTC data of the vehicle model to be developed, thereby reducing development costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0025] Figure 1 The figure is a flowchart of the automobile DTC data standardization processing method of the present invention. DETAILED DESCRIPTION

[0026] The specific implementation of the present invention is further described in detail below in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present invention, but are not intended to limit the scope of the present invention.

[0027] It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections.

[0028] In order to simplify the drawings, only the parts related to the present invention are schematically shown in each figure, and they do not represent the actual structure of the product. In addition, in order to simplify the drawings and facilitate understanding, in some figures, only one of the parts with the same structure or function is schematically drawn or marked. In this article, "one" not only means "only one", but also means "more than one".

[0029] It should be further understood that the term “and / or” used in the specification and appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0030] In the embodiments shown in the drawings, the indications of directions (such as up, down, left, right, front and back) used to explain the structure and movement of the various components of the present invention are not absolute but relative. These descriptions are appropriate when these components are in the positions shown in the drawings. If the descriptions of the positions of these components change, the indications of these directions also change accordingly.

[0031] In addition, in the description of the present application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0032] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings and other implementation methods can be obtained based on these drawings without creative work.

[0033] See also Figure 1 , as shown, a method for standardizing automobile DTC data of the present invention comprises the following steps:

[0034] Step 1: Standardize the format and extract basic information from the DTC original data to form a standard dictionary table;

[0035] Specifically, a DTC data processing module is constructed for standardizing DTC data, and the processing module includes two operation permissions: a data processing end and a data review end; a DTC standard data storage module is constructed for storing DTC standard data that takes effect after standardization processing.

[0036] The processing module adapts the DTC reference data with standardized format and automatically extracts basic information, where the basic information includes: DTC code, sub-product system to which the DTC code belongs, controller name, controller supplier, controller version, fault code meaning and other basic DTC data information.

[0037] The information is extracted and formed into a standard dictionary table in a standard format. The data element information in the standard dictionary table includes: DTC code, sub-product system to which the DTC code belongs, controller name, controller supplier, controller version, and fault code.

[0038] Step 2, extracting basic information of each field from the DTC data of the vehicle model to be developed to form a business data meta-information table;

[0039] Step 3: Create comparison rules, compare the business data metadata table with the DTC elements in the standard dictionary table, and determine the standardization tasks;

[0040] Import the DTC data of the development vehicle model to be standardized into the processing module, set the DTC data comparison rules in the processing module to create the DTC data standardization task,

[0041] Specifically, the DTC code, sub-product system, controller name, fault code meaning and other information of the DTC data to be standardized are matched with the DTC standard data (including: DTC code, sub-product system, controller name, controller vendor, controller version number, fault code meaning, DTC standard meaning and other information) that has been standardized in the storage module, and DTC data standardization tasks are created according to the matching situation. The comparison rules are as follows:

[0042] A1. If the DTC code, sub-product system, controller name, and fault code meaning information are the same, it means that the DTC data has been standardized and there is no need to create a new DTC data standardization task;

[0043] A2. For controller names, DTC codes, and fault code meaning information that are the same, the processing module references the DTC standard meaning information in the matching DTC standard data in the storage module and marks it as "reference", generating the corresponding DTC data standardization task;

[0044] A3. If the controller name and fault code meaning information are the same, the processing module references the DTC standard meaning information in the matching DTC standard data in the storage module and marks it as "reference", and generates the corresponding DTC data standardization task;

[0045] A4. If the controller name and DTC code are the same, the processing module borrows the DTC standard meaning information in the matching DTC standard data in the storage module and marks it as "pending confirmation", and generates the corresponding DTC data standardization task;

[0046] A5. If at least one of the controller names, DTC codes or fault code meaning elements is the same, the processing module borrows the DTC standard meaning information in the matching DTC standard data in the storage module and marks it as "to be modified", and generates the corresponding DTC data standardization task;

[0047] A6. If the information is not the same, the DTC data will be marked as "newly developed".

[0048] Step 4: Based on the standardized tasks, create standardized operating rules to complete the creation of reporting factors, signal deviation meaning, signal source information, reporting subject, signal deviation level, severity and other information to complete the DTC data standardization.

[0049] The standardized operating rules in step 4 are:

[0050] B1: The DTC standard meaning information marked as "reference" does not need to be modified and can be submitted for review directly;

[0051] B2, for the DTC standard meaning information marked as "to be confirmed" or "to be modified", the recommended DTC standard meaning information is confirmed or modified according to the DTC information processing standard;

[0052] B3, for those marked as "newly developed", create DTC standard meaning information such as reporting factor, signal deviation meaning, signal source information (parts, areas), reporting subject, signal deviation level, severity, etc. based on the basic information of DTC data extracted in step 1.

[0053] In B3, based on the basic information of DTC data extracted in step 1, DTC standard meaning information such as reporting factor, signal deviation meaning, signal source information (parts, areas), reporting subject, signal deviation level, severity, etc. is created. After the created information is reviewed and effective by the data review end, it is stored in the storage module to complete the DTC standardization processing of the vehicle model to be developed.

[0054] The specific "newly developed" DTC information processing standards are as follows:

[0055] 1) Creation of reporting subject information

[0056] The reporting code body is the controller information used to describe the fault code storage and perform logical judgment.

[0057] 2) Creation of reporting factor information

[0058] Create a reporting factor database to store information such as signals converted through voltage, resistance, and current that are clearly defined in the meaning of the fault code (for example, temperature, rainfall position, liquid level, speed signal, etc.) or basic physical quantities that are clearly defined in the meaning of the fault code (for example, voltage, current, resistance, phase, power, axle load, frequency, yaw rate, pressure, etc.).

[0059] 3) Signal source information creation

[0060] The data processing end selects the signal source - part information associated with the DTC fault from the vehicle parts database based on the part information expressed in the meaning of the fault code. If there is no suitable general part name, a new one will be created.

[0061] The data processing end creates signal source-area information based on the non-component, function, and system information expressed in the meaning of the fault code.

[0062] 4) Creation of information on the meaning of signal deviation

[0063] The processing module automatically extracts characters from the meaning of the fault code that are used to indicate a functional failure or a fault phenomenon.

[0064] 5) Signal deviation level information creation

[0065] The processing module automatically imports the fault code meaning information extracted from the DTC data, and the data processing end deletes the fault code meaning information and retains the level information that has been clearly defined in the fault code meaning.

[0066] For example: If the fault code meaning is described as: clutch overtemperature level 2 fault, then the signal deviation level of the DTC standardized data is: level 2.

[0067] 6) Severity information creation

[0068] The data processing end creates corresponding severity level information based on the consequences caused by the fault code (ranging from affecting driving safety to only providing a warning, and dividing the severity levels).

[0069] The present invention provides a method for standardizing automobile DTC data, which forms a standard dictionary table by formatting DTC original data, and quickly obtains unmatched DTC data by comparing the DTC data of a vehicle model to be developed with the standard dictionary table. Then, automatic matching or new development is performed as needed to achieve rapid development and correspondence of the DTC data of the vehicle model to be developed, thereby reducing development costs.

[0070] Finally, the method of the present application is only a preferred implementation scheme and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for standardizing automobile DTC data, characterized in that: The following steps are included: Step 1, standardizing the format and extracting basic information from the DTC original data to form a standard dictionary table, wherein the data metadata in the standard dictionary table includes: DTC code, sub-product system to which the DTC code belongs, controller name, controller supplier, controller version, and fault code; Step 2: extract the basic information of each field from the DTC data of the vehicle model to be developed to form a business data metadata table; Step 3: Create a comparison rule, compare the DTC elements in the business data metadata table with the standard dictionary table, and determine the standardization task; When comparing the DTC elements in the business data meta information table with the standard dictionary table, When the controller name and fault code meaning are the same, the DTC standard meaning information in the matching DTC standard data in the standard dictionary table is referenced and marked as "reference"; When the controller name and DTC code are the same, the DTC standard meaning information in the matching DTC standard data in the standard dictionary table is borrowed and marked as "pending confirmation"; When at least one of the controller names, DTC codes or fault code meaning elements is the same, the DTC standard meaning information in the matching DTC standard data in the standard dictionary table is borrowed and marked as "to be modified"; When the data metadata information is different, the DTC data is marked as "newly developed"; Step 4: Based on the standardized tasks, create standardized operation rules to complete the creation of reporting factors, signal deviation meanings, signal source information, reporting subjects, signal deviation levels, and severity information to complete DTC data standardization; The standardized operating rules in step 4 are: The DTC standard meaning information marked as "reference" does not need to be modified and can be submitted for review directly; For DTC standard meaning information marked as "to be confirmed" or "to be modified", the recommended DTC standard meaning information is confirmed or modified according to the DTC information processing standard; For those marked as "Newly Developed", create DTC standard meaning information such as reporting factor, signal deviation meaning, signal source information, reporting subject, signal deviation level, and severity based on the basic information of DTC data extracted in step 1; Among them, the "newly developed" DTC information processing standard process is as follows: First, the main body of the reporting code is created: the main body of the reporting code is used to describe the controller information for fault code storage and logical judgment; Secondly, the reporting factor information is created: a reporting factor database is created to store the signal converted by voltage, resistance, and current or the basic physical quantity information specified in the meaning of the fault code; the data processing end selects the signal source-parts information associated with the DTC fault from the vehicle parts database based on the parts information expressed in the meaning of the fault code; Signal source information creation: The data processing end creates signal source-area information based on the non-component, function, and system information expressed in the meaning of the fault code; Signal deviation meaning information creation: Automatically extract the characters used to indicate functional failure or fault phenomenon in the meaning of the fault code; Creation of signal deviation level information: The fault code meaning information extracted from the DTC data is brought in, and the data processing end deletes the fault code meaning information and retains the level information that has been clearly defined in the fault code meaning; Severity information creation: The data processing end creates corresponding severity level information based on the consequences caused by the fault code.

Images