CN112445816B - Vehicle diagnosis data reference method, device, terminal equipment and storage medium - Google Patents

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

Info

Publication number
CN112445816B
CN112445816B CN202011266848.0A CN202011266848A CN112445816B CN 112445816 B CN112445816 B CN 112445816B CN 202011266848 A CN202011266848 A CN 202011266848A CN 112445816 B CN112445816 B CN 112445816B
Authority
CN
China
Prior art keywords
layer
diagnosis
diagnostic
identification information
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.)
Active
Application number
CN202011266848.0A
Other languages
Chinese (zh)
Other versions
CN112445816A (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

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 an ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnosis 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 all layers of diagnostic objects according to a preset sequence from the EV layer diagnostic objects until the diagnostic data objects which are consistent with the target identification information are searched to serve as the diagnostic data objects to be referenced, and returning the information of the diagnostic data objects to be referenced. The embodiment of the application can realize cross-diagnostic-layer diagnostic data object reference.

Description

Vehicle diagnosis data reference method, 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 quoting method, a device, terminal equipment and a storage medium.
Background
The open diagnostic data exchange (Open Diagnostic Data Exchange, ODX) specifies the standard diagnostic data format of the automotive diagnostic industry, and when the diagnostic apparatus diagnoses vehicles of different vehicle types or different electronic control units (Electronic Control Unit, ECU), only the ODX source file adapted to the vehicle type or ECU needs to be loaded, without any change to the diagnostic apparatus.
At present, each diagnostic data object in the ODX source file exists in each hierarchical file, and when the diagnostic instrument 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 the searching mode often has the condition 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 diagnostic data objects.
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 an ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnosis 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 all layers of diagnostic objects according to a preset sequence from the EV layer diagnostic objects until the diagnostic data objects which are consistent with the target identification information are searched to serve as the diagnostic data objects to be referenced, and returning the information of the diagnostic data objects to be referenced.
Optionally, the traversing the layers of diagnostic objects from the EV layer diagnostic object according to a preset sequence at least includes:
traversing the EV layer diagnosis object;
and if the EV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing all SD layer diagnosis objects.
Optionally, after said traversing all SD layer diagnostic objects, further comprising:
and if all the SD layer diagnosis objects do not have the diagnosis data objects consistent with the target identification information, traversing the BV layer diagnosis objects inherited by the EV layer diagnosis objects.
Optionally, after traversing the BV layer diagnostic object inherited by the EV layer diagnostic object, the method further comprises:
and if the BV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing all PR layer diagnosis objects.
Optionally, after traversing all PR layer diagnostic objects, further comprising:
and if all the PR layer diagnosis objects do not have the diagnosis data objects conforming to the target identification information, traversing FG layer diagnosis objects inherited by the BV layer diagnosis objects.
Optionally, after traversing the BV layer diagnostic object inherited by the EV layer diagnostic object, the method further comprises:
If the BV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing a first PR layer diagnosis object referenced in the BV layer diagnosis object;
if the first PR layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing the FG layer diagnosis object inherited by the BV layer diagnosis object;
and if the FG layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing a second PR layer diagnosis object referenced in the FG layer diagnosis object.
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 apparatus, comprising:
the system comprises an acquisition unit, a diagnosis unit and a reference unit, wherein the acquisition unit is used for acquiring a diagnosis instruction and determining a target ECU and target identification information, wherein the target ECU is an ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnosis data object to be quoted when the target ECU is diagnosed;
an EV layer diagnosis object determining unit, configured to determine an EV layer diagnosis object corresponding to the target ECU according to the target ECU;
And the searching unit is used for traversing the diagnostic objects of each layer according to a preset sequence from the diagnostic object of the EV layer until the diagnostic data object which accords with the target identification information is searched to serve as the diagnostic data object to be referred, and returning the information of the diagnostic data object to be referred.
Optionally, the search unit includes:
the first traversing module is used for traversing the EV layer diagnosis object; and if the EV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing all SD layer diagnosis objects.
Optionally, the search unit further includes:
and the second traversing module is used for traversing the BV layer diagnosis object inherited by the EV layer diagnosis object if all the SD layer diagnosis objects do not have the diagnosis data object consistent with the target identification information.
Optionally, the search unit further includes:
and the third traversing module is used for traversing all PR layer diagnosis objects if the BV layer diagnosis objects do not have diagnosis data objects which are consistent with the target identification information.
Optionally, the search unit further includes:
and a fourth traversing module, configured to traverse the FG layer diagnostic object inherited by the BV layer diagnostic object if all the PR layer diagnostic objects do not have diagnostic data objects conforming to 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 traversing 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 traversing module, configured to traverse, if the first PR layer diagnostic object does not have a diagnostic data object that matches the target identification information, an FG layer diagnostic object that is inherited by the BV layer diagnostic object;
and a seventh traversing module, configured to traverse 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 that matches 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 third aspect of the embodiments of the present application provides a terminal device comprising 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 the 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 steps of the vehicle diagnostic data referencing method.
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 perform the steps of the vehicle diagnostic data referencing method as set forth in any of the first aspects above.
Compared with the prior art, the embodiment of the application has the beneficial effects that: in the embodiment of the application, after the target ECU and the target identification information are determined by acquiring the diagnosis instruction and the corresponding EV layer diagnosis object is determined according to the target ECU, the diagnosis objects of all layers can be traversed from the EV layer diagnosis object according to the preset sequence until the diagnosis data object to be referred is found, and compared with the mode that the conventional diagnostic instrument can only find the diagnosis data object to be referred in a single layer diagnosis object, the success rate of finding the diagnosis data object to be referred 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 of the embodiments of the present application, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person of ordinary skill in the art.
Fig. 1 is a schematic view of an application scenario for vehicle diagnostic data referencing provided in an embodiment of the present application;
FIG. 2 is a schematic diagram of a diagnostic layer structure according to 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 illustrating a record of source information of data references 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 apparatus provided in 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 configurations, 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 illustrate the technical solutions described in the present application, the following description is made by specific examples.
It should 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 is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification 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 any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In addition, in the description of the present application, the terms "first," "second," "third," etc. are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.
Fig. 1 shows a schematic diagram of an application scenario corresponding to a vehicle diagnostic data referencing method according to an embodiment of the present application, including a diagnostic apparatus 11 and a vehicle 12. When the diagnostic apparatus 11 needs to perform vehicle diagnosis on the vehicle 12, the diagnostic apparatus 11 is connected to an on-board automatic diagnostic system (On Board Diagnostics, OBD) interface 121 of the vehicle 12, and 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. Then, the reference to the diagnostic data can be achieved by referencing the diagnostic data object in the diagnostic instrument program.
The ODX source files specifically include a plurality of ODX source files corresponding to different ECUs at different levels. Specifically, as shown in fig. 2, the diagnostic layers in the ODX source file may include five diagnostic layers, specifically four diagnostic layers from top to bottom (from generalization to specific): PROTOCOL (PR) layer, function GROUP (FG) layer, basic-variable (BV) layer, and specific electronic control unit variable (ECU-variable, EV) layer; and also includes a SHARED DATA (ECU-SHARED-DATA, SD) layer. Wherein:
The PR layer defines a certain diagnostic application layer Protocol, such as a controller area network (Controller Area Network, CAN) Protocol, a Keyword Protocol (KWP), a network diagnostic communication Protocol (Diagnostic communication over Internet Protocol, DOIP), a vehicle network standard Protocol (Flexray), or an Ethernet Protocol (Ethernet), etc.
The FG layer defines a functional group diagnosis service or data that is commonly supported by a plurality of ECUs.
The BV layer represents the diagnostic data type of an ODX database of the basic variable type of a specific ECU, and in each vehicle model, each ECU only has one BASE-VARIANT file, which can be inherited from PROTOCOL or FUNCTIONAL-GROUP, can contain references to the diagnostic services and data in the two layers of diagnostic layers, and can change the inherited services and data.
The EV layer is a specific implementation of each ECU. For example, in a complete ODX source file package (pack ODX DATA, PDX), there is only one BASE-VARIANT file for the engine, but the engine may have a 1.4,1.6 version of the configuration, and the engine ECU of the different configuration may have different diagnostic DATA, as embodied in the ECU-VARIANT.
The SD layer is a database defining generic data types that are referenced by the 4 diagnostic layer files above.
Illustratively, for a PDX package of one vehicle type, the PR layer includes files of: DLC_PR_CAN.odx-d, DLC_PR_Ethernet.odx-d, DLC_PR_flexray.odx-d, etc.; the FG layer includes files of: DLC_FG_CAN.odx-d, DLC_FG_Ethernet.odx-d, DLC_FG_Flexray.odx-d, etc.; the BV layer includes files including: basic variable files of each ECU such as 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 the like; the EV layer includes files including: specific implementation files of each ECU such as 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 the like; the SD layer includes files including: dlc_sd_dop.odx-d, dlc_sd_uds.odx-d, dlc_sd_units.odx-d, etc.
Specifically, each ODX source file is an extensible markup language XML format file, and diagnostic data of different types in a single ODX source file is packaged by XML labels; the ODX source file of each diagnostic layer corresponds to a diagnostic data object which is analyzed into a diagnostic layer level, and is called a diagnostic layer diagnostic object for short; the diagnostic data in the single ODX source file is further parsed into diagnostic data objects below the class object. For example, for an EV layer file DLC_EV_EMS.odx-d corresponding to an engine management system (Engine Management System, EMS), the diagnostic instrument analyzes the EV layer file DLC_EV_EMS.odx-d into an EV layer diagnostic object named EV_EMS, and each diagnostic data in DLC_EV_EMS.odx-d is analyzed 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 an EV layer diagnostic object named ev_ems by resolving it to a short name of ecu_vraiant, and the respective diagnostic DATA DIAG-DATA-diconetwork-SPEC, DTC-DOPS, DTC-DOP, DTCs, DTC, and the like nested stepwise under the ecu_vraiant are resolved one by one to respective diagnostic DATA objects under the EV diagnostic object. Wherein, the ECU-VARIANT represents a specialized ECU object; DIAG-DATA-DICTIONARY-SPEC represents a diagnostic DATA DICTIONARY set containing DOP sets (Data Object Property, which can be simply understood as algorithm-related DATA) of various simple types and complex types, and is referenced by other diagnostic parameters, and participates in calculating original DATA replied by ECU, so as to obtain physical values and display the physical values to a user interface; DTC (Diagnostic Trouble Code) diagnosing fault codes, namely fault codes for short, and DTCS represents a collection of DTCs; DTC-DOP represents a specific fault code-dependent DOP, and DTC-DOPS represents a set of DTC-DOPs. For example, for the "DTC-DOP" type diagnostic data in fig. 3, a c++ object corresponding to one DTC-DOP is created in the c++ program of the diagnostic apparatus as a diagnostic data object corresponding to the DTC-DOP type data (referred to as DTC-DOP object for short). At the same time, the data within the DTC-DOP tag of fig. 3 is stored into 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 in fig. 3, respectively, and the data in the DIAG-code-TYPE tag in fig. 3, etc. by one DIAG-code-TYPE object, and so on. Similarly, the BV layer file, FG layer file, PR layer file, and SD layer file are each parsed into BV layer diagnostic object, FG layer diagnostic object, PR layer diagnostic object, and SD layer diagnostic object, respectively, that include the respective diagnostic data objects.
Generally, after obtaining the target identification information (for example, SHORT NAME SHORT-NAME or original unique identification ID of the 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, so as to implement reference to the diagnostic data of the ODX source file through reference to the diagnostic data object. In the ODX source file, the files of each diagnostic layer usually have a relationship of inheritance or mutual reference, so as to avoid the repeated writing of some diagnostic data, which leads to the waste of storage space. For example, general diagnostic data that a plurality of ECUs commonly need to refer to may be stored only in the SD layer file (or BV layer, FG layer, PR layer), after which the EV layer file (e.g., dlc_ev_ems.odx-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 (e.g., as shown in fig. 4) without specific writing of the details of the general diagnostic data in the EV layer file. However, since the diagnostic apparatuses generally store the diagnostic data objects in the ODX source file separately, the diagnostic apparatuses only search the diagnostic data objects in the EV layer of the single layer without considering the reference and inheritance relationship of each diagnostic layer, and if the diagnostic apparatuses cannot search the diagnostic data objects, the diagnostic apparatuses directly return the result of the search failure. In order to solve the problem, the embodiment of the application provides a vehicle diagnosis data referencing method, device, terminal equipment and storage medium, after determining target ECU and target identification information according to a diagnosis instruction, all layers of diagnosis objects are traversed according to a preset sequence from EV layer diagnosis objects corresponding to the target ECU until the diagnosis data object conforming to the target identification information is found as the diagnosis data object to be referenced, and information of the diagnosis data object to be referenced is returned, so that cross-diagnosis layer searching of the diagnosis data object is realized, and compared with the mode that the existing diagnostic instrument can only search the diagnosis data object to be referenced in a single layer diagnosis object, the success rate of searching the diagnosis data object to be referenced can be improved, and referencing of the diagnosis data object is effectively realized.
Embodiment one:
fig. 5 shows a flowchart of a first vehicle diagnostic data referencing method provided by an embodiment of the present application, where an execution body of the embodiment of the present application is a terminal device, specifically may be a diagnostic apparatus, and is described in detail below:
in S501, a diagnosis instruction is acquired, 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 diagnosing the target ECU.
In this embodiment of the present application, the diagnostic instruction may specifically be an instruction that a user operates on an input device (for example, a touch screen, an input key, etc.) of the diagnostic apparatus, where the diagnostic instruction may include information of an ECU currently to be diagnosed selected by the user and information of a diagnostic function currently to be performed. After the diagnostic instrument receives the diagnostic instruction, the target ECU is determined according to the information of the ECU to be diagnosed, which is contained in the diagnostic instruction, and the target identification information is determined according to the diagnostic function information, which is contained in the diagnostic instruction. The target ECU may be any one of the ECUs of the vehicle such as an airbag control unit (Airbag 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 when diagnosing the target ECU. Alternatively, 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", or the like. For example, if the diagnostic function information included in the current diagnostic instruction is a fault code reading function, the short name "DTCRecord" corresponding to the fault code reading function may be determined by a pre-stored comparison table of the diagnostic function and the identification information, and in this case, "DCTRecord" is taken as the currently determined target identification information.
In S502, an EV layer diagnosis target corresponding to the target ECU is determined from the target ECU.
The diagnostic apparatus stores in advance each EV layer diagnostic object obtained by analyzing the correspondence of each EV layer file in the ODX source file. 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 individual EV layer diagnostic objects. For example, if the currently specified target ECU is an EMS, an EV layer diagnostic object named "ev_ems" is acquired from EV layer diagnostic objects, which are diagnostic data objects obtained by parsing dlc_ev_ems.odx-d files, as currently specified EV layer diagnostic objects.
In S503, starting from the EV layer diagnostic object, traversing the diagnostic objects of each layer according to a preset sequence until the diagnostic data object conforming to the target identification information is found as the diagnostic data object to be referenced, and returning the information of the diagnostic data object to be referenced.
After the EV layer diagnosis object is determined, traversing all layers of diagnosis objects according to a preset sequence from the EV layer diagnosis object until the diagnosis data object which accords with the target identification information is found to be used as the diagnosis data object to be referred, returning information of the diagnosis data object to be referred, such as a pointer of the diagnosis data to be referred, and then realizing the reference of the diagnosis data object to be referred by calling the pointer. The diagnosis objects of each layer comprise EV layer diagnosis object, BV layer diagnosis object, FG layer diagnosis object, PR layer diagnosis object and SD layer diagnosis object. For example, assuming that the current target identification information is a short name "DTCRecord", according to the short name, each diagnostic data object included in the EV layer diagnostic object is first traversed in a first-level manner in the EV layer diagnostic object: DIAG-DATA-diconary-SPEC diagnostic DATA object, DCT-DOPS diagnostic DATA object, DCT-DOP diagnostic DATA object, until a short name "dtcrecor" is found in DTC-DOP diagnostic DATA object, which indicates that a diagnostic DATA object matching the target identification information has been found in EV layer diagnostic DATA object currently, and returns the diagnostic DATA object DTC-DOP as the diagnostic DATA object to be referenced. When no diagnostic DATA object conforming to the target identification information is found after traversing DIAG-DATA-DICTONARY-SPEC diagnostic DATA objects, DCT-DOPS diagnostic DATA objects, DCT-DOP diagnostic DATA objects, DTCS diagnostic DATA objects, DTC diagnostic DATA objects and other diagnostic DATA objects in EV layer diagnostic objects, selecting one diagnostic object from BV layer diagnostic objects, FG layer diagnostic objects, PR layer diagnostic objects and SD layer diagnostic objects as the next diagnostic object according to a preset sequence, and continuing 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 acquiring the diagnosis instruction and the corresponding EV layer diagnosis object is determined according to the target ECU, the diagnosis objects of all layers can be traversed from the EV layer diagnosis object according to the preset sequence until the diagnosis data object to be referred is found, and compared with the mode that the conventional diagnostic instrument can only find the diagnosis data object to be referred in a single layer diagnosis object, the success rate of finding the diagnosis data object to be referred can be improved, so that the reference of the diagnosis data object is effectively realized.
Optionally, the traversing the layers of diagnostic objects from the EV layer diagnostic object according to a preset sequence at least includes:
traversing the EV layer diagnosis object;
and if the EV layer diagnosis object does not exist the diagnosis data object to be referenced which accords with the target identification information, traversing all SD layer diagnosis objects.
In the embodiment of the present application, after each diagnostic data object in the EV layer diagnostic objects is traversed, no diagnostic data object matching 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 inheritance or reference relationships.
Considering that the SD layer file contains most of general data in the ODX source file, the current diagnostic data object to be referred to has a high probability of being found in the SD layer diagnostic object, so that the SD layer diagnostic object is preferentially selected as the diagnostic object corresponding to the diagnostic layer to be traversed next. And traversing each diagnostic data object in each SD layer diagnostic object (including the SD layer diagnostic objects corresponding to each SD layer file such as DLC_SD_DOP.odx-d, DLC_SD_UDS.odx-d, DLC_SD_UNITS.odx-d and the like) in sequence, stopping traversing if the diagnostic data object conforming to the target identification information is found in any SD layer diagnostic object, taking the diagnostic data object conforming to the target identification information as the diagnostic data object to be referenced, and returning the information of the diagnostic data object to be referenced.
In this embodiment of the present invention, the preset sequence specifically refers to traversing EV layer diagnostic objects first, and 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 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 if all the SD layer diagnosis objects do not have the diagnosis data objects consistent with the target identification information, traversing the BV layer diagnosis objects inherited by the EV layer diagnosis objects.
In this embodiment, in contrast to the diagnostic layer relationship of fig. 2, the EV layer diagnostic object is actually a specific implementation of a BV layer diagnostic object, where the EV layer diagnostic object directly inherits from the BV layer diagnostic object, and the BV layer diagnostic object has a high 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 among the individual 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, each of the BV diagnostic objects is traversed, and if a diagnostic data object matching the target identification information is found in the BV diagnostic object, the information of the diagnostic data object is returned. For example, if the EV layer diagnostic object currently determined according to the target ECU is specifically an ev_ems diagnostic object corresponding to the dlc_ev_ems.odx-d file, the BV diagnostic object that is inherited accordingly is a bv_ems diagnostic object corresponding to the 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 prioritized as the next diagnostic object, so that the diagnostic data object to be referred is further and efficiently found.
Optionally, after traversing the BV layer diagnostic object inherited by the EV layer diagnostic object, the method further comprises:
and if the BV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing all PR layer diagnosis objects.
Typically, the specific contents of the partial diagnostic data object of the BV layer diagnostic object or the partial diagnostic data object of the FG layer diagnostic object inherited by the BV layer diagnostic object are stored in the PR layer diagnostic object, i.e. some diagnostic data objects in the BV layer diagnostic object originate from the PR layer diagnostic object. Therefore, in the embodiment of the present application, after traversing the BV layer diagnostic object, if the diagnostic data object matching with the target identification information is not found, all PR layer diagnostic objects are further used as diagnostic objects to be traversed in the next step. And then traversing each PR layer diagnosis object in turn, stopping traversing if any PR layer diagnosis object finds the diagnosis data object which accords with the target identification information, and returning the information of the diagnosis data object.
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, all PR layer diagnostic objects can be traversed directly, namely PR layer diagnostic objects possibly led by two layers of diagnostic objects, namely the BV layer diagnostic object or 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 vehicle diagnostic data quote can be further improved.
Optionally, after traversing all PR layer diagnostic objects, further comprising:
and if all the PR layer diagnosis objects do not have the diagnosis data objects conforming to the target identification information, traversing FG layer diagnosis objects inherited by the BV layer diagnosis objects.
In the embodiment of the application, when the diagnostic data object which accords with the target identification information cannot be found from all PR layer diagnostic objects, the FG layer diagnostic object inherited by the BV layer diagnostic object is further determined to be the next layer diagnostic object. And traversing each diagnostic data object in the FG layer diagnostic objects, and returning the information of the diagnostic data object if the diagnostic data object which is consistent with the target identification information is found in the FG layer diagnostic objects.
As the FG layer diagnosis object inherited by the BV layer diagnosis object can be further discovered when the diagnosis data object to be quoted cannot be found from the BV layer diagnosis object and all PR layer diagnosis objects, each layer diagnosis object is fully traversed according to the inheritance relation of each diagnosis layer, and the probability of finding the diagnosis data object to be quoted is improved.
Optionally, after traversing the BV layer diagnostic object inherited by the EV layer diagnostic object, the method further comprises:
if the BV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing a first PR layer diagnosis object referenced in the BV layer diagnosis object;
if the first PR layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing the FG layer diagnosis object inherited by the BV layer diagnosis object;
and if the FG layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing a second PR layer diagnosis object referenced in the FG layer diagnosis object.
In this embodiment of the present application, after the EV layer diagnostic object, all the SD layer diagnostic objects, and the BV layer diagnostic object directly inherited by the EV layer diagnostic object are traversed in sequence, if no diagnostic data conforming to the target identification information can be found, the search priority order specified by the ODX standard is further followed: and traversing and searching the diagnosis objects of each layer in sequence until the diagnosis data object conforming to the target identification information is found in one layer of diagnosis objects, stopping traversing, taking the diagnosis data object conforming to the target identification information as the diagnosis data object to be referenced, and returning the information of the diagnosis data object to be referenced.
In the embodiment of the application, when the diagnostic data object conforming to the target identification information does not exist in the BV layer diagnostic object, the diagnostic data object of other layers can be traversed further according to the priority order specified by the ODX standard, so that the diagnostic data to be referred can be fully searched by combining the referential relationship and the inheritance relationship 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 accords with the target identification information cannot be found after the diagnostic objects of each layer are traversed, an error code is returned to prompt the user that the current vehicle diagnostic data reference fails.
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 sequence of traversal is fully according to ODX standard:
EV layer diagnosis object- & gtEV layer reference first SD layer diagnosis object- & gtEV layer diagnosis object- & gtBV layer reference second SD layer diagnosis object- & gtBV layer reference first PR layer diagnosis object- & gtBV layer inheritance FG layer diagnosis object- & gtFG layer reference third SD layer diagnosis object- & gtFG layer reference second PR layer diagnosis object- & gtPR layer diagnosis object- & gtfourth SD layer diagnosis object- & gtPR layer diagnosis object. The diagnosis objects referenced by the current hierarchy are traversed according to the reference relation of the current hierarchy each time, and then the diagnosis objects inherited by the current hierarchy are traversed according to the inheritance relation of the current hierarchy.
When the program interface is set, the vehicle diagnosis data can traverse the cross-level diagnosis objects step by step according to the preset sequence 1, the diagnosis objects corresponding to each diagnosis layer can be fully traversed according to the ODX standard and the quotation relation and the inheritance relation between the diagnosis layers, the diagnosis data to be quoted is fully searched, the success rate of searching the diagnosis data objects to be quoted is improved, and therefore the quotation of the diagnosis data objects is effectively realized.
Preset sequence 2: sequence after optimizing the preset sequence 1:
EV layer diagnosis object- & gt all SD layer diagnosis objects- & gt BV layer diagnosis object inherited by EV layer diagnosis object- & gt first PR layer diagnosis object inherited by BV layer diagnosis object- & gt FG layer diagnosis object inherited by BV layer- & gt second PR layer diagnosis object inherited by FG layer diagnosis object.
Based on the ODX standard, considering that the SD layer file contains most general data in the ODX source file, the current diagnostic data object to be quoted can be found in the SD layer diagnostic object with high probability, so that 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 that are more likely to find the diagnostic data object to be referred are directly traversed, without traversing the SD layer diagnostic objects according to the SD layer diagnostic objects that are 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 optimizing the preset sequence 2:
EV layer diagnosis object- & gtall SD layer diagnosis object- & gtBV layer diagnosis object inherited by EV layer diagnosis object- & gtall PR layer diagnosis object- & gtFG layer diagnosis object inherited by BV layer.
On the basis of the preset sequence 2, after traversing BV layer diagnosis objects, traversing all PR layer diagnosis objects directly, namely traversing PR layer diagnosis objects possibly led by two layers of diagnosis objects, namely BV layer diagnosis objects or FG layer diagnosis objects inherited by BV layer diagnosis objects, at one time, so that the efficiency of vehicle diagnosis data reference can be further improved. For example, when the diagnostic data object to be referred is stored in the second PR layer diagnostic object referred to by the FG layer diagnostic object, traversal of the FG layer diagnostic object can be directly omitted, so that efficiency of searching the diagnostic data object to be referred is improved, and further efficiency of referring the diagnostic data of the vehicle is improved.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.
Embodiment two:
fig. 6 shows a schematic structural diagram of a vehicle diagnostic data referencing apparatus provided in an embodiment of the present application, and for convenience of explanation, only parts relevant to the embodiment of the present application are shown:
the vehicle diagnostic data referencing apparatus includes: an acquisition unit 61, an EV layer diagnosis object 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 diagnosing the target ECU.
And an EV layer diagnosis object determining unit 62 configured to determine, according to the target ECU, an EV layer diagnosis object corresponding to the target ECU.
And a searching unit 63, configured to traverse the diagnostic objects of each layer in a preset order from the diagnostic object of the EV layer until the diagnostic data object conforming to the target identification information is found as the diagnostic data object to be referred to, and return information of the diagnostic data object to be referred to.
Optionally, the searching unit 63 includes:
the first traversing module is used for traversing the EV layer diagnosis object; and if the EV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing all SD layer diagnosis objects.
Optionally, the searching unit 63 further includes:
and the second traversing module is used for traversing the BV layer diagnosis object inherited by the EV layer diagnosis object if all the SD layer diagnosis objects do not have the diagnosis data object consistent with the target identification information.
Optionally, the searching unit 63 further includes:
and the third traversing module is used for traversing all PR layer diagnosis objects if the BV layer diagnosis objects do not have diagnosis data objects which are consistent with the target identification information.
Optionally, the searching unit 63 further includes:
and a fourth traversing module, configured to traverse the FG layer diagnostic object inherited by the BV layer diagnostic object if all the PR layer diagnostic objects do not have diagnostic data objects conforming to the target identification information.
Optionally, the searching unit 63 further includes a fifth traversing module, a sixth traversing module, and a seventh traversing module:
a fifth traversing 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 traversing module, configured to traverse, if the first PR layer diagnostic object does not have a diagnostic data object that matches the target identification information, an FG layer diagnostic object that is inherited by the BV layer diagnostic object;
And a seventh traversing module, configured to traverse 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 that matches the target identification information.
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, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a 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 process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
Embodiment III:
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 executable on the processor 70. The processor 70, when executing the computer program 72, implements the steps of the respective vehicle diagnostic data referencing method embodiments described above, such as steps S501 to S503 shown in fig. 5. Alternatively, the processor 70, when executing the computer program 72, performs the functions of the modules/units of the apparatus embodiments described above, such as the functions of the units 61 to 63 shown in fig. 6.
By way of example, 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 complete the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions for describing the execution 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 diagnosis object determination unit, and a search unit, each of which functions as follows:
The acquisition unit is used for acquiring the 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 the identification information corresponding to the diagnostic data object to be quoted when the target ECU is diagnosed.
And the EV layer diagnosis object determining unit is used for determining an EV layer diagnosis object corresponding to the target ECU according to the target ECU.
And the searching unit is used for traversing the diagnostic objects of each layer according to a preset sequence from the diagnostic object of the EV layer until the diagnostic data object which accords with the target identification information is searched to serve as the diagnostic data object to be referred, and returning the information of the diagnostic data object to be referred.
The terminal device 7 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. 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 the terminal device 7 and does not constitute a limitation of the terminal device 7, and may include more or less components than illustrated, or may combine certain components, or different components, e.g., the terminal device may further include an input-output device, a network access device, a bus, etc.
The processor 70 may be a central processing unit (Central Processing Unit, CPU), or may be another general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a Field-programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or the like. 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 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) or 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 as well as other programs and data required by the terminal device. The memory 71 may also be used for temporarily storing 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-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a 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 process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
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 solution. 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 manners. For example, the apparatus/terminal device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each method embodiment described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; 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 scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims (7)

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 an ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnosis data object to be quoted 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;
traversing the EV layer diagnosis object;
if the EV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing all shared data SD layer diagnosis objects;
If all the SD layer diagnosis objects do not have the diagnosis data objects consistent with the target identification information, traversing the basic variable BV layer diagnosis objects inherited by the EV layer diagnosis objects;
if the BV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing a first PR layer diagnosis object referenced in the BV layer diagnosis object;
if the first PR layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing the FG layer diagnosis object inherited by the BV layer diagnosis object;
and if the FG layer diagnosis object does not have the diagnosis data object conforming to the target identification information, traversing a second PR layer diagnosis object referenced in the FG layer diagnosis object until the diagnosis data object conforming to the target identification information is found to serve as the diagnosis data object to be referenced, and returning the information of the diagnosis data object to be referenced.
2. The diagnostic data referencing method of claim 1, wherein after said traversing said basic variable BV layer diagnostic object inherited by said EV layer diagnostic object, further comprising:
and if the BV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing all protocol PR layer diagnosis objects.
3. The diagnostic data referencing method according to claim 2, wherein after said traversing all protocol PR layer diagnostic objects, further comprising:
and if all the PR layer diagnosis objects do not have the diagnosis data objects consistent with the target identification information, traversing the function group FG layer diagnosis objects inherited by the BV layer diagnosis objects.
4. 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.
5. A vehicle diagnostic data referencing apparatus, comprising:
the system comprises an acquisition unit, a diagnosis unit and a reference unit, wherein the acquisition unit is used for acquiring a diagnosis instruction and determining a target ECU and target identification information, wherein the target ECU is an ECU to be diagnosed currently, and the target identification information is identification information corresponding to a diagnosis data object to be quoted when the target ECU is diagnosed;
an EV layer diagnosis object determining unit, configured to determine an EV layer diagnosis object corresponding to the target ECU according to the target ECU;
the searching unit is used for traversing each layer of diagnostic objects according to a preset sequence from the EV layer of diagnostic objects until the diagnostic data object which accords with the target identification information is searched for as the diagnostic data object to be referred, and returning the information of the diagnostic data object to be referred;
The search unit includes:
the first traversing module is used for traversing the EV layer diagnosis object; if the EV layer diagnosis object does not have the diagnosis data object which accords with the target identification information, traversing all SD layer diagnosis objects;
the second traversing module is used for traversing BV layer diagnosis objects inherited by the EV layer diagnosis objects if all the SD layer diagnosis objects do not have diagnosis data objects consistent with the target identification information;
a fifth traversing 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 traversing module, configured to traverse, if the first PR layer diagnostic object does not have a diagnostic data object that matches the target identification information, an FG layer diagnostic object that is inherited by the BV layer diagnostic object;
and a seventh traversing module, configured to traverse 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 that matches the target identification information.
6. 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 processor, when executing the computer program, causes the terminal device to carry out the steps of the method according to any one of claims 1 to 4.
7. A computer readable storage medium storing a computer program, characterized in that the computer program, when executed by a processor, causes a terminal device to carry out the steps of the method according to any one of claims 1 to 4.
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 CN112445816A (en) 2021-03-05
CN112445816B true 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)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113065033B (en) * 2021-03-22 2023-03-14 江铃汽车股份有限公司 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

Also Published As

Publication number Publication date
CN112445816A (en) 2021-03-05

Similar Documents

Publication Publication Date Title
CN110309125B (en) Data verification method, electronic device and storage medium
CN110083145B (en) Automobile diagnosis method and device, readable storage medium and automobile diagnosis instrument
CN111552267B (en) Vehicle diagnosis method and device and vehicle diagnosis equipment
CN110601880A (en) Cloud platform, service processing method, command interface and computer equipment
CN111813095A (en) Vehicle diagnosis method, device and medium
CN108345658A (en) Algorithm calculates decomposing process, server and the storage medium of track
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
CN112506999B (en) Cloud computing and artificial intelligence based big data mining method and digital content server
CN112445797B (en) Vehicle diagnosis data reference method, device, terminal equipment and storage medium
CN113848862B (en) Diagnostic software acquisition method, device, communication equipment and storage medium
CN111309972B (en) Data processing method, device, terminal equipment and storage medium
CN111736848B (en) Packet conflict positioning method, device, electronic equipment and readable storage medium
CN111930097B (en) Vehicle diagnostic data analysis method, device, equipment and storage medium
CN114491044A (en) Log processing method and device
CN113342430A (en) Fault code processing method and device, terminal equipment and readable storage medium
CN112711584A (en) Data checking method, checking device, terminal equipment and readable storage medium
CN112433943A (en) Method, device, equipment and medium for detecting environment variable based on abstract syntax tree
CN110297947A (en) A kind of data calling method, device and electronic equipment
CN112104766B (en) Diagnostic protocol reconstruction method, device, terminal equipment and storage medium
CN113535881B (en) Fault code information storage method, device, communication equipment and storage medium
CN112445491A (en) File sequence processing method and device, terminal equipment and storage medium
CN114326674B (en) ECU (electronic control Unit) refreshing method and device, electronic equipment and storage medium
CN116208661B (en) Function configuration adaptation method, device, vehicle and storage medium
CN114818645B (en) Automatic report generation method, device, equipment and medium based on data body

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