A method for developing automotive DTC fault diagnosis process

Abstract

The present invention provides a method for developing a DTC fault diagnosis process for an automobile. The method constructs a DTC standard database to store basic DTC information and DTC standard meaning information after standardized processing, formulates diagnostic unit coding rules and classification standards for universal diagnostic units and electrical diagnostic units, and constructs a corresponding relationship between a circuit function loop and a DTC of a historically developed vehicle model. By matching the characteristic category code corresponding to the universal diagnostic unit of the vehicle model to be developed with the diagnostic process database, the circuit diagnostic unit code of the vehicle model to be developed, the circuit function loop code to which the circuit diagnostic unit belongs, the connector code, and the information combination of the pin relationship set are matched with the diagnostic process database. The database can be quickly borrowed based on the matching results, and development tasks can be quickly generated for those that cannot be borrowed, thereby realizing automatic matching, identification, and borrowing, reducing manual workload, and at the same time, the borrowed part does not need secondary development, thereby shortening the development time cycle.

Description

Technical Field

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

[0002] With the continuous development of electronic technology, DTC fault diagnosis is also constantly being improved and updated. The traditional DTC fault diagnosis process development is based on manual analysis of possible failure principles in the functional circuit of the vehicle circuit diagram, systematic diagnosis cause analysis, borrowing analysis of historical developed data or new development. However, in the process of DTC fault diagnosis process development, the following problems still exist:

[0003] 1. Although DTC data is a general reference material, it generally serves multiple brands or models. However, when developing DTC diagnostic processes for different brands and models, the workload of manually identifying the borrowing of each DTC diagnostic process is large;

[0004] 2. When different developers perform data analysis, there is a risk of incomplete analysis and inconsistent analysis quality, which will result in unclear results for guiding diagnosis.

[0005] Therefore, how to provide an intelligent, efficient, and shorter development cycle automotive DTC fault diagnosis process development method is an urgent problem that technicians in this field need to solve. Summary of the invention

[0006] The invention provides a method for developing a DTC fault diagnosis process for an automobile, so as to solve the problems of a long development cycle, incomplete analysis and inconsistent quality in the existing DTC fault diagnosis process for an automobile.

[0007] According to one aspect of the present invention, a method for developing a DTC fault diagnosis process for an automobile is provided, comprising the following steps:

[0008] Step 1: Create a DTC standard database to store basic DTC information and standardized DTC standard meaning information; create a diagnostic process database to store diagnostic paths and diagnostic unit information of historically developed vehicle models;

[0009] According to the XML format file of the fault diagnosis manual of the historically developed vehicle model, the vehicle model information, the controller name, the chapter information in each XML file, the diagnosis process name information, and the diagnosis process information are extracted; according to the information of each diagnosis process, the content of each diagnosis step in the diagnosis process is used as a diagnosis unit for information extraction; the order relationship of the names of each diagnosis step is used as a diagnosis path for extraction;

[0010] Standardize the part names contained in the extracted diagnostic unit names; mark the category features of the diagnostic unit and assign category feature codes; formulate diagnostic unit codes based on the category feature codes, part numbers, and circuit function loop name codes of the diagnostic unit; classify the diagnostic unit codes based on the category features of the diagnostic unit and assign feature category codes;

[0011] Create a circuit function loop library to store the information of each circuit function loop in the system schematic diagram, and build the corresponding relationship between the circuit function loop library and the DTC of the historical development model;

[0012] Circuit diagrams and graphics are extracted from the fault diagnosis manuals of historical development models to assist in explaining the DTC fault diagnosis process;

[0013] Create a graphic recognition model to extract the vehicle model, controller name, diagnostic process name, connector code, and pin number from the circuit diagram in SVG format;

[0014] By comparing the connector codes and pin numbers in each circuit function loop created historically with the connector codes and pin numbers extracted from the circuit diagram, the corresponding relationship between the DTC of the historical development vehicle model and the circuit function loop is established;

[0015] Step 2: Develop the diagnostic process for the vehicle model to be developed;

[0016] Step 21, based on the DTC reference data of the vehicle model to be developed, the DTC data is standardized; based on the wiring harness drawing, vehicle schematic diagram, and fuse box schematic diagram of the vehicle model to be developed, the vehicle circuit information is extracted; based on the extracted circuit information, the functional loop information of each circuit in the system schematic diagram associated with the DTC is created; a diagnostic path recommendation model is created, and the recommendation model recommends historical diagnostic paths that can be used for reference;

[0017] Step 22, extracting the diagnostic unit code in each diagnostic path of the vehicle model to be developed, and determining the feature category code to which the diagnostic unit belongs;

[0018] Match the feature category code corresponding to the vehicle model to be developed with the feature category code of the universal diagnostic unit within the brand. For the one that matches the universal one within the brand, retrieve the corresponding brand universal diagnostic unit template through the category feature code. Retrieve the fuse, relay information, and universal component names in the corresponding circuit function loop from the circuit function loop library through the corresponding relationship between the category feature codes, and automatically fill them into the universal diagnostic unit template of the vehicle model to be developed to generate the diagnostic unit of the vehicle model to be developed.

[0019] Match the controller name, DTC standard meaning, and diagnostic unit feature category code of the vehicle to be developed with those of the historically developed vehicles. If there is a match, borrow the corresponding general diagnostic unit content and assign a new diagnostic unit code;

[0020] The diagnostic unit code of the vehicle model to be developed, the circuit function loop code of the diagnostic unit, the connector code, and the pin relationship set are matched with those of the historically developed vehicle models. If there is a match, the diagnostic unit data is directly borrowed.

[0021] Based on the above solution, a circuit function loop library is preferably created to store the circuit function loop information of each circuit in the system schematic diagram, specifically including:

[0022] Extract line information from wiring harness drawings, vehicle schematics, and fuse box schematics of historically developed models. Create and encode circuit function loop names based on the functional principle content and line connection relationships that need to be explained in the system schematics, and store them in the circuit function loop library;

[0023] Based on the component brand name and fuse / relay brand name, create corresponding cross-brand common names and circuit function loop information;

[0024] Components, connector codes, nodes, pin numbers, wire numbers, wire colors, wire diameters, pin functions, fuse / relay names, fuse / relay numbers, and fuse / relay pin numbers are extracted from the line information and stored in corresponding circuit function loops.

[0025] Based on the above solutions, a diagnostic path recommendation model is created. The recommendation model recommends historical diagnostic paths that can be used as reference, including:

[0026] Find the historical diagnostic path with the same DTC information as the vehicle model to be developed. For the same DTC information, match the component number set in the circuit function loop corresponding to the DTC. When the two are 100% matched, recommend the matching diagnostic path; when the two do not match, further match through the component common name set and circuit function loop code set, calculate the similarity of the component number set corresponding to the DTC, and recommend the corresponding diagnostic path;

[0027] For those with different DTC information, the component number set in the circuit function loop corresponding to the DTC is matched. When the two are 100% matched, further matching and recommendation are performed through the signal deviation meaning information in the DTC information. When the two do not match, further matching is performed by searching the function loop code set, and the similarity of the component number set corresponding to the DTC is calculated to recommend the corresponding diagnostic path.

[0028] Based on the above scheme, the component number set similarity calculation model of the DTC corresponding circuit function loop is as follows:

[0029] The similarity of diagnostic paths with the same component common name = the number of function component number sets in each historical diagnostic path that are the same as the function component number sets to which the target vehicle model DTC belongs / the number of function component number sets to which the target vehicle model DTC belongs.

[0030] Based on the above scheme, the controller name, DTC standard meaning, and diagnostic unit feature category code information combination of the vehicle model to be developed are matched with those of the historically developed vehicle models. When there is no match, a corresponding universal diagnostic unit is newly developed based on reference materials.

[0031] Based on the above scheme, it is preferred to match the information combination of the diagnostic unit code of the vehicle model to be developed, the circuit function loop code of the diagnostic unit, the connector code, and the pin relationship set with the historically developed vehicle models. If there is a match, its diagnostic unit data is directly borrowed; and when borrowing, first the same development platform is used, and then the latest data is uploaded across platforms.

[0032] Preferably, based on the above scheme, the information combination of the diagnostic unit code of the vehicle model to be developed, the circuit function loop code to which the diagnostic unit belongs, the connector code, and the pin relationship set is matched with the vehicle models that have been developed historically. When there is no match, the circuit function loop code corresponding to the diagnostic unit code is extracted, and the connector code and pin relationship extracted from the corresponding circuit function loop are used to develop the corresponding circuit diagnostic unit according to the electrical diagnostic unit template.

[0033] The present invention provides a method for developing a DTC fault diagnosis process for an automobile. The method constructs a DTC standard database to store basic DTC information and standard meaning information of DTCs after standardization. The method combines the established diagnosis process database and circuit function loop library to construct a corresponding relationship between the circuit function loop library and the DTC of historically developed vehicle models. By matching the feature category code corresponding to the vehicle model to be developed with the feature category code of the universal diagnostic unit within the brand, the database that can be borrowed can be quickly borrowed according to the matching result, and the development task that cannot be borrowed can be quickly generated, thereby realizing automatic matching, identification and borrowing. This not only reduces the manual workload, but also makes the machine automatic identification and analysis more comprehensive and the analysis quality more stable. At the same time, the borrowed part does not need secondary development, thereby shortening the development time cycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] 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:

[0035] Figure 1 A flowchart of a method for developing a DTC fault diagnosis process for an automobile according to the present invention;

[0036] Figure 2 A flowchart for extracting elements of the diagnostic manual of historically developed vehicle models of the present invention to form a database;

[0037] Figure 3 A flowchart created for the relationship between the DTC and circuit function loops of the historical development vehicle model of the present invention. DETAILED DESCRIPTION

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

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

[0040] 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".

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

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

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

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

[0045] See also Figure 1 , and combined with Figure Figure 2 and Figure 3 As shown, a method for developing a vehicle DTC fault diagnosis process of the present invention specifically includes extracting elements of diagnostic manuals of historically developed vehicle models to form a database; retrieving data of a vehicle model to be developed and comparing it with the database to determine whether the diagnostic process of the vehicle model to be developed is to be developed or borrowed.

[0046] Among them, the elements of the diagnostic manual of historically developed models are extracted to form a database, including:

[0047] Step A1, DTC standardization processing;

[0048] A DTC standard database is created to store basic DTC information and standardized DTC standard meaning information.

[0049] Based on the DTC reference data of each controller of the development vehicle model, the basic information of DTC data is extracted, where the basic information of DTC data includes DTC code, sub-product system to which the DTC code belongs, controller name, controller supplier, controller version, and fault code meaning.

[0050] Based on the extracted basic information of DTC data, DTC standard meaning information is created to complete the standardization of DTC data.

[0051] Among them, the meaning of DTC standard includes:

[0052] Reporting factor (used to store signals converted by voltage, resistance, and current (such as temperature, rainfall position, liquid level, speed signal, etc.) or basic physical quantities specified in the meaning of the fault code);

[0053] Signal deviation meaning (characters used to indicate functional failure or fault phenomenon in the meaning of the fault code); signal source information (based on the component information expressed in the meaning of the fault code, create the signal source-part information associated with the DTC fault; based on the non-component, function, and system information expressed in the meaning of the fault code, create the signal source-area information);

[0054] Report code body (controller information used to describe fault code storage and perform logical judgment);

[0055] Signal deviation level (level information is clearly stated in the meaning of the fault code);

[0056] Severity (the severity of the consequences caused by the fault code).

[0057] Step A2, extracting diagnostic path and diagnostic unit information;

[0058] Create a diagnostic process database to store diagnostic paths and diagnostic unit information of historically developed vehicle models.

[0059] Based on the XML format files of the fault diagnosis manuals of historically developed vehicles, vehicle model information, controller name, chapter information in each XML file, and diagnostic process name information and diagnostic process information are extracted.

[0060] According to the information of each diagnostic process, the content of each diagnostic step in the diagnostic process is used as a diagnostic unit for information extraction; the sequence relationship of the names of each diagnostic step is used as a diagnostic path for extraction.

[0061] Standardize the names of parts (electrical components or mechanical parts) contained in the extracted diagnostic unit names (i.e., create a common name that is common across brands); mark the category characteristics of the diagnostic unit and assign category characteristic codes; formulate the diagnostic unit code based on the category characteristic code, part number, and circuit function loop name code of the diagnostic unit.

[0062] The diagnostic units are classified according to their category characteristics. The diagnostic units that can be used in the same vehicle brand and the diagnostic units with the same DTC code in the same brand are defined as universal diagnostic units (i.e. diagnostic units that are not related to component information); those that cannot be used in the same vehicle brand are classified as electrical diagnostic units.

[0063] Among them, the common diagnostic unit types include the following:

[0064] 1. Common diagnostic unit feature type code within the brand:

[0065] Insurance Check – EQBXTD;

[0066] Relay inspection – EQJQTD;

[0067] Parts replacement elimination method – JDTD;

[0068] 2. Same DTC code within the brand, common diagnostic unit characteristic type code:

[0069] DTC confirmation – QRMRTD;

[0070] Symptom confirmation – QRZZTD;

[0071] Fault code priority - QRBCTD;

[0072] Code clearing confirmation——YZTD;

[0073] Step A3, creating the relationship between the DTC of the historical development model and the circuit function loop;

[0074] Step A3.1, circuit function loop creation;

[0075] Create a circuit function loop library to store the circuit function loop information in the system schematic diagram.

[0076] Extract line information from the wiring harness drawings, vehicle schematics, fuse box schematics and other materials of historically developed models, create and encode circuit function loop names based on the functional principle content and line connection relationships that need to be explained in the system schematic. Extract element information such as components, connector codes, nodes, pin numbers, wire numbers, wire colors, wire diameters, pin functions, fuse / relay names, fuse / relay numbers, and fuse / relay pin numbers from the line information and store them in the corresponding circuit function loops; create corresponding cross-brand common names based on component brand names and fuse / relay brand names to complete the creation of circuit function loop information.

[0077] Step A3.2, creating the correspondence between the DTC of the historical development vehicle model and the circuit function loop;

[0078] Extract the circuit diagram graphics used to assist in explaining the DTC fault diagnosis process from the fault diagnosis manual of the historical development model. Create a graphic recognition model to extract the model, controller name, diagnosis process name, connector code, and pin number from the circuit diagram graphics in SVG format.

[0079] By comparing the connector codes and pin numbers in each historically created circuit function loop with the connector codes and pin numbers extracted from the circuit diagram, a correspondence between the DTC of the historically developed vehicle model and the circuit function loop is established.

[0080] The development of the diagnostic process of the vehicle model to be developed in the present invention specifically includes:

[0081] Step B1, diagnostic pathway development;

[0082] Based on the DTC reference materials of the vehicle to be developed, the DTC data is standardized; based on the wiring harness drawings, vehicle schematics, and fuse box schematics of the vehicle to be developed, the vehicle circuit information is extracted. Based on the extracted circuit information, the functional loop information of each circuit in the system schematic associated with the DTC is created.

[0083] Create a diagnostic path recommendation model. The recommendation model recommends historical diagnostic paths that can be used as reference. The specific recommendation rules are as follows:

[0084] Step B11, searching for the same historical diagnostic path as the DTC information of the vehicle model to be developed (i.e., the combination of DTC code, controller name, sub-product system, reporting factor, reporting subject, signal source, signal deviation meaning, etc.).

[0085] For DTCs with the same information, the component number set in the circuit function loop corresponding to the DTC is matched. If a complete match exists, the completely matched diagnostic path is recommended. If not, further matching is performed through the component common name set and the circuit function loop code set, and the similarity of the component number set corresponding to the DTC is calculated to recommend the corresponding diagnostic path.

