CN112445816A - Vehicle diagnostic data reference method and device, terminal equipment and storage medium - Google Patents

Vehicle diagnostic data reference method and device, terminal equipment and storage medium Download PDF

Info

Publication number
CN112445816A
CN112445816A CN202011266848.0A CN202011266848A CN112445816A CN 112445816 A CN112445816 A CN 112445816A CN 202011266848 A CN202011266848 A CN 202011266848A CN 112445816 A CN112445816 A CN 112445816A
Authority
CN
China
Prior art keywords
diagnostic
layer
identification information
diagnostic data
objects
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202011266848.0A
Other languages
Chinese (zh)
Other versions
CN112445816B (en
Inventor
刘均
邓蒙召
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Launch Technology Co Ltd
Original Assignee
Shenzhen Launch Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Launch Technology Co Ltd filed Critical Shenzhen Launch Technology Co Ltd
Priority to CN202011266848.0A priority Critical patent/CN112445816B/en
Publication of CN112445816A publication Critical patent/CN112445816A/en
Application granted granted Critical
Publication of CN112445816B publication Critical patent/CN112445816B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/289—Object oriented databases

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Stored Programmes (AREA)
  • Testing And Monitoring For Control Systems (AREA)

Abstract

The application is applicable to the technical field of vehicles, and provides a vehicle diagnosis data quoting method, a device and terminal equipment, which comprise the following steps: acquiring a diagnosis instruction, and determining a target ECU and target identification information, wherein the target ECU is the ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnostic data object to be quoted when the target ECU is diagnosed; determining an EV layer diagnosis object corresponding to the target ECU according to the target ECU; and traversing each layer of diagnostic objects according to a preset sequence from the EV layer diagnostic object until the diagnostic data object which is consistent with the target identification information is found out to be used as the diagnostic data object to be quoted, and returning the information of the diagnostic data object to be quoted. The embodiments of the present application enable cross-diagnostic-layer diagnostic data object referencing.

Description

Vehicle diagnostic data reference method and device, terminal equipment and storage medium
Technical Field
The application belongs to the technical field of vehicles, and particularly relates to a vehicle diagnosis data reference method, a vehicle diagnosis data reference device, terminal equipment and a storage medium.
Background
Open Diagnostic Data Exchange (ODX) specifies a standard Diagnostic Data format in the automobile Diagnostic industry, and when a Diagnostic apparatus diagnoses automobiles of different automobile types or different Electronic Control Units (ECUs), only an ODX source file adapted to the automobile type or the ECU needs to be loaded, and the Diagnostic apparatus does not need to be changed.
At present, each diagnostic data object in an ODX source file exists in each hierarchical file, and when a diagnostic apparatus calls the diagnostic data object based on the ODX source file, the diagnostic data object can only be searched based on a single diagnostic layer, and this search mode often has a case that the reference of the diagnostic data object fails.
Disclosure of Invention
In view of this, embodiments of the present application provide a vehicle diagnostic data referencing method, apparatus, terminal device and storage medium, so as to solve the problem in the prior art how to effectively reference a diagnostic data object.
A first aspect of an embodiment of the present application provides a vehicle diagnostic data referencing method, including:
acquiring a diagnosis instruction, and determining a target ECU and target identification information, wherein the target ECU is the ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnostic data object to be quoted when the target ECU is diagnosed;
determining an EV layer diagnosis object corresponding to the target ECU according to the target ECU;
and traversing each layer of diagnostic objects according to a preset sequence from the EV layer diagnostic object until the diagnostic data object which is consistent with the target identification information is found out to be used as the diagnostic data object to be quoted, and returning the information of the diagnostic data object to be quoted.
Optionally, traversing each layer of diagnostic objects according to a preset order from the EV layer diagnostic object includes at least:
traversing the EV-level diagnostic object;
and traversing all SD layer diagnostic objects if the diagnostic data objects consistent with the target identification information do not exist in the EV layer diagnostic objects.
Optionally, after said traversing all SD layer diagnostic objects, further comprising:
and traversing the BV layer diagnostic object inherited by the EV layer diagnostic object if all the SD layer diagnostic objects do not have the diagnostic data object conforming to the target identification information.
Optionally, after traversing the BV layer diagnostic object inherited by the EV layer diagnostic object, further comprising:
and traversing all PR layer diagnostic objects if the BV layer diagnostic object does not have a diagnostic data object which is consistent with the target identification information.
Optionally, after the traversing all PR layer diagnostic objects, further comprising:
and traversing the FG layer diagnostic object inherited by the BV layer diagnostic object if all the PR layer diagnostic objects do not have the diagnostic data object which is consistent with the target identification information.
Optionally, after traversing the BV layer diagnostic object inherited by the EV layer diagnostic object, further comprising:
traversing a first PR layer diagnostic object referenced in the BV layer diagnostic object if the BV layer diagnostic object does not have a diagnostic data object consistent with the target identification information;
if the first PR layer diagnosis object does not have a diagnosis data object which is consistent with the target identification information, traversing the FG layer diagnosis object inherited by the BV layer diagnosis object;
and traversing a second PR layer diagnostic object referenced in the FG layer diagnostic object if the FG layer diagnostic object does not have a diagnostic data object consistent with the target identification information.
Optionally, the identification information is unique identification number or name information included in the open diagnostic data exchange ODX data.
A second aspect of an embodiment of the present application provides a vehicle diagnostic data referencing device, including:
the system comprises an acquisition unit, a diagnosis unit and a processing unit, wherein the acquisition unit is used for acquiring a diagnosis instruction and determining a target ECU and target identification information, the target ECU is the ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnostic data object to be quoted when the target ECU is diagnosed;
the EV layer diagnostic object determining unit is used for determining an EV layer diagnostic object corresponding to the target ECU according to the target ECU;
and the searching unit is used for traversing all layers of diagnostic objects according to a preset sequence from the EV layer diagnostic object until the diagnostic data object which is consistent with the target identification information is found out to be used as the diagnostic data object to be quoted, and returning the information of the diagnostic data object to be quoted.
Optionally, the search unit includes:
a first traversal module to traverse the EV-level diagnostic object; and traversing all SD layer diagnostic objects if the diagnostic data objects consistent with the target identification information do not exist in the EV layer diagnostic objects.
Optionally, the search unit further includes:
and the second traversal module is used for traversing the BV layer diagnostic object inherited by the EV layer diagnostic object if all the SD layer diagnostic objects do not have the diagnostic data object which is consistent with the target identification information.
Optionally, the search unit further includes:
and the third traversal module is used for traversing all the PR layer diagnostic objects if the BV layer diagnostic object does not have a diagnostic data object which is consistent with the target identification information.
Optionally, the search unit further includes:
and the fourth traversal module is used for traversing the FG layer diagnostic object inherited by the BV layer diagnostic object if all the PR layer diagnostic objects do not have the diagnostic data object which is consistent with the target identification information.
Optionally, the search unit further includes a fifth traversal module, a sixth traversal module, and a seventh traversal module:
a fifth traversal module, configured to traverse a first PR layer diagnostic object referenced in the BV layer diagnostic object if the BV layer diagnostic object does not have a diagnostic data object that matches the target identification information;
a sixth traversal module, configured to traverse an FG-layer diagnostic object inherited by the BV-layer diagnostic object if the first PR-layer diagnostic object does not have a diagnostic data object that matches the target identification information;
and the seventh traversing module is used for traversing a second PR layer diagnostic object quoted in the FG layer diagnostic object if the diagnostic data object which is consistent with the target identification information does not exist in the FG layer diagnostic object.
Optionally, the identification information is unique identification number or name information included in the open diagnostic data exchange ODX data.
A third aspect of the embodiments of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, which when executed by the processor, causes the terminal device to implement the steps of the vehicle diagnostic data referencing method as described.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium storing a computer program which, when executed by a processor, causes a terminal device to implement the steps of the vehicle diagnostic data referencing method as described.
A fifth aspect of embodiments of the present application provides a computer program product, which, when run on a terminal device, causes the terminal device to execute the steps of the vehicle diagnostic data referencing method according to any one of the first aspects described above.
Compared with the prior art, the embodiment of the application has the advantages that: in the embodiment of the application, after the target ECU and the target identification information are determined by the obtained diagnosis instruction and the corresponding EV layer diagnosis object is determined according to the target ECU, all layers of diagnosis objects can be traversed from the EV layer diagnosis object according to the preset sequence until the diagnosis data object to be quoted is found, and compared with the mode that the existing diagnosis instrument can only find the diagnosis data object to be quoted in a single layer diagnosis object, the success rate of finding the diagnosis data object to be quoted can be improved, so that the reference of the diagnosis data object is effectively realized.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
FIG. 1 is a schematic diagram illustrating an application scenario of vehicle diagnostic data referencing according to an embodiment of the present application;
FIG. 2 is a schematic view of a diagnostic slice configuration provided by an embodiment of the present application;
FIG. 3 is a schematic diagram of an EV layer file provided in an embodiment of the present application;
FIG. 4 is a schematic diagram of a record of data reference source information in a diagnostic layer file according to an embodiment of the present application;
FIG. 5 is an exemplary diagram of a vehicle diagnostic data referencing method provided by an embodiment of the present application;
FIG. 6 is a schematic diagram of a vehicle diagnostic data referencing device provided by an embodiment of the present application;
fig. 7 is a schematic diagram of a terminal device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In addition, in the description of the present application, the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
Fig. 1 shows a schematic application scenario diagram corresponding to the vehicle diagnostic data referencing method in the embodiment of the present application, including a diagnostic apparatus 11 and a vehicle 12. When the diagnostic device 11 needs to perform vehicle diagnosis On the vehicle 12, the diagnostic device 11 is connected to an On-Board Diagnostics (OBD) interface 121 of the vehicle 12, loads an ODX source file provided by a manufacturer of the vehicle 12, parses the ODX source file, and creates a corresponding diagnostic data object (e.g., C + + object) for each diagnostic data of the ODX source file. And then, by referring to the diagnostic data object in the diagnostic instrument program, the reference to the diagnostic data can be realized.
The ODX source files include multiple ODX source files corresponding to different ECUs in different hierarchies. Specifically, as shown in fig. 2, the diagnostic layers in the ODX source file may include five diagnostic layers, specifically four from top to bottom (from general to specific), by hierarchical classification: a PROTOCOL (PR) layer, a FUNCTIONAL-GROUP (FG) layer, a basic-variable (BV) layer, a specific electronic control unit variable (ECU-VARIANT, EV) layer; and also includes a SHARED DATA (ECU-SHARED-DATA, SD) layer. Wherein:
the PR layer defines a Diagnostic application layer Protocol, such as a Controller Area Network (CAN) Protocol, a Keyword Protocol (KWP), a Network Diagnostic communication Protocol (DOIP), a vehicle-mounted Network standard Protocol (Flexray), or an Ethernet Protocol (Ethernet).
The FG layer defines a functional group diagnostic service or data that is commonly supported by a plurality of ECUs.
The BV layer represents the diagnostic data type of the ODX database for the basic variable type of a particular ECU, and in each vehicle model, each ECU has only one BASE-value file that can be inherited from PROTOCOL or FUNCTIONAL-GROUP, can contain references to diagnostic services and data in the upper two diagnostic layers, and can modify the inherited services and data.
The EV layer is a specific implementation of each ECU. For example, in a complete ODX source package (PACKAGED ODX DATA, PDX), there is only one engine BASE-VARIANT file, but the engine may have different versions of configuration such as 1.4, 1.6, etc., and engine ECUs with different configurations have different diagnostic DATA, which are embodied in the ECU-VARIANT.
The SD layer is a database that defines the general data types, which are referenced by the above 4 diagnostic layer files.
Illustratively, for a PDX package for a vehicle model, the PR layer includes the following files: DLC _ PR _ CAN.odx-d, DLC _ PR _ Ethernet.odx-d, DLC _ PR _ Flexray.odx-d, etc.; FG layers include files such as: DLC _ FG _ can.odx-d, DLC _ FG _ ethernet.odx-d, DLC _ FG _ flexray.odx-d, etc.; the BV layer includes files: DLC _ BV _ AC.odx-d, DLC _ BV _ ACU.odx-d, DLC _ BV _ BCM.odx-d, DLC _ BV _ EGSM.odx-d, DLC _ BV _ EMS.odx-d, DLC _ BV _ EPS.odx-d and other basic variable files of each ECU; the EV layer includes files: DLC _ EV _ AC.odx-d, DLC _ EV _ ACU.odx-d, DLC _ EV _ BCM.odx-d, DLC _ EV _ EGSM.odx-d, DLC _ EV _ EMS.odx-d, DLC _ EV _ EPS.odx-d and other specific implementation files of each ECU; the SD layer includes files: DLC _ SD _ dop.odx-d, DLC _ SD _ uds.odx-d, DLC _ SD _ units.odx-d, etc.
Specifically, each of the ODX source files is an XML format file, and different types of diagnostic data in a single ODX source file are encapsulated by XML tags; the ODX source files of all the diagnosis layers are correspondingly analyzed into diagnosis data objects at a diagnosis layer level, which are called diagnosis layer diagnosis objects for short; and each diagnostic data in a single ODX source file is further parsed into each diagnostic data object below the class object. For example, for the EV layer file DLC _ EV _ ems.odx-d corresponding to the Engine Management System (EMS), the diagnostic device resolves it into an EV layer diagnostic object named EV _ EMS, and each diagnostic data in DLC _ EV _ ems.odx-d is resolved into each diagnostic data object in the EV layer diagnostic object one by one. Illustratively, as shown in fig. 3, the root node of the DLC _ EV _ ems.odx-d file is parsed into one EV layer diagnostic object named EV _ EMS by ECU _ VRAIANT, which is short named EV _ EMS, and the respective diagnostic DATA DIAG-DATA-diagnostic-SPEC, DTC-DOPS, DTC-DOP, DTCs, etc., nested in stages below the ECU _ VRAIANT, are parsed into the respective diagnostic DATA objects below the EV diagnostic object one by one. Wherein ECU-VARIANT represents a specialized ECU object; DIAG-DATA-DICTIONARY-SPEC represents a diagnostic DATA DICTIONARY set containing various simple and complex DOP sets (DATA Object Property, which can be simply understood as DATA related to an algorithm) referred to by other diagnostic parameters, and participates in calculating the original DATA returned by the ECU, and the physical values are displayed on a user interface; DTCs (diagnostic Trouble codes), namely fault codes for short, wherein DTCs represent a set of DTCs; DTC-DOP indicates a specific fault code-related DOP, and DTC-DOPS indicates a set of DTC-DOP. Illustratively, for the diagnostic data of the "DTC-DOP" type in fig. 3, a C + + object corresponding to the creation of a DTC-DOP in the C + + program of the diagnostic instrument is used as the diagnostic data object corresponding to the DTC-DOP type data (referred to as DTC-DOP object for short). Meanwhile, the data in the DTC-DOP tag of FIG. 3 is stored in the DTC-DOP object. Specifically, each string TYPE string variable is defined in the DTC-DOP object to store the original unique identification ID, the relative identification OID, the SHORT NAME SHORT-NAME, the LONG NAME LONG-NAME, etc. in fig. 3, respectively, and data in the DIAG-code-TYPE tag in fig. 3 is stored through an object of the DIAG-code-TYPE, etc., and so on. Similarly, the BV layer file, FG layer file, PR layer file, and SD layer file are each parsed into a BV layer diagnostic object, an FG layer diagnostic object, a PR layer diagnostic object, and an SD layer diagnostic object, respectively, containing the respective diagnostic data objects.
Generally, after acquiring target identification information (for example, a SHORT-NAME or an original unique identification ID of a diagnostic data object), the diagnostic apparatus may start to traverse and search the diagnostic data object corresponding to the target identification information in the corresponding EV-layer diagnostic object according to the target identification information, and return a pointer of the diagnostic data object, thereby implementing reference to the diagnostic data of the ODX source file by reference to the diagnostic data object. In an ODX source file, the files of the various diagnostic layers usually have an inheritance relationship or a reference relationship with each other, so as to avoid the repeated writing of some diagnostic data, which results in the waste of storage space. For example, general diagnostic data that a plurality of ECUs need to refer to in common may be stored only in the SD layer file (or BV layer, FG layer, PR layer), and then the EV layer file (e.g., DLC _ EV _ ems. odd-d file) of a specific one of the ECUs may directly refer to the general diagnostic data of the SD layer (or BV layer, FG layer, PR layer) by writing data reference source information (such as shown in fig. 4) without specifically writing the details of the general diagnostic data in the EV layer file. However, since the diagnostic apparatus usually stores each diagnostic data object in the ODX source file, reference and inheritance relationships of each diagnostic layer are not considered, the diagnostic apparatus only searches for the diagnostic data object in the single-layer EV layer diagnostic object, and if the diagnostic data object cannot be searched, a result of the search failure is directly returned. In order to solve the problem, embodiments of the present application provide a vehicle diagnostic data referencing method, apparatus, terminal device, and storage medium, after determining a target ECU and target identification information according to a diagnostic instruction, traverse each layer of diagnostic objects according to a preset order from an EV layer diagnostic object corresponding to the target ECU until a diagnostic data object corresponding to the target identification information is found as a diagnostic data object to be referenced, and return information of the diagnostic data object to be referenced, thereby implementing cross-diagnostic fault finding of the diagnostic data object.
The first embodiment is as follows:
fig. 5 is a schematic flowchart illustrating a first vehicle diagnostic data referencing method provided in an embodiment of the present application, where an execution subject in the embodiment of the present application is a terminal device, which may specifically be a diagnostic apparatus, and details are as follows:
in S501, a diagnosis instruction is obtained, and a target ECU and target identification information are determined, where the target ECU is an ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnostic data object to be referred when the target ECU is diagnosed.
In the embodiment of the present application, the diagnosis instruction may specifically be an instruction operated by a user on an input device (e.g., a touch screen, an input key, etc.) of the diagnostic apparatus, and the diagnosis instruction may include information of the ECU currently to be diagnosed and information of a diagnosis function currently to be performed, which are selected by the user. And after receiving the diagnosis instruction, the diagnostic instrument determines a target ECU according to the information of the ECU to be diagnosed, which is contained in the diagnosis instruction, and determines target identification information according to the diagnosis function information contained in the diagnosis instruction. The target ECU may be any one of the ECUs of the vehicle, such as an air bag Control Unit (ACU) and an engine management system EMS.
The target identification information is identification information corresponding to a diagnostic data object to be referred to when the target ECU is diagnosed. Optionally, the identification information may specifically be a unique identification number or name information in the open diagnostic data exchange ODX data. For example, the unique identification number "ID" in fig. 3, or NAME information such as a SHORT NAME "SHORT _ NAME", a LONG NAME "LONG _ NAME", and the like. For example, if the diagnostic function information included in the current diagnostic instruction is a fault code reading function, the short name corresponding to the fault code reading function may be determined as "DTCRecord" through a pre-stored comparison table of the diagnostic function and the identification information, and at this time, "DCTRecord" is used as the currently determined target identification information.
In S502, an EV layer diagnostic target corresponding to the target ECU is determined based on the target ECU.
The diagnostic instrument stores in advance each EV layer diagnostic object obtained by analyzing each EV layer file in the ODX source file correspondingly. After the target ECU is determined, an EV layer diagnostic object corresponding to the current target ECU may be determined from among the pre-stored respective EV layer diagnostic objects. For example, if the currently-determined target ECU is EMS, an EV layer diagnostic object named "EV _ EMS" is acquired as the currently-determined EV layer diagnostic object from the EV layer diagnostic objects, which are diagnostic data objects analyzed from the DLC _ EV _ EMS.
In S503, traversing each layer of diagnostic objects according to a preset sequence from the EV layer diagnostic object until the diagnostic data object corresponding to the target identification information is found as the diagnostic data object to be referred to, and returning information of the diagnostic data object to be referred to.
After the EV layer diagnostic object is determined, traversing each layer of diagnostic objects according to a preset sequence from the EV layer diagnostic object until the diagnostic data object corresponding to the target identification information is found to be used as the diagnostic data object to be quoted, returning the information of the diagnostic data object to be quoted, for example, returning a pointer of the diagnostic data object to be quoted, and then realizing the quote of the diagnostic data object to be quoted by calling the pointer. The diagnosis objects of each layer comprise EV layer diagnosis objects, BV layer diagnosis objects, FG layer diagnosis objects, PR layer diagnosis objects and SD layer diagnosis objects. For example, if the current target identification information is a short name "dtcrerecord", then according to the short name, first traversing each diagnostic data object included in the EV-level diagnostic object one level at a time in the EV-level diagnostic object: until the short name 'DTCRECord' is found in the DTC-DOP diagnostic DATA object, the diagnostic DATA object which is consistent with the target identification information is found in the EV layer diagnostic DATA object, and the diagnostic DATA object DTC-DOP is taken as the diagnostic DATA object to be quoted, and the information of the diagnostic DATA object is returned. And when all levels of diagnostic DATA objects such as DIAG-DATA-DICTIONARY-SPEC diagnostic DATA objects, DCT-DOPS diagnostic DATA objects, DCT-DOP diagnostic DATA objects, DTCS diagnostic DATA objects, DTC diagnostic DATA objects and the like in the EV layer diagnostic objects are traversed, selecting one diagnostic object from the BV layer diagnostic object, the FG layer diagnostic object, the PR layer diagnostic object and the SD layer diagnostic object as a next diagnostic object according to a preset sequence, and continuously traversing and searching all diagnostic DATA objects contained in the diagnostic object in the next diagnostic object until the diagnostic DATA object conforming to the target identification information is found.
In the embodiment of the application, after the target ECU and the target identification information are determined by the obtained diagnosis instruction and the corresponding EV layer diagnosis object is determined according to the target ECU, all layers of diagnosis objects can be traversed from the EV layer diagnosis object according to the preset sequence until the diagnosis data object to be quoted is found, and compared with the mode that the existing diagnosis instrument can only find the diagnosis data object to be quoted in a single layer diagnosis object, the success rate of finding the diagnosis data object to be quoted can be improved, so that the reference of the diagnosis data object is effectively realized.
Optionally, traversing each layer of diagnostic objects according to a preset order from the EV layer diagnostic object includes at least:
traversing the EV-level diagnostic object;
and traversing all SD layer diagnostic objects if the diagnostic data object to be referred which is consistent with the target identification information does not exist in the EV layer diagnostic objects.
In the embodiment of the application, after traversing each diagnostic data object in the EV layer diagnostic objects, no diagnostic data object corresponding to the target identification information is found, which indicates that the diagnostic data object corresponding to the target identification information may be stored in the diagnostic objects corresponding to other diagnostic layers according to an inheritance or reference relationship.
Considering that in the ODX source file, the SD layer file contains most general data, and the current diagnostic data object to be referred to has a high probability of being found in the SD layer diagnostic object, therefore, the SD layer diagnostic object is preferentially selected as the diagnostic object corresponding to the next diagnostic layer to be traversed. And traversing each diagnostic data object in each SD layer diagnostic object (which can comprise SD layer diagnostic objects corresponding to each SD layer file such as DLC _ SD _ DOP.odx-d, DLC _ SD _ UNITS.odx-d) in sequence, stopping traversing if a diagnostic data object conforming to the target identification information is found in any one SD layer diagnostic object, taking the diagnostic data object conforming to the target identification information as a diagnostic data object to be quoted, and returning the information of the diagnostic data object to be quoted.
In the embodiment of the application, the preset sequence is that the EV layer diagnostic objects are traversed first, when the EV layer diagnostic object does not have the diagnostic data object to be referred, all SD layer diagnostic objects can be traversed, and since the SD layer diagnostic object includes most of the general diagnostic data objects, the diagnostic data object to be referred can be found more efficiently according to the sequence.
Optionally, after said traversing all SD layer diagnostic objects, further comprising:
and traversing the BV layer diagnostic object inherited by the EV layer diagnostic object if all the SD layer diagnostic objects do not have the diagnostic data object conforming to the target identification information.
In this embodiment of the application, referring to the diagnostic layer relationship of fig. 2, the EV layer diagnostic object is actually a specific implementation of a BV layer diagnostic object, and the EV layer diagnostic object directly inherits the BV layer diagnostic object, and the BV layer diagnostic object has a higher probability of directly including the current diagnostic data object to be referred. Therefore, if no diagnostic data object matching the target identification information is found from any of the SD layer diagnostic objects, the BV layer diagnostic object having a direct inheritance relationship with the EV layer diagnostic object is further set as the next diagnostic object. At this time, traversing each diagnostic data object in the BV diagnostic object, and if the diagnostic data object corresponding to the target identification information is found in the BV diagnostic object, returning the information of the diagnostic data object. Illustratively, if the EV layer diagnostic object currently determined from the target ECU is specifically an EV _ EMS diagnostic object corresponding to a DLC _ EV _ ems.odx-d file, the corresponding inherited BV diagnostic object is a BV _ EMS diagnostic object corresponding to a DLC _ BV _ ems.odx-d file.
In the embodiment of the application, when the diagnostic object to be referred is not found in the SD layer diagnostic object, the BV layer diagnostic object having a direct inheritance relationship with the EV layer diagnostic object can be further preferentially considered as the next diagnostic object, so that the diagnostic data object to be referred can be further efficiently found.
Optionally, after traversing the BV layer diagnostic object inherited by the EV layer diagnostic object, further comprising:
and traversing all PR layer diagnostic objects if the BV layer diagnostic object does not have a diagnostic data object which is consistent with the target identification information.
Usually, the specific contents of the partial diagnostic data objects of the BV layer diagnostic object or the FG layer diagnostic object inherited by the BV layer diagnostic object are stored in the PR layer diagnostic object, i.e. some of the BV layer diagnostic objects are derived from PR layer diagnostic objects. Therefore, in the embodiment of the present application, after traversing the BV layer diagnostic object, if the diagnostic data object that matches the target identification information is not found, all PR layer diagnostic objects are further used as the diagnostic objects to be traversed next. And then, sequentially traversing each PR layer diagnostic object, if the diagnostic data object which is consistent with the target identification information is found out by any PR layer diagnostic object, stopping traversing, and returning the information of the diagnostic data object.
In the embodiment of the application, when the BV layer diagnostic object does not have the diagnostic data object which is consistent with the target identification information, all PR layer diagnostic objects can be directly traversed, that is, all PR layer diagnostic objects which may be referred to by two layers of diagnostic objects, namely the BV layer diagnostic object or an FG layer diagnostic object inherited by the BV layer diagnostic object, are traversed at one time, so that the efficiency and the success rate of referring the vehicle diagnostic data can be further improved.
Optionally, after the traversal through all PR layer diagnostic objects, further comprising:
and traversing the FG layer diagnostic object inherited by the BV layer diagnostic object if all the PR layer diagnostic objects do not have the diagnostic data object which is consistent with the target identification information.
In the embodiment of the application, when the diagnosis data object which is consistent with the target identification information cannot be searched from all the PR layer diagnosis objects, the FG layer diagnosis object inherited by the BV layer diagnosis object is further determined as the next layer diagnosis object. And traversing each diagnostic data object in the FG layer diagnostic objects, and if the diagnostic data object which is consistent with the target identification information is found in the FG layer diagnostic objects, returning the information of the diagnostic data object.
When the diagnostic data object to be referred cannot be found from the BV layer diagnostic object and all the PR layer diagnostic objects, the FG layer diagnostic object inherited by the BV layer diagnostic object can be further inherited, so that the diagnostic objects of all layers are fully traversed according to the inheritance relationship of all diagnostic layers, and the probability of finding the diagnostic data object to be referred is improved.
Optionally, after traversing the BV layer diagnostic object inherited by the EV layer diagnostic object, further comprising:
traversing a first PR layer diagnostic object referenced in the BV layer diagnostic object if the BV layer diagnostic object does not have a diagnostic data object consistent with the target identification information;
if the first PR layer diagnosis object does not have a diagnosis data object which is consistent with the target identification information, traversing the FG layer diagnosis object inherited by the BV layer diagnosis object;
and traversing a second PR layer diagnostic object referenced in the FG layer diagnostic object if the FG layer diagnostic object does not have a diagnostic data object consistent with the target identification information.
In the embodiment of the present application, after the EV layer diagnostic objects, all SD layer diagnostic objects, and the BV layer diagnostic object directly inherited by the EV layer diagnostic objects are sequentially traversed, if no diagnostic data corresponding to the target identification information can be found, the search priority order specified by the ODX standard is further followed: and sequentially traversing and searching the first PR layer diagnostic object referenced by the BV layer diagnostic object, the FG layer diagnostic object inherited by the BV layer diagnostic object and the second PR layer diagnostic object referenced by the FG layer diagnostic object until the diagnostic data object corresponding to the target identification information is searched in one layer of diagnostic objects, stopping traversing, taking the diagnostic data object corresponding to the target identification information as a diagnostic data object to be referenced, and returning the information of the diagnostic data object to be referenced.
In the embodiment of the application, when the diagnostic data object which is consistent with the target identification information does not exist in the BV layer diagnostic object, other layers of diagnostic objects can be further traversed according to the priority order specified by the ODX standard, so that the diagnostic data to be referred can be sufficiently searched in combination with the reference relation and the inheritance relation of the ODX standard, the success rate of searching the diagnostic data object to be referred is improved, and the reference of the diagnostic data object is effectively realized.
Further, if the diagnostic data object which is consistent with the target identification information cannot be found after all layers of diagnostic objects are traversed, an error code is returned to prompt a user that the current vehicle diagnostic data fails to be quoted.
In summary, the preset sequence in step S503 in the embodiment of the present application may have the following several sequences:
preset sequence 1: the order of traversal is exactly as per the ODX standard:
EV layer diagnostic object → first SD layer diagnostic object referenced by EV layer → BV layer diagnostic object inherited by EV layer → second SD layer diagnostic object referenced by BV layer → first PR layer diagnostic object referenced by BV layer diagnostic object → FG layer diagnostic object inherited by BV layer → third SD layer diagnostic object referenced by FG layer → second PR layer diagnostic object referenced by FG layer → fourth SD layer diagnostic object referenced by PR layer diagnostic object. The diagnostic objects referenced by the current level are traversed according to the reference relationship of the current level, and then the diagnostic objects inherited by the current level are traversed according to the inheritance relationship of the current level.
When the vehicle diagnostic data can perform the step-by-step traversal of the cross-layer diagnostic objects according to the preset sequence 1 through the program interface, the diagnostic objects corresponding to the diagnostic layers can be fully traversed according to the reference relation and the inheritance relation between the diagnostic layers and the diagnostic data to be referred can be fully searched according to the ODX standard, the success rate of searching the diagnostic data objects to be referred is improved, and the reference of the diagnostic data objects is effectively realized.
The preset sequence 2: the sequence after optimizing the preset sequence 1 is as follows:
EV layer diagnostic object → all SD layer diagnostic objects → BV layer diagnostic object inherited by EV layer diagnostic object → first PR layer diagnostic object referenced by BV layer diagnostic object → FG layer diagnostic object inherited by BV layer → second PR layer diagnostic object referenced by FG layer diagnostic object.
On the basis of the ODX standard, considering that in an ODX source file, an SD layer file contains most general data, and a current diagnostic data object to be quoted has higher probability of being found in the SD layer diagnostic object, therefore, the preset sequence 1 specified by the ODX standard is optimized and improved, and the preset sequence 2 is designed. That is, after traversing the EV-layer diagnostic objects, all SD-layer diagnostic objects which are likely to find the diagnostic data object to be referred to are directly traversed, and it is not necessary to traverse the SD-layer diagnostic objects according to the SD-layer diagnostic objects referred to by each layer each time after entering other layers of diagnostic objects, so that the diagnostic data object to be referred to can be found more efficiently.
Preset sequence 3: the sequence after further optimization of the preset sequence 2:
EV layer diagnostic object → all SD layer diagnostic objects → BV layer diagnostic object inherited by EV layer diagnostic object → all PR layer diagnostic objects → FG layer diagnostic object inherited by BV layer.
On the basis of the preset sequence 2, after the BV layer diagnostic objects are traversed, all the PR layer diagnostic objects are directly traversed, that is, all the PR layer diagnostic objects which are possibly used by two layers of diagnostic objects, namely the BV layer diagnostic objects or FG layer diagnostic objects inherited by the BV layer diagnostic objects, are traversed at one time, so that the efficiency of referring the vehicle diagnostic data can be further improved. For example, when the diagnostic data object to be referred is stored in the second PR layer diagnostic object referred by the FG layer diagnostic object, the traversal of the FG layer diagnostic object can be directly omitted, the efficiency of finding the diagnostic data object to be referred is improved, and the efficiency of referring the vehicle diagnostic data is further improved.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Example two:
fig. 6 is a schematic structural diagram of a vehicle diagnostic data referencing device according to an embodiment of the present application, and for convenience of explanation, only the portions related to the embodiment of the present application are shown:
the vehicle diagnostic data referencing device includes: an acquisition unit 61, an EV layer diagnosis target determination unit 62, and a search unit 63. Wherein:
the obtaining unit 61 is configured to obtain a diagnosis instruction, and determine a target ECU and target identification information, where the target ECU is an ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnostic data object to be referred when the target ECU is diagnosed.
And an EV layer diagnostic object determining unit 62, configured to determine, according to the target ECU, an EV layer diagnostic object corresponding to the target ECU.
And the searching unit 63 is configured to traverse each layer of diagnostic objects according to a preset sequence from the EV layer diagnostic object until the diagnostic data object corresponding to the target identification information is found as the diagnostic data object to be referred, and return information of the diagnostic data object to be referred.
Optionally, the search unit 63 includes:
a first traversal module to traverse the EV-level diagnostic object; and traversing all SD layer diagnostic objects if the diagnostic data objects consistent with the target identification information do not exist in the EV layer diagnostic objects.
Optionally, the searching unit 63 further includes:
and the second traversal module is used for traversing the BV layer diagnostic object inherited by the EV layer diagnostic object if all the SD layer diagnostic objects do not have the diagnostic data object which is consistent with the target identification information.
Optionally, the searching unit 63 further includes:
and the third traversal module is used for traversing all the PR layer diagnostic objects if the BV layer diagnostic object does not have a diagnostic data object which is consistent with the target identification information.
Optionally, the searching unit 63 further includes:
and the fourth traversal module is used for traversing the FG layer diagnostic object inherited by the BV layer diagnostic object if all the PR layer diagnostic objects do not have the diagnostic data object which is consistent with the target identification information.
Optionally, the search unit 63 further includes a fifth traversal module, a sixth traversal module, and a seventh traversal module:
a fifth traversal module, configured to traverse a first PR layer diagnostic object referenced in the BV layer diagnostic object if the BV layer diagnostic object does not have a diagnostic data object that matches the target identification information;
a sixth traversal module, configured to traverse an FG-layer diagnostic object inherited by the BV-layer diagnostic object if the first PR-layer diagnostic object does not have a diagnostic data object that matches the target identification information;
and the seventh traversing module is used for traversing a second PR layer diagnostic object quoted in the FG layer diagnostic object if the diagnostic data object which is consistent with the target identification information does not exist in the FG layer diagnostic object.
Optionally, the identification information is unique identification number or name information included in the open diagnostic data exchange ODX data.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
Example three:
fig. 7 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in fig. 7, the terminal device 7 of this embodiment includes: a processor 70, a memory 71, and a computer program 72, such as a vehicle diagnostic data reference program, stored in the memory 71 and operable on the processor 70. The processor 70, when executing the computer program 72, implements the steps in the various vehicle diagnostic data referencing method embodiments described above, such as steps S501-S503 shown in fig. 5. Alternatively, the processor 70, when executing the computer program 72, implements the functions of the modules/units in the above-mentioned device embodiments, such as the functions of the units 61 to 63 shown in fig. 6.
Illustratively, the computer program 72 may be partitioned into one or more modules/units that are stored in the memory 71 and executed by the processor 70 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 72 in the terminal device 7. For example, the computer program 72 may be divided into an acquisition unit, an EV layer diagnostic object determination unit, and a search unit, and each unit specifically functions as follows:
the system comprises an acquisition unit, a diagnosis unit and a target identification unit, wherein the acquisition unit is used for acquiring a diagnosis instruction and determining a target ECU and target identification information, the target ECU is the ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnostic data object to be quoted when the target ECU is diagnosed.
And the EV layer diagnostic object determining unit is used for determining the EV layer diagnostic object corresponding to the target ECU according to the target ECU.
And the searching unit is used for traversing all layers of diagnostic objects according to a preset sequence from the EV layer diagnostic object until the diagnostic data object which is consistent with the target identification information is found out to be used as the diagnostic data object to be quoted, and returning the information of the diagnostic data object to be quoted.
The terminal device 7 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 70, a memory 71. It will be appreciated by those skilled in the art that fig. 7 is merely an example of a terminal device 7 and does not constitute a limitation of the terminal device 7 and may comprise more or less components than shown, or some components may be combined, or different components, for example the terminal device may further comprise input output devices, network access devices, buses, etc.
The Processor 70 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 71 may be an internal storage unit of the terminal device 7, such as a hard disk or a memory of the terminal device 7. The memory 71 may also be an external storage device of the terminal device 7, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 7. Further, the memory 71 may also include both an internal storage unit and an external storage device of the terminal device 7. The memory 71 is used for storing the computer program and other programs and data required by the terminal device. The memory 71 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims (10)

1. A vehicle diagnostic data referencing method, comprising:
acquiring a diagnosis instruction, and determining a target Electronic Control Unit (ECU) and target identification information, wherein the target ECU is the current ECU to be diagnosed, and the target identification information is identification information corresponding to a diagnostic data object to be referred when the target ECU is diagnosed;
determining a specific electronic control unit variable EV layer diagnosis object corresponding to the target ECU according to the target ECU;
and traversing each layer of diagnostic objects according to a preset sequence from the EV layer diagnostic object until the diagnostic data object which is consistent with the target identification information is found out to be used as the diagnostic data object to be quoted, and returning the information of the diagnostic data object to be quoted.
2. The diagnostic data referencing method according to claim 1, wherein traversing each layer of diagnostic objects in a preset order starting from the EV layer of diagnostic objects comprises at least:
traversing the EV-level diagnostic object;
and traversing all shared data SD layer diagnostic objects if the diagnostic data objects which are consistent with the target identification information do not exist in the EV layer diagnostic objects.
3. The diagnostic data referencing method according to claim 2, further comprising, after said traversing all shared data SD layer diagnostic objects:
and traversing the basic variable BV layer diagnostic object inherited by the EV layer diagnostic object if all the SD layer diagnostic objects do not have the diagnostic data object conforming to the target identification information.
4. The diagnostic data referencing method according to claim 3, wherein after said traversing the basic variable BV level diagnostic object inherited by said EV level diagnostic object, further comprising:
and traversing all protocol PR layer diagnostic objects if the BV layer diagnostic object does not have a diagnostic data object which is consistent with the target identification information.
5. The diagnostic data referencing method according to claim 4, further comprising, after said traversing all protocol PR layer diagnostic objects:
and traversing the function group FG layer diagnostic object inherited by the BV layer diagnostic object if all the PR layer diagnostic objects do not have the diagnostic data object which is consistent with the target identification information.
6. The diagnostic data referencing method according to claim 3, wherein after said traversing the basic variable BV level diagnostic object inherited by said EV level diagnostic object, further comprising:
traversing a first PR layer diagnostic object referenced in the BV layer diagnostic object if the BV layer diagnostic object does not have a diagnostic data object consistent with the target identification information;
if the first PR layer diagnosis object does not have a diagnosis data object which is consistent with the target identification information, traversing the FG layer diagnosis object inherited by the BV layer diagnosis object;
and traversing a second PR layer diagnostic object referenced in the FG layer diagnostic object if the FG layer diagnostic object does not have a diagnostic data object consistent with the target identification information.
7. The diagnostic data referencing method according to claim 1, wherein said identification information is unique identification number or name information included in open diagnostic data exchange, ODX, data.
8. A vehicle diagnostic data referencing device, comprising:
the system comprises an acquisition unit, a diagnosis unit and a processing unit, wherein the acquisition unit is used for acquiring a diagnosis instruction and determining a target ECU and target identification information, the target ECU is the ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnostic data object to be quoted when the target ECU is diagnosed;
the EV layer diagnostic object determining unit is used for determining an EV layer diagnostic object corresponding to the target ECU according to the target ECU;
and the searching unit is used for traversing all layers of diagnostic objects according to a preset sequence from the EV layer diagnostic object until the diagnostic data object which is consistent with the target identification information is found out to be used as the diagnostic data object to be quoted, and returning the information of the diagnostic data object to be quoted.
9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the computer program, when executed by the processor, causes the terminal device to carry out the steps of the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, causes a terminal device to carry out the steps of the method according to any one of claims 1 to 7.
CN202011266848.0A 2020-11-13 2020-11-13 Vehicle diagnosis data reference method, device, terminal equipment and storage medium Active CN112445816B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011266848.0A CN112445816B (en) 2020-11-13 2020-11-13 Vehicle diagnosis data reference method, device, terminal equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011266848.0A CN112445816B (en) 2020-11-13 2020-11-13 Vehicle diagnosis data reference method, device, terminal equipment and storage medium

Publications (2)

Publication Number Publication Date
CN112445816A true CN112445816A (en) 2021-03-05
CN112445816B CN112445816B (en) 2024-04-02

Family

ID=74736999

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011266848.0A Active CN112445816B (en) 2020-11-13 2020-11-13 Vehicle diagnosis data reference method, device, terminal equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112445816B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113065033A (en) * 2021-03-22 2021-07-02 江铃汽车股份有限公司 ODX file-based diagnosis method

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102010056232A1 (en) * 2010-12-24 2012-06-28 Volkswagen Ag Method for automatic writing of diagnosis data in control device of motor car, involves reading diagnosis data from collecting units by using cross references, and writing read diagnosis data in control devices
CN104216978A (en) * 2014-09-01 2014-12-17 观致汽车有限公司 Automatic generation method and system for vehicle diagnosis database
CN105302113A (en) * 2015-10-28 2016-02-03 武汉锐科控制系统有限公司 Configurable and extensible automobile diagnosis system and diagnosis method
CN109918361A (en) * 2019-03-11 2019-06-21 威马智慧出行科技（上海）有限公司 The creation method and device and data-storage system of vehicle diagnosis database
CN110083145A (en) * 2019-05-13 2019-08-02 深圳市元征科技股份有限公司 A kind of vehicle diagnosis method, device and readable storage medium storing program for executing and Auto analyzer
KR20200000607A (en) * 2018-06-25 2020-01-03 현대자동차주식회사 Diagnostic data base structure and diagnostic system using the same
CN111857100A (en) * 2020-07-30 2020-10-30 深圳市元征科技股份有限公司 Automobile diagnosis method and device and related equipment

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102010056232A1 (en) * 2010-12-24 2012-06-28 Volkswagen Ag Method for automatic writing of diagnosis data in control device of motor car, involves reading diagnosis data from collecting units by using cross references, and writing read diagnosis data in control devices
CN104216978A (en) * 2014-09-01 2014-12-17 观致汽车有限公司 Automatic generation method and system for vehicle diagnosis database
CN105302113A (en) * 2015-10-28 2016-02-03 武汉锐科控制系统有限公司 Configurable and extensible automobile diagnosis system and diagnosis method
KR20200000607A (en) * 2018-06-25 2020-01-03 현대자동차주식회사 Diagnostic data base structure and diagnostic system using the same
CN109918361A (en) * 2019-03-11 2019-06-21 威马智慧出行科技（上海）有限公司 The creation method and device and data-storage system of vehicle diagnosis database
CN110083145A (en) * 2019-05-13 2019-08-02 深圳市元征科技股份有限公司 A kind of vehicle diagnosis method, device and readable storage medium storing program for executing and Auto analyzer
CN111857100A (en) * 2020-07-30 2020-10-30 深圳市元征科技股份有限公司 Automobile diagnosis method and device and related equipment

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113065033A (en) * 2021-03-22 2021-07-02 江铃汽车股份有限公司 ODX file-based diagnosis method

Also Published As

Publication number Publication date
CN112445816B (en) 2024-04-02

Similar Documents

Publication Publication Date Title
CN110083145B (en) Automobile diagnosis method and device, readable storage medium and automobile diagnosis instrument
CN111813095A (en) Vehicle diagnosis method, device and medium
CN111552267B (en) Vehicle diagnosis method and device and vehicle diagnosis equipment
CN113472555B (en) Fault detection method, system, device, server and storage medium
CN113111227A (en) Data processing method and device, electronic equipment and storage medium
CN112445816B (en) Vehicle diagnosis data reference method, device, terminal equipment and storage medium
CN114329090A (en) Path reference searching method and device, electronic equipment and storage medium
CN113434582B (en) Service data processing method and device, computer equipment and storage medium
WO2008005566A2 (en) System and method to determine a single sql bom solve
CN114238767A (en) Service recommendation method and device, computer equipment and storage medium
CN112506999B (en) Cloud computing and artificial intelligence based big data mining method and digital content server
CN117707478A (en) Demand management method, device, equipment and storage medium
CN112445797B (en) Vehicle diagnosis data reference method, device, terminal equipment and storage medium
CN114185707A (en) Vehicle fault diagnosis method and device, terminal equipment and storage medium
CN113848862A (en) Diagnostic software acquisition method and device, communication equipment and storage medium
CN114416057A (en) Project code packaging method and device, terminal equipment and storage medium
CN113342430A (en) Fault code processing method and device, terminal equipment and readable storage medium
CN112445491B (en) File sequence processing method, device, terminal equipment and storage medium
CN112104766B (en) Diagnostic protocol reconstruction method, device, terminal equipment and storage medium
US8639668B2 (en) Structured requirements management
CN111309972A (en) Data processing method and device, terminal equipment and storage medium
CN114326674B (en) ECU (electronic control Unit) refreshing method and device, electronic equipment and storage medium
CN112035474B (en) Data searching method and device
CN113535881B (en) Fault code information storage method, device, communication equipment and storage medium
CN117688564B (en) Detection method, device and storage medium for intelligent contract event log

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant