CN111103861B

CN111103861B - Method and apparatus for developing an integrated system based on vehicle after-market diagnostic needs

Info

Publication number: CN111103861B
Application number: CN201811249208.1A
Authority: CN
Inventors: 陆泳; 徐伟卿; 徐继财; 赵俊; 张军; 杨颖文; 丁楠
Original assignee: SAIC General Motors Corp Ltd; Pan Asia Technical Automotive Center Co Ltd
Current assignee: SAIC General Motors Corp Ltd; Pan Asia Technical Automotive Center Co Ltd
Priority date: 2018-10-25
Filing date: 2018-10-25
Publication date: 2023-04-07
Anticipated expiration: 2038-10-25
Also published as: CN111103861A

Abstract

The present invention relates to the field of vehicle after-market diagnostics, and more particularly, to a method, apparatus, computer-readable storage medium, and integration system for developing an integration system based on vehicle after-market diagnostic requirements. A method for developing an integrated system based on vehicle after-market diagnostic needs according to one aspect of the present invention comprises the steps of: modularizing and analyzing the diagnosis standard of an electronic module in the vehicle to establish a structured data chain of a unified template; importing diagnostic data based on the structured data chain; authorizing and verifying the diagnostic data and converting the authorized and verified diagnostic data into ODX diagnostic data; and performing real-time vehicle verification and verification on the ODX diagnosis data to construct an ODX diagnosis database.

Description

Method and apparatus for developing an integrated system based on vehicle after-market diagnostic requirements

Technical Field

The present invention relates to the field of vehicle after-market diagnostics, and more particularly, to a method, apparatus, computer-readable storage medium, and integrated system for developing an integrated system based on vehicle after-market diagnostic requirements.

Background

Electronic and electrical modules are widely popularized in application of vehicle occupancy, and technologies of vehicle-mounted data bus and electronic module OBD diagnosis are rapidly popularized and applied. The post-sale maintainability of electronic module diagnosis is more and more important, and powerful guarantee is provided for maintenance technicians such as a 4S shop or a third-party maintenance shop to actually solve vehicle troubleshooting.

The diagnostic specification in the electronic module describes a series of diagnostic services, defines request response rules between the ECU and the diagnostic instrument, processing behaviors of the ECU on request messages and information meanings of the request messages and the response messages, and is an important part for diagnostic communication between the ECU and the diagnostic instrument. However, the development of the diagnostic specification of the electronic module is still developed on the basis of word and excel, so that the workload and the efficiency of after-sale diagnostic development are high, and related data and information are missed and error risks exist.

Disclosure of Invention

It is an object of the present invention to provide a method for developing vehicle-based after-market diagnostic needs that improves the standardization, completeness of diagnostic need development and the efficiency and quality of development efforts.

A method for developing a vehicle based on an after-market diagnostic need according to one object of the present invention comprises the steps of:

modularizing and analyzing the diagnosis standard of an electronic module in the vehicle to establish a structured data chain of a unified template;

importing diagnostic data based on the structured data chain;

authorizing and verifying the diagnostic data and converting the authorized and verified diagnostic data into ODX diagnostic data; and

and performing real-time verification and verification on the ODX diagnosis data to construct an ODX diagnosis database.

Optionally, in the method, the step of modularly parsing the diagnostic specification of the electronic module in the vehicle includes:

developing a format unified template based on the diagnosis requirement data of each module aiming at the diagnosis specification of each electronic module; and

and interpreting the diagnosis specification of the electronic module based on the format unified template so as to establish a structured data chain of the unified module.

Optionally, in the above method, the structured data chain is classified, and the record data of each type of data is defined to import the structured data chain in the format of EXCEL.

Optionally, in the above method, the authorized and verified diagnostic data and the ODX diagnostic data are converted to each other to achieve data synchronization and verification, and the authorized and verified diagnostic data and the ODX diagnostic data are synchronized with the diagnostic data.

Optionally, in the above method, the integrated system provides an ODX conversion plug-in to convert the authorized and verified diagnostic data into ODX diagnostic data.

Optionally, in the above method, the performing real-vehicle verification and verification on the ODX diagnostic data further comprises:

if a problem is found in real vehicle verification and verification, modifying and editing the ODX diagnostic data;

converting the ODX conversion plug-in into an EXCEL format file through the ODX conversion plug-in the integrated system; and

modifying error information against a diagnostic specification to update error information in the ODX diagnostic data.

Optionally, in the above method, the ODX diagnostic database is provided to downstream authorized diagnostic software for use.

It is another object of the present invention to provide an integrated system developed based on the after-market diagnostic needs of a vehicle that provides a complete system from the formulation, interpretation, diagnostic need development, real-time verification and verification of diagnostic specifications.

An integrated system developed based on the need for after-market vehicle diagnostics according to another object of the present invention comprises:

the system comprises a first module, a second module and a third module, wherein the first module is used for modularly analyzing the diagnosis specification of an electronic module in a vehicle to establish a structured data chain of a unified template;

a second module for importing diagnostic data based on the structured data chain;

a third module for authorizing and verifying the diagnostic data and converting the authorized and verified diagnostic data into ODX diagnostic data; and

and the fourth module is used for carrying out real-vehicle verification and verification on the ODX diagnosis data so as to construct an ODX diagnosis database.

It is still another object of the present invention to provide an apparatus for developing an integrated system based on after-market diagnostic needs of a vehicle, which is capable of developing an integrated system based on after-market diagnostic needs of a vehicle in a standardized and efficient manner.

A further object of the present invention is to provide an apparatus for developing an integrated system based on vehicle after-market diagnostic requirements, comprising a memory, a processor and a computer program stored on said memory and executable on said processor, wherein said computer program is executed to implement the steps of any of the methods described above.

It is still another object of the present invention to provide a computer-readable storage medium that can develop an integrated system based on after-market vehicle diagnostic needs in a standardized and efficient manner.

According to a further object of the invention, a computer-readable storage medium has stored thereon a computer program which, when executed by a processor, carries out the steps of any of the methods described hereinbefore.

The system integrates the database management of the diagnosis standard data, the editing of the software requirement data and the conversion among a plurality of template data of the real vehicle verification to generate the ODX database and the software requirement data required by the development of the after-sales diagnosis software, thereby reducing the workload of engineering personnel and improving the convenience and accuracy of the vehicle verification.

Drawings

The above and/or other aspects and advantages of the present invention will become more apparent and more readily appreciated from the following description of the various aspects taken in conjunction with the accompanying drawings, in which like or similar elements are designated with like reference numerals. The drawings comprise:

FIG. 1 is a schematic diagram of an integrated system developed based on after-market vehicle diagnostic needs in accordance with one embodiment of the present invention.

FIG. 2 is a flow chart of a method of determining ODX diagnostic data as applied to the embodiment shown in FIG. 1.

Fig. 3 is a flowchart of a method of constructing an ODX diagnosis database applied to the embodiment shown in fig. 1.

FIG. 4 is a structured data chain of unified templates developed based on after-market vehicle diagnostic requirements, according to another embodiment of the present invention.

FIG. 5 is a schematic block diagram of an apparatus for developing an integrated system based on after-market vehicle diagnostic needs in accordance with yet another embodiment of the present invention.

Detailed Description

The present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the invention are shown. This invention may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. The embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

In the present specification, words such as "comprise" and "comprises" mean that, in addition to elements and steps directly and unequivocally stated in the specification and claims, the technical solution of the present invention does not exclude other elements and steps not directly or unequivocally stated.

Terms such as "first" and "second" do not denote an order of elements in time, space, size, etc., but rather are used to distinguish one element from another.

FIG. 1 is a schematic diagram of an integrated system developed based on after-market vehicle diagnostic needs in accordance with one embodiment of the present invention. The system according to the present embodiment may, by way of example but not necessarily, provide for implementing the method steps to be described below in a manner having separate functional modules. Alternatively, the above-described independent functional module may also be integrated with other functional modules in the vehicle.

The integrated system 10 developed based on after-market vehicle diagnostic needs shown in fig. 1 includes a first module 110, a second module 120, a third module 130, and a fourth module 140. In the present embodiment, the first module 110 is configured to perform modular parsing on the diagnostic criteria of the electronic modules in the vehicle to establish a structured data chain of unified templates; a second module 120 for importing diagnostic data based on the structured data chain; a third module 130 for authorizing and verifying the diagnostic data and converting the authorized and verified diagnostic data into ODX diagnostic data; and the fourth module 140 performs real-time validation and verification of the ODX diagnostic data to construct an ODX diagnostic database. Preferably, in this embodiment, the diagnosis instructions, parameters and functions related to after-sales repair in the diagnosis specification can be edited into the first module 110 through a set interface and template, and the initial diagnosis data can be imported into the second module 120 through diagnosis specification interpretation and diagnosis requirement development. Preferably, a template with a uniform format developed based on the diagnosis requirement data of each module for the diagnosis specification of each electronic module may be integrated in the integration system 10, and the template may be used to interpret the diagnosis specification of the electronic module and edit the interpreted diagnosis specification into the first module 110, or may be directly edited in the original data of the system 10 according to the information such as the model of the electronic module. Preferably, the second module 120 can import the data of the diagnosis development requirement into the third module 130 in the EXCEL format for authorization and verification based thereon. Preferably, an ODX conversion plug-in may be integrated into the third module 130 to convert the imported authorized and verified EXCEL data into ODX diagnostic data for import into the fourth module 140. Optionally, the ODX conversion plug-in may be configured to: based on the actual requirements of the integrated system 10 and third party engineering diagnostic equipment software for ODX diagnostic data, ODX format analysis is performed on each type of related data. In the fourth module 140, the vehicle is subjected to diagnosis instruction operation by the external diagnostic apparatus, and the ODX diagnosis data is verified by the real vehicle diagnosis instruction verification. If problems are found, the ODX data can be modified and configured on-the-fly. And after the verification is finished, constructing a complete ODX diagnosis database for downstream authorized diagnosis software to use.

FIG. 2 is a flow chart of a method of determining ODX diagnostic data as applied to the embodiment shown in FIG. 1. As shown in fig. 2, at step 210, the diagnostic criteria and the information about the electronic module are interpreted and edited into the system, or edited directly into the original data of the system according to the information about the model of the electronic module. Step 220 is then entered for structured data processing of diagnostic specification definitions using data modeling through the grooming and unification of diagnostic specifications for a wide variety of vehicle electronic modules in step 210. Because the diagnostic specification formats and contents of each electronic module are very different, and the development templates of each engineer and technician are also inconsistent, it is necessary to develop a diagnostic specification for each electronic module, develop a format unifying template based on the data of the diagnostic requirements of each module, and structure the diagnostic specification of the electronic module based on the format unifying template to establish a structured data chain of the unifying template. Preferably, the structured data chain can be classified and the record data of each type of data is defined to authorize and verify the structured data chain by the format of EXCEL. For example, the structured data may be divided into 11 classes, which are a page class, an application information class, a fault code class, a control function class, a data display class, a data list class, a program scope class, a programming class, a version information class, and the like. The log data for each type of data may be defined, for example, the fault code class: fault code number, fault description, FTB (small code) number, FTB description, priority, GTOC directory, ECU, remark, vehicle type application, etc. Through the steps, the development of the diagnosis requirement of the integrated system can be completed.

After performing step 220, the method shown in FIG. 2 proceeds to step 230. In this step, the authorized diagnosis data is automatically generated based on the format unifying template of the data development of the diagnosis requirement of each module, and the authorized diagnosis data and the system data can be converted to each other. Step 240 is then entered where the authorized diagnostic data is verified by incorporating actual service requirements to output final authorized diagnostic data. Converting the authorized diagnostic data to an ODX database via an ODX conversion plug-in. The authorized diagnostic data is converted to an ODX database by an ODX conversion plug-in, as shown in step 250. Preferably, based on the definition of ODX of IS022901-1 open diagnosis interaction specification, the ODX format of each type of related data IS analyzed based on the actual requirements of an after-sales diagnosis requirement development system and third-party engineering diagnostic instrument software on an ODX database so as to develop the ODX conversion plug-in. For example, for the ODX format analysis of DTC fault code class, the DTC needs to be declared according to IS022901-1, the required DTC information IS compiled, and then the data records are added and deleted according to actual needs.

As shown in fig. 3, in step 310, the ODX diagnostic data is imported into engineering diagnostic software to perform relevant diagnostic command operations on the vehicle through an external diagnostic instrument. If a problem is found, the ODX diagnostic data can be modified and edited directly in the software. If no problem is found, step 320 is entered and a diagnostic code is automatically generated by the engineering diagnostic software based on the ODX diagnostic data.

Then step 330 is entered, in step 330, the ODX diagnostic code is subjected to real vehicle verification through the real vehicle or gantry diagnostic instruction verification, the problems found in the verification are strengthened through the real vehicle verification, and the diagnostic specification or the authorization document is corrected in time to obtain complete ODX diagnostic data.

Step 340 is then entered to determine the accuracy of the complete ODX diagnostic data. If the diagnosis is correct, an ODX diagnosis database is constructed; and if the ODX diagnosis data are wrong, immediately configuring the ODX data according to the actual measurement result so as to update the ODX diagnosis data in real time.

It should be noted that the complete ODX diagnosis database verified by the real vehicle is converted into the EXCEL file through the ODX conversion plug-in provided by the present invention, and serves as the authorized EXCEL diagnosis requirement development file to be provided for the downstream maintenance information development and maintenance diagnosis software development.

As shown in FIG. 4, the integrated system of the present invention builds a structured data chain to allow database processing of all data. The data is divided into 11 categories, namely page category, application information category, fault code category, control function category, data display category, data list category, program scope category, programming category, version information category and the like. A specific example is shown in fig. 4, in which the record data of each type of data is defined. For example, the failing code class: fault code number, fault code description, FTB small code number, FTB small code description, priority level and freeze frame data. In this way, the data inside the system of the present invention can output the diagnosis and development requirement data in the format of EXCEL, so that the output EXCEL data can be converted into an ODX database file by the ODX conversion plug-in provided by the system of the present invention. Preferably, based on the definition of ODX in IS022901-1 open diagnosis interaction specification, the ODX format of each kind of related data IS analyzed based on the actual requirements of the system and third-party engineering diagnostic equipment software on an ODX database, so as to develop an ODX conversion plug-in. For example, the ODX data parsed for the data of the DTC fault code class is as follows:

with reference to the ODX format definition of the ISO22901 open diagnostics specification, ODX is described in the unified modeling language, ULM, diagram form, and the data exchange format uses the configuration scripting language (XML). For the script definition of the XML of the DTC, firstly, referring to the data object attribute definition of the relevant DTC-DOP in ISO22901-1, including data extension parameters, formula conversion, result types and the like, and completing the definition of the script. And then, the developed DTC-DOP needs to be loaded into the appointed diagnostic software, and whether the data are normally applied or not is confirmed through compiling, because although the diagnostic software is also developed according to the ODX requirement, certain difference still exists in the actual application, and the DOP coding can be finally determined through verification.

The DTCs are declared according to the requirements of IS022901-1, required DTC information IS written, and then data records are added and deleted according to actual requirements. Preferably, in the specification of IS022900-1, the ODX format of all vehicle electronic modules IS defined, and in practical applications, relevant parameters to be applied for the after-market diagnosis need to be developed according to the ODX requirements of the diagnosis tool.

The apparatus 50 for developing an integrated system based on after-market vehicle diagnostic requirements, shown in fig. 5, comprises a memory 510, a processor 520 and a computer program 530 stored on the memory 510 and executable on the processor 520, wherein execution of the computer program 530 may implement the methods described above with reference to fig. 2 and 3.

According to a further aspect of the invention, a computer-readable storage medium is also provided, on which a computer program is stored which, when being executed by a processor, is adapted to carry out the method described above with reference to fig. 2 and 3.

The embodiments and examples set forth herein are presented to best explain the embodiments in accordance with the present technology and its particular application and to thereby enable those skilled in the art to make and utilize the invention. However, those skilled in the art will recognize that the foregoing description and examples have been presented for the purpose of illustration and example only. The description as set forth is not intended to cover all aspects of the invention or to limit the invention to the precise form disclosed.

In view of the foregoing, the scope of the present disclosure is to be determined by the following claims.

Claims

1. A method for developing an integrated system based on the need for after-market diagnosis of a vehicle, said method comprising the steps of:

modularly analyzing the diagnosis specifications of the electronic modules in the vehicle to establish a structured data chain of unified templates, wherein the diagnosis specifications are subjected to structured data processing by data modeling, and the diagnosis specifications for each electronic module are developed, a format unified template is developed based on data of diagnosis requirements of each module, and the diagnosis specifications of the electronic modules are structured based on the format unified template to establish a structured data chain of unified templates, wherein the structured data chain is classified, and record data of each type of data is defined to authorize and verify the structured data chain in the format of EXCEL; importing diagnostic data based on the structured data chain;

and performing real-time vehicle verification and verification on the ODX diagnosis data to construct an ODX diagnosis database.

2. The method of claim 1, wherein modularly parsing diagnostic specifications for electronic modules in a vehicle comprises:

3. The method of claim 1, wherein:

the authorized and verified diagnostic data and the ODX diagnostic data are transformed to each other to achieve data synchronization and verification, and the authorized and verified diagnostic data and the ODX diagnostic data are synchronized with the diagnostic data.

4. The method of claim 3, wherein the integrated system provides an ODX conversion plug-in to convert the authorized and verified diagnostic data into ODX diagnostic data.

5. The method of claim 1, performing real-vehicle validation and verification of the ODX diagnostic data further comprising:

6. The method of claim 1, further comprising:

providing the ODX diagnostic database to downstream authorized diagnostic software for use.

7. An integrated system developed based on the need for after-market diagnosis of a vehicle, the system comprising the following modules:

a first module for modularly parsing the diagnostic specifications of the electronic modules in the vehicle to establish a structured data chain of unified templates, wherein the diagnostic specifications are structured data processed using data modeling, and the diagnostic specifications for each electronic module are developed, a format unified template is developed based on data of diagnostic requirements of the respective modules, and the diagnostic specifications of the electronic modules are structured based on the format unified template to establish a structured data chain of unified templates, wherein the structured data chain is classified, and log data of each type of data is defined to authorize and verify the structured data chain in the format of EXCEL;

8. An apparatus for developing an integrated system based on vehicle after-market diagnostic needs, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor executes the computer program to implement the method of any one of claims 1-6.

9. A computer readable storage medium having stored thereon a collection of machine executable instructions, wherein said machine executable instructions when executed by a processor implement the method of any one of claims 1-6.