[0086] Step B12, for DTC information that is different, directly match the component number set in the circuit function loop corresponding to the DTC. If a complete match exists, further match and recommend it through the signal deviation meaning information in the DTC information; if not, further match it by searching the circuit function loop code set, and calculate the similarity of the component number set corresponding to the DTC, and recommend the corresponding diagnostic path.

[0087] When recommending, priority is given to diagnostic paths with high similarity. If there are paths with the same similarity, priority is given to diagnostic paths with more diagnostic steps. The recommended diagnostic paths under different matching methods are marked with status, and corresponding diagnostic path development tasks are established for each path.

[0088] Adjust the recommended diagnostic paths under different matching methods, recognize the characters in the names of each diagnostic unit in the diagnostic path, automatically mark the category characteristics of the diagnostic units, generate diagnostic unit codes, and complete the development of the diagnostic path for the vehicle model to be developed.

[0089] Among them, the component number set similarity calculation model of the circuit function loop corresponding to DTC is as follows:

[0090] The similarity of diagnostic paths with the same component common name = the number of function component number sets in each historical diagnostic path that are the same as the function component number sets to which the target vehicle model DTC belongs / the number of function component number sets to which the target vehicle model DTC belongs.

[0091] Step B2, retrieve the data of the vehicle model to be developed and compare it with the database to determine whether to develop or borrow the diagnostic process of the vehicle model to be developed;

[0092] Step B21, development of content for universal diagnostic units within the brand;

[0093] Identify the diagnostic unit code in each diagnostic path of the vehicle to be developed, determine the characteristic category code to which the diagnostic unit belongs, and match the corresponding characteristic category code with the common diagnostic unit characteristic category code within the brand. For the matching that is common within the brand, the corresponding brand common diagnostic unit template is retrieved through the category characteristic code, and the fuse, relay information, and component common names in the corresponding circuit function loop are retrieved from the circuit function loop library through the category characteristic code correspondence relationship "fuse inspection - EQBXTD, relay inspection - EQJQTD, parts replacement elimination method - JDTD", and automatically filled in the common diagnostic unit template of the vehicle to be developed to generate the diagnostic unit of the vehicle to be developed.

[0094] Step B22, common diagnostic unit content development for the same DTC code;

[0095] Identify the diagnostic unit codes in each diagnostic path of the vehicle to be developed, determine the characteristic category code to which the diagnostic unit belongs, and match the corresponding characteristic category code with the common diagnostic unit characteristic category code within the brand. Match the controller name, DTC standard meaning, and diagnostic unit characteristic category code of the vehicle to be developed with the historical developed vehicle models. If there is a match, directly borrow the corresponding common diagnostic unit content and assign a new diagnostic unit code; if there is no match, directly develop the corresponding common diagnostic unit based on the reference material.

[0096] Step B23, circuit diagnosis unit development;

[0097] Extract the diagnostic unit codes in each diagnostic path of the vehicle to be developed, and match the diagnostic unit codes of the vehicle to be developed, the circuit function loop codes to which the diagnostic unit belongs, the connector codes, and the pin relationship set with those of the historically developed vehicles. For matches, directly borrow their diagnostic unit data. When borrowing, give priority to the latest uploaded data on the same development platform, and secondly, cross-platform data; for no matches, extract the circuit function loop codes corresponding to the diagnostic unit codes, and according to the electrical diagnostic unit template, extract the connector codes and pin relationships from the corresponding circuit function loops to develop the corresponding circuit diagnostic unit.

[0098] In order to explain the technical solution of the present invention in detail, the DTC standardization processing method in step A1 of the present invention will be introduced in detail below, and its specific steps are as follows:

[0099] Step 1: Standardize DTC data of the vehicle model to be developed; Step 2: Extract fault diagnosis element information of historical vehicle models; Step 3: Recommend the relationship between DTC and functional circuit of the vehicle model to be developed; Step 4: Construct the correspondence between DTC and system schematic diagram; Step 5: Check the fault circuit.

[0100] Among them, step 1 is to standardize the DTC data of the vehicle to be developed, which specifically includes:

[0101] According to the DTC reference materials of the vehicle model to be developed, the basic information of DTC data is extracted from the DTC reference materials, where the basic information of DTC data specifically includes DTC code, sub-product system, controller name, controller supplier, controller version, and fault code meaning.

[0102] Based on the extracted basic information of DTC data, DTC standard meaning information is created, where the DTC standard meaning information includes: reporting factor (used to store signals converted by voltage, resistance, and current as specified in the fault code meaning (for example: temperature, rainfall position, liquid level, speed signal, etc.) or basic physical quantities as specified in the fault code meaning), signal deviation meaning (characters used to indicate functional failure or fault phenomenon in the fault code meaning), signal source information (non-component, function, and system information described in the fault code meaning); reporting subject (controller information used to explain fault code storage and perform logical judgment), signal deviation level (level information specified in the fault code meaning) and severity (level of severity of consequences caused by the fault code), thus completing the standardized processing of DTC data.

[0103] Step 2, extracting the fault diagnosis factor information of historical vehicle models;

[0104] Create a fault circuit library to store vehicle model information, controller name, diagnostic process name, functional circuit information (extracted from wiring harness drawings, vehicle electrical schematics, fuse box schematics and other materials, including all component information, connector information, wiring harness information, fuse / relay information and other elements used to realize a certain electrical function on the vehicle, as well as current / signal direction information in the functional circuit), DTC standard data, circuit diagrams and other information extracted from historically developed vehicle model fault diagnosis manuals.

[0105] Create the correspondence between DTC standard data and functional circuits from historical development vehicle fault diagnosis.

[0106] Step 3: Recommend the relationship between DTC and functional circuit of the vehicle model to be developed;

[0107] Create an electrical function circuit library to store the information of each function circuit in the system schematic diagram.

[0108] During the system schematic development process, the first-level function name and the second-level function name under the first-level function split are defined according to the functional principle content to be explained and the necessity of functional split description.

[0109] According to the primary function name or the secondary function name, the names of the functional circuits contained in the primary function name or the secondary function name and their information are created respectively (i.e., based on the wiring harness drawing, the vehicle schematic, the fuse box schematic and other materials, all the component information (part number, part name), connector information (connector coding, pin number, pin function), wiring harness information (wire number, wire color, wire diameter), fuse / relay information (fuse / relay name, number, fuse / relay pin number) and other elements used to realize a certain electrical function on the vehicle are extracted, as well as the current / signal direction information in the functional circuit).

[0110] Establish the association logic between the function loop name and the function loop graphic elements in the system schematic diagram.

[0111] Step 4: Establish the correspondence between DTC standard data and system schematic diagram;

[0112] Create a function circuit search rule. First, use the standard meaning information of the DTC of the model to be developed to search for all function circuit sets corresponding to the DTC with the same standard meaning in the fault circuit library. Then, match the found function circuit with the function circuit information created for the model to be developed to determine the correspondence between the model to be developed and the function circuit. The specific search rules are as follows:

[0113] 1) By combining the controller name, sub-product system, reporting factor, reporting subject, signal source-part / area, signal deviation meaning and other elements in the DTC standard meaning information of the model to be developed, first match and search for the functional circuit set with the same DTC standard data elements in the fault circuit library within the same brand, and then search across brands;

[0114] 2) Extract the vehicle model information, the function circuit name, the part name in the function circuit, the part number, the pin function set, the connector code and the pin relationship set and other information sets from the function circuit of the vehicle model to be developed created in step 2.2;

[0115] The information set extracted from the functional circuit of the vehicle to be developed is further matched with the functional circuit information of the DTC with the same standard meaning matched and found in 1) to determine the corresponding relationship between the vehicle to be developed and the functional circuit.

[0116] Based on the correspondence between the DTC standard data and the functional circuits of the vehicle to be developed, and the correspondence between the primary function names, secondary function names and the functional circuits contained in the system schematic diagram, the correspondence between the DTC standard data, the functional circuit names and the system schematic diagram of the vehicle to be developed is established;

[0117] When checking the fault circuit where the DTC is located, check the correspondence between the DTC standard data, functional circuit name, and system schematic diagram created in the interface, automatically call up the system schematic diagram graphic associated with the DTC data, and light up the graphic elements of the fault circuit where each DTC is located in the system schematic diagram (the fault circuit is composed of one or more functional circuit information. When multiple functional circuit information is combined, duplicate line information is de-duplicated and merged) to assist in completing DTC fault diagnosis.

[0118] Among them, when the DTC corresponding fault circuit involves multiple system schematic diagrams, the system schematic diagram with the largest number of functional circuits in the DTC corresponding fault circuit will be displayed in the center as the main diagram, and other system schematic diagrams will be reduced to sub-diagrams for display. The position relationship between each sub-diagram and the main diagram is arranged according to the position relationship between the components included in the functional circuit and the components of the main diagram. Click the sub-diagram to switch to view the complete fault circuit of DTC.

[0119] Compared with the prior art, the present invention provides a method for developing a DTC fault diagnosis process for an automobile, constructs a DTC standard database to store basic DTC information and standard meaning information of DTCs after standardization, combines the established diagnostic process database and circuit function loop library, constructs a correspondence between the circuit function loop library and the DTC of historically developed vehicle models, and matches the feature category code corresponding to the vehicle model to be developed with the feature category code of the universal diagnostic unit within the brand, and can quickly borrow from the database based on the matching results, and quickly generate development tasks for those that cannot be borrowed, thereby realizing automatic matching, identification and borrowing, which not only reduces manual workload, but also makes machine automatic identification and analysis more comprehensive and the analysis quality more stable; at the same time, the borrowed part does not need secondary development, thereby shortening the development time cycle.

[0120] 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 developing a DTC fault diagnosis process for an automobile, characterized in that: The following steps are included: Step 1, create a DTC standard database for storing DTC basic information and standardized DTC standard meaning information; Create a diagnostic process database to store diagnostic paths and diagnostic unit information of historically developed vehicle models; According to the XML format file of the fault diagnosis manual of the historically developed vehicle model, the vehicle model information, the controller name, the chapter information in each XML file, the diagnosis process name information, and the diagnosis process information are extracted; according to the information of each diagnosis process, the content of each diagnosis step in the diagnosis process is used as a diagnosis unit for information extraction; the order relationship of the names of each diagnosis step is used as a diagnosis path for extraction; Standardize the part names contained in the extracted diagnostic unit names; mark the category features of the diagnostic unit and assign category feature codes; formulate diagnostic unit codes based on the category feature codes, part numbers, and circuit function loop name codes of the diagnostic unit; classify the diagnostic unit codes based on the category features of the diagnostic unit and assign feature category codes; Create a circuit function loop library to store the information of each circuit function loop in the system schematic diagram, and build the corresponding relationship between the circuit function loop library and the DTC of the historical development model; Circuit diagrams and graphics are extracted from the fault diagnosis manuals of historical development models to assist in explaining the DTC fault diagnosis process; Create a graphic recognition model to extract the vehicle model, controller name, diagnostic process name, connector code, and pin number from the circuit diagram in SVG format; By comparing the connector codes and pin numbers in each circuit function loop created historically with the connector codes and pin numbers extracted from the circuit diagram, the corresponding relationship between the DTC of the historical development vehicle model and the circuit function loop is established; Step 2: Develop the diagnostic process for the vehicle model to be developed; Step 21, standardizing the DTC data according to the DTC reference data of the vehicle model to be developed; Extract vehicle wiring information based on the wiring harness drawings, vehicle schematics, and fuse box schematics of the vehicle model to be developed; create functional loop information of each circuit in the system schematic associated with DTC based on the extracted wiring information; create a diagnostic path recommendation model, which recommends historical diagnostic paths that can be used as reference; Step 22, extracting the diagnostic unit code in each diagnostic path of the vehicle model to be developed, and determining the feature category code to which the diagnostic unit belongs; Match the feature category code corresponding to the vehicle model to be developed with the feature category code of the universal diagnostic unit within the brand. For the one that matches the universal one within the brand, retrieve the corresponding brand universal diagnostic unit template through the category feature code. Retrieve the fuse, relay information, and universal component names in the corresponding circuit function loop from the circuit function loop library through the corresponding relationship between the category feature codes, and automatically fill them into the universal diagnostic unit template of the vehicle model to be developed to generate the diagnostic unit of the vehicle model to be developed. Match the controller name, DTC standard meaning, and diagnostic unit feature category code of the vehicle to be developed with those of the historically developed vehicles. If there is a match, borrow the corresponding general diagnostic unit content and assign a new diagnostic unit code; The diagnostic unit code of the vehicle model to be developed, the circuit function loop code of the diagnostic unit, the connector code, and the pin relationship set are matched with those of the historically developed vehicle models. If there is a match, the diagnostic unit data is directly borrowed.

2. The method for developing a DTC fault diagnosis process for an automobile according to claim 1, characterized in that: Create a circuit function loop library to store the information of each function loop in the system schematic diagram, including: Extract line information from wiring harness drawings, vehicle schematics, and fuse box schematics of historically developed models. Create and encode circuit function loop names based on the functional principle content and line connection relationships that need to be explained in the system schematics, and store them in the circuit function loop library; Based on the component brand name and fuse / relay brand name, create corresponding cross-brand common names and circuit function loop information; Components, connector codes, nodes, pin numbers, wire numbers, wire colors, wire diameters, pin functions, fuse / relay names, fuse / relay numbers, and fuse / relay pin numbers are extracted from the line information and stored in corresponding circuit function loops.

3. A method for developing an automobile DTC fault diagnosis process as claimed in claim 2, characterized in that: Create a diagnostic pathway recommendation model. The recommendation model recommends historical diagnostic pathways that can be used as reference, including: Find the historical diagnostic path with the same DTC information as the vehicle model to be developed. For the same DTC information, match the component number set in the circuit function loop corresponding to the DTC. When the two are 100% matched, recommend the matching diagnostic path; when the two do not match, further match through the component common name set and circuit function loop code set, calculate the similarity of the component number set corresponding to the DTC, and recommend the corresponding diagnostic path; For DTCs with different information, the component number set in the circuit function loop corresponding to the DTC is matched. When the two are 100% matched, further matching and recommendation are performed through the signal deviation meaning information in the DTC information. When the two do not match, further matching is performed by searching the circuit function loop coding set, and the similarity of the component number set corresponding to the DTC is calculated to recommend the corresponding diagnostic path.

4. The method for developing a DTC fault diagnosis process for an automobile as claimed in claim 3, characterized in that: The similarity calculation model of the component number set of the DTC corresponding circuit function loop is: The similarity of diagnostic paths with the same component common name = the number of function component number sets in each historical diagnostic path that are the same as the function component number sets to which the target vehicle model DTC belongs / the number of function component number sets to which the target vehicle model DTC belongs.

5. The method for developing a DTC fault diagnosis process for an automobile according to claim 1, characterized in that: The controller name, DTC standard meaning, and diagnostic unit feature category code of the vehicle model to be developed are matched with those of the historically developed vehicle models. When no match exists, a corresponding universal diagnostic unit is newly developed based on reference materials.

6. The method for developing a DTC fault diagnosis process for an automobile according to claim 1, characterized in that: The diagnostic unit code, circuit function loop code, connector code, and pin relationship set of the vehicle model to be developed are matched with those of the historically developed vehicles. If there is a match, the diagnostic unit data is directly borrowed; when borrowing, first upload the latest data on the same development platform and then across platforms.

7. The method for developing a DTC fault diagnosis process for an automobile as claimed in claim 6, characterized in that: The diagnostic unit code, the circuit function loop code, the connector code, and the pin relationship set of the vehicle model to be developed are matched with those of the historically developed vehicles. When there is no match, the circuit function loop code corresponding to the diagnostic unit code is extracted, and the connector code and pin relationship extracted from the corresponding circuit function loop are used to develop the corresponding circuit diagnostic unit according to the electrical diagnostic unit template.

Images