CN104965507A - Method used for generating open diagnostic data exchange database and device - Google Patents
Method used for generating open diagnostic data exchange database and device Download PDFInfo
- Publication number
- CN104965507A CN104965507A CN201510374642.2A CN201510374642A CN104965507A CN 104965507 A CN104965507 A CN 104965507A CN 201510374642 A CN201510374642 A CN 201510374642A CN 104965507 A CN104965507 A CN 104965507A
- Authority
- CN
- China
- Prior art keywords
- diagnostic data
- son file
- identifier
- odx
- definition
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
- G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Computer And Data Communications (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to a method used for generating an open diagnostic data exchange database and a device. The method comprises the steps that diagnostic data in a diagnostic data description file are validated according to pre-conditions; if validation is incorrect, the corresponding diagnostic data are modified according to a validation incorrectness prompt message, and the diagnostic data in the diagnostic data description file are validated again according to the pre-conditions; if validation is correct, the diagnostic data are parsed according to the format of the diagnostic data description file; the parsed diagnostic data are used to generate an XML format file according to a UML model; and XML Schema validation is carried out on the XML format file, so as to generate an ODX database. According to the invention, the workload is greatly reduced; the work efficiency is improved; the process of the method is simple; a development cycle is shortened; and the problems of high error rate and the like of traditional manual ODX database editing are solved.
Description
Technical field
The present invention relates to automobile electronic controller diagnostic design technical field, particularly relate to and a kind ofly generate the method for open diagnostic data switching database, generate the device of open diagnostic data switching database.
Background technology
Based on XML (Extensible Markup Language, extend markup language) ODX (OpenDiagnostic Data Exchange, open diagnostic data exchanges) be a kind of open diagnostic data form, be convenient to exchange diagnosis data, improve research and development, test, production and efficiency after sale, reduce diagnostic data handling cost, mutual for diagnostic data in vehicle Life cycle.The ODX of current latest edition is 2.2.0, and data model is divided into seven layers: ODX-D, ODX-C, ODX-V, ODX-E, ODX-FD, ODX-F, ODX-M.As shown in Figure 1: ODX-D part describes the communication process between diagnostic equipment and ECU (Electronic Control Unit, electronic controller), comprises the request of diagnosis service, response format and used parameter type etc.ODX-C part describes the messaging parameter between diagnostic equipment and ECU, such as network layer timing parameters, application layer timing parameters, baud rate etc.ODX-V describes the information of vehicle, such as OEM (original equipment manufacturer) information, vehicle information, vehicle topology etc.ODX-F part is described the data uploading download, is applied on line refreshable program.ODX-E part describes the configuration information of vehicle, comprises according to specific vehicle environmental, place, enable/to close optional function, setting characteristic curve etc.ODX-FD part describes the diagnostic message of Function-oriented.ODX-M part describes some diagnostic function information that multiple ECU realizes jointly.
Usually EXCEL form is adopted to describe when formulating diagnostic data description document at present, CANdela Studio, ODXStudio editing machine or diagnostic tool collection DTS Venice-ODX editing machine is generally adopted in diagnosis development, according to the diagnostic data description document edit ODX database formulated, carry out diagnosis development and testing so that follow-up.But along with Automobile Electronic Industry development, the ECU quantity that some luxurious car is installed now has exceeded 60, based on the ODX database of each ECU of EXCEL form diagnostic data description document edit, with heavy work load, the possibility of mistake is very high, and the method process is lengthy and tedious, wastes time and energy, construction cycle is long, and efficiency is low.
Summary of the invention
Based on this, be necessary for the problems referred to above, a kind of method and the device that generate open diagnostic data switching database are provided, the workload that ODX diagnostic data base generates can be reduced.
Generate a method for open diagnostic data switching database, comprise step:
According to pre-conditioned, each diagnostic data in diagnostic data description document is verified;
If verify wrong, according to the miscue information of verification, corresponding diagnostic data is modified, and returns according to the pre-conditioned step verified each diagnostic data in diagnostic data description document;
If verify errorless, according to the form of described diagnostic data description document, described each diagnostic data is resolved;
Each diagnostic data after resolving is generated XML format file according to uml model;
XML Schema verification is carried out to described XML format file, generates ODX database.
Generate a device for open diagnostic data switching database, comprise diagnostic data correction verification module, diagnostic data modified module, diagnostic data parsing module, file generating module and database generation module; Diagnostic data modified module is connected with diagnostic data correction verification module respectively with diagnostic data parsing module, and diagnostic data parsing module is connected with database generation module by file generating module;
Diagnostic data correction verification module, for verifying each diagnostic data in diagnostic data description document according to pre-conditioned;
Diagnostic data modified module, for when verifying wrong, according to the miscue information of verification, modifying to corresponding diagnostic data, obtaining new described diagnostic data;
Diagnostic data parsing module, for when verifying errorless, according to the form of described diagnostic data description document, resolves described each diagnostic data;
File generating module, for generating XML format file by each diagnostic data after parsing according to uml model;
Database generation module, for carrying out XML Schema verification to described XML format file, generates ODX database.
The present invention generates the method and apparatus of open diagnostic data switching database, each diagnostic data in existing diagnostic data description document is verified, when verifying errorless, by resolving and uml model diagnostic data, generate the XML format file of ODX, then carry out XML Schema verification, directly generate standardized ODX database.The present invention utilizes diagnostic data description document automatically to generate ODX database, do not need again according to diagnostic data description document edit ODX database in diagnosis development, considerably reduce workload, improve work efficiency, and the method process is simple, shorten the construction cycle, solve the drawbacks such as the error rate height of traditional-handwork editor ODX database.
Accompanying drawing explanation
Fig. 1 is ODX data model schematic diagram in prior art;
Fig. 2 is the schematic flow sheet that the present invention generates the embodiment of the method one of open diagnostic data switching database;
Fig. 3 is the schematic flow sheet that the present invention generates the embodiment of the method two of open diagnostic data switching database;
Fig. 4 is the structural representation that the present invention generates the device embodiment one of open diagnostic data switching database;
Fig. 5 is the structural representation that the present invention generates the device embodiment two of open diagnostic data switching database;
Fig. 6 is the structural representation of son file name definition module embodiments of the present invention;
Fig. 7 is the structural representation of diagnostic data inspection module embodiment of the present invention.
Embodiment
Technical purpose for a better understanding of the present invention, the technical scheme taked and the technique effect reached, be described in detail the specific embodiment of the present invention below in conjunction with accompanying drawing.It should be noted that, first, second word such as grade occurred in literary composition is only to distinguish each technical characteristic, is not limited the order of each technical characteristic and quantity.
As shown in Figure 1, a kind of method generating open diagnostic data switching database, comprises step:
S110, according to pre-conditioned, each diagnostic data in diagnostic data description document to be verified;
If S120 verifies wrong, according to the miscue information of verification, corresponding diagnostic data is modified, and returns according to the pre-conditioned step verified each diagnostic data in diagnostic data description document;
If S130 verifies errorless, according to the form of described diagnostic data description document, described each diagnostic data is resolved;
S140, each diagnostic data after resolving is generated XML format file according to uml model;
S150, XML Schema verification is carried out to described XML format file, generate ODX database.
The form of diagnostic data description document is WORD form or EXCEL form etc., can adopt the existing diagnostic data description document editted, and also according to ODX standard from edlin, then can generate ODX database according to the diagnostic data description document editted.So, as shown in Figure 2, before step S110, can also step be comprised:
S090, each son file title comprised according to ODX standard definition diagnostic data description document;
S100, according to the corresponding diagnostic data of each son file name acquiring, generate diagnostic data description document.
Each son file that diagnostic data description document comprises can be put in one file, also can be each independently file.Such as, if diagnostic data description file format is EXCEL form, then each son file can be each Sheet content of pages inside a Microsoft Excel, also can set up separately Microsoft Excel file for each son file.No matter son file exists in what manner, does not all affect the generation of follow-up ODX database.
In one embodiment, each son file title step comprised according to ODX standard definition diagnostic data description document can comprise:
ECU diagnostic data company information according to ODX standard defines the first son file title, and the first son file title comprises Business Name and company author etc.;
Formulate definition second son file title according to the ECU diagnostic data information of vehicles of ODX standard (ODX-V), the second son file title comprises manufacturer OEM information, vehicle information and vehicle bus topological structure etc.;
Support diagnosing protocol definition the 3rd son file title according to the ECU of ODX standard (ODX-C), the 3rd son file title comprises: network layer timing parameters, application layer timing parameters, baud rate, ECU unit physical addressing address and ECU unit diagnosis functional addressing address etc.;
According to ECU diagnostic data version management information definition the 4th son file title of ODX standard (ADMIN-DATA), the 4th son file title comprises: version information, version establishment date, version author, release status, version modify content and version modify explanation etc.;
Diagnose service parameter definition the 5th son file title according to the ECU of ODX standard (DIAG-COMMS in ODX-D), the 5th son file title comprises: diagnosis service identifier (SERVICE-ID), diagnosis service identifier describe, diagnosis service subfunction identifier, diagnosis service subfunction identifier describe, forbid positive response state, the description of diagnostic session pattern, addressing mode, security access levels, diagnosis service operational phase and negative response description etc.; Forbid that positive response state comprises to support and do not support; Addressing mode comprises physical addressing, functional addressing; Diagnosis service operational phase comprises development phase, the stage of rolling off the production line and stage after sale;
Diagnose service request parameter to define the 6th son file title according to the ECU of ODX standard (REQUESTS in ODX-D), the 6th son file title comprises: diagnose service identifier, diagnose service identifier description, subfunction identifier is served in diagnosis, diagnose and serve the description of subfunction identifier, diagnosis services request diagnostic data identifier, the description of diagnostic data identifier, the description of diagnostic data parameter, diagnostic data parameter, the total amount of byte diagnosing service data and subdata parameter; Subdata parameter comprises: the description of subdata parameter, byte location, Bit position and Bit length, physical values maximal value, physical values minimum value, conversion formula, data type, default value and unit;
According to ECU diagnosis service reception response parameter definition the 7th son file title of ODX standard (POS-RESPONSES in ODX-D), the 7th son file title comprises: diagnose service identifier, diagnose the description of service indications, subfunction identifier is served in diagnosis, diagnose the description of service subfunction identifier, diagnosis service reception response diagnostics data identifier, the description of diagnostic data identifier, the description of diagnostic data parameter, diagnostic data parameter, the total amount of byte diagnosing service reception response data and subdata parameter; Subdata parameter comprises: the description of subdata parameter, byte location, Bit position and Bit length, physical values maximal value, physical values minimum value, conversion formula, data type, default value and unit;
According to ECU diagnosis service negative response parameter definition the 8th son file title of ODX standard (NEG-RESPONSES in ODX-D), 8th son file title comprises: negative response diagnosis service identifier, negative response diagnosis service identifier describes, and service identifier is diagnosed in request, request diagnosis service identifier describes, negative yardage value and description thereof are served in diagnosis;
According to ECU tracing trouble code parameters definition the 9th son file title of ODX standard (DTC-DOPS in ODX-D), the 9th son file title comprises: the description of diagnostic trouble code hexadecimal values, diagnostic trouble code, diagnostic trouble code show code, trouble code attribute and the definition of diagnostic trouble code state etc.;
Describe definition the tenth son file title according to the data uploading download of ODX standard (ODX-F), the tenth son file title comprises: start address, data length and refreshing block size etc.;
According to vehicle configuration information definition the 11 son file title of ODX standard (ODX-E), the 11 son file title comprises: according to specific vehicle environmental, place, enable/to close optional function, setting characteristic curve etc.
After defining each son file title, namely can according to each son file title, corresponding diagnostic data is filled in each son file by the mode such as artificial, obtains diagnostic data description document.Based on the diagnostic data description document of above-mentioned generation, in one embodiment, step S110 can comprise:
Whether verify containing Business Name and company author in the first son file, namely whether the diagnostic data of Business Name and company author fills in the first son file;
Whether verify in the second son file containing manufacturer OEM information, vehicle information and vehicle bus topological structure;
Whether the network layer timing parameters verified in the 3rd son file meets preset range; Whether application layer timing parameters meets preset range; Whether baud rate meets preset range; Whether ECU unit physical addressing address meets preset range; Whether ECU unit diagnosis functional addressing address meets preset range;
Whether the version information form verified in the 4th son file meets ODX format standard; Whether version establishment date format meets ODX format standard; Version author and release status whether correct; Whether version modify content and version modify illustrate correct;
Verify in the 5th son file and diagnose service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition; Diagnosis service identifier describes and whether diagnosis service subfunction identifier descriptor format meets ODX format standard; Whether correctly forbid that positive response state (support, do not support), the description of diagnostic session pattern, addressing mode, security access levels, diagnosis service operational phase (development phase, the stage of rolling off the production line, after sale stage) and negative response describe scope;
Verify in the 6th son file and diagnose service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition; Whether diagnosis services request diagnostic data identifier meets the diagnosing protocol range of definition; Diagnosis service identifier describes, diagnosis service subfunction identifier describes, diagnostic data identifier describes, diagnostic data parameter describes and whether subdata parameter descriptor format meets the requirement of ODX format standard; Whether the total amount of byte of diagnosis service data equals the subdata total bytes defined; Whether Bit position and the Bit length of subdata byte location and subdata is consistent; Whether the conversion formula form of subdata meets ODX format standard; Whether the maximal value calculated according to conversion formula is consistent with the physical values maximal value defined and physical values minimum value with minimum value; Whether data type is correct; Whether unit form meets the requirement of ODX format standard;
Verify in the 7th son file and diagnose service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition; Whether diagnosis service reception response diagnostics data identifier meets the diagnosing protocol range of definition; Diagnosis service identifier describes, diagnosis service subfunction identifier describes, diagnostic data identifier describes, diagnostic data parameter describes and whether subdata parameter descriptor format meets the requirement of ODX format standard; Whether the total amount of byte of diagnosis service reception response data equals the subdata total bytes defined; Whether Bit position and the Bit length of subdata byte location and subdata is consistent; Whether the conversion formula form of subdata meets ODX format standard; Whether the maximal value calculated according to conversion formula is consistent with the physical values maximal value defined and physical values minimum value with minimum value; Whether data type is correct; Whether unit form meets the requirement of ODX format standard;
Verify negative response diagnosis service identifier in the 8th son file, request diagnosis service identifier and diagnosis service negative yardage value and whether meet diagnosing protocol definition; Negative response diagnosis service identifier describes, request diagnosis service identifier describes and whether diagnosis service negative yardage value descriptor format meets the requirement of ODX format standard;
Verify diagnostic trouble code hexadecimal values form and scope in the 9th son file and whether meet diagnosing protocol definition; Whether diagnostic trouble code hexadecimal values is consistent with diagnostic trouble code show code; Diagnostic trouble code describes and whether trouble code attribute form meets ODX format standard; Whether the definition of diagnostic trouble code state meets diagnosing protocol definition;
Verify in the tenth son file and refresh block size and whether meet diagnosing protocol requirement (being less than or equal to 4096); Whether start address and the data length of definition equal data in actual refreshing file;
Verify according to specific vehicle environmental in the 11 son file, place, enable/to close optional function, whether setting characteristic curve is correct.
Each diagnostic data in diagnostic data description document is verified, miscue information reminding function is set, when some diagnostic data is wrong, according to the miscue information ejected, modify to corresponding diagnostic data, then back-checking step verifies.All diagnostic data verifications are errorless, then resolve each diagnostic data according to the form of diagnostic data description document.Such as, the form of diagnostic data description document is EXCEL, then adopt EXCEL Data Analysis software to resolve each diagnostic data.
After being parsed each diagnostic data, based on UML (Unified Modeling Language, unified modeling language) model generation XML format file.Then XMLSchema (extend markup language framework) verification is carried out to the XML format file generated, generate standardized ODX database.Wherein the generation of XML format file and the XML Schema of XML format file verify and all can realize according to mode existing in prior art.
Based on same inventive concept, the present invention also provides a kind of device generating open diagnostic data switching database, is described in detail below in conjunction with the embodiment of accompanying drawing to apparatus of the present invention.
As shown in Figure 4, a kind of device generating open diagnostic data switching database, comprises diagnostic data correction verification module 410, diagnostic data modified module 420, diagnostic data parsing module 430, file generating module 440 and database generation module 450; Diagnostic data modified module 420 is connected with diagnostic data correction verification module 410 respectively with diagnostic data parsing module 430, and diagnostic data parsing module 430 is connected with database generation module 450 by file generating module 440;
Diagnostic data correction verification module 410, for verifying each diagnostic data in diagnostic data description document according to pre-conditioned;
Diagnostic data modified module 420, for when verifying wrong, according to the miscue information of verification, modifying to corresponding diagnostic data, obtaining new described diagnostic data; Diagnostic data correction verification module 410 re-starts diagnostic data verification;
Diagnostic data parsing module 430, for when verifying errorless, according to the form of described diagnostic data description document, resolves described each diagnostic data;
File generating module 440, for generating XML format file by each diagnostic data after parsing according to uml model;
Database generation module 450, for carrying out XML Schema verification to described XML format file, generates ODX database.
The form of diagnostic data description document is WORD form or EXCEL form etc.Each son file that diagnostic data description document comprises can be put in one file, also can be each independently file.As shown in Figure 5, apparatus of the present invention can also comprise son file name definition module 460 and description document generation module 470, and son file name definition module 460 is connected with diagnostic data correction verification module 410 by description document generation module 470;
Son file name definition module 460, for each son file title comprised according to ODX standard definition diagnostic data description document;
Description document generation module 470, for according to the corresponding diagnostic data of each son file name acquiring, generates diagnostic data description document.
As shown in Figure 6, son file name definition module 460 can comprise:
First son file name definition unit 4601, define the first son file title for the ECU diagnostic data company information according to ODX standard, the first son file title comprises Business Name and company author etc.;
Second son file name definition unit 4602, for formulating definition second son file title according to the ECU diagnostic data information of vehicles of ODX standard (ODX-V), the second son file title comprises manufacturer OEM information, vehicle information and vehicle bus topological structure etc.;
3rd son file name definition unit 4603, for supporting diagnosing protocol definition the 3rd son file title according to the ECU of ODX standard (ODX-C), the 3rd son file title comprises: network layer timing parameters, application layer timing parameters, baud rate, ECU unit physical addressing address and ECU unit diagnosis functional addressing address etc.;
4th son file name definition unit 4604, for ECU diagnostic data version management information definition the 4th son file title according to ODX standard (ADMIN-DATA), the 4th son file title comprises: version information, version establishment date, version author, release status, version modify content and version modify explanation etc.;
5th son file name definition unit 4605, for diagnosing service parameter definition the 5th son file title according to the ECU of ODX standard (DIAG-COMMS in ODX-D), the 5th son file title comprises: diagnosis service identifier (SERVICE-ID), diagnosis service identifier describe, diagnosis service subfunction identifier, diagnosis service subfunction identifier describe, forbid positive response state, the description of diagnostic session pattern, addressing mode, security access levels, diagnosis service operational phase and negative response description etc.; Forbid that positive response state comprises to support and do not support; Addressing mode comprises physical addressing, functional addressing; Diagnosis service operational phase comprises development phase, the stage of rolling off the production line and stage after sale;
6th son file name definition unit 4606, for diagnosing service request parameter to define the 6th son file title according to the ECU of ODX standard (REQUESTS in ODX-D), the 6th son file title comprises: diagnose service identifier, diagnose service identifier description, subfunction identifier is served in diagnosis, diagnose and serve the description of subfunction identifier, diagnosis services request diagnostic data identifier, the description of diagnostic data identifier, the description of diagnostic data parameter, diagnostic data parameter, the total amount of byte diagnosing service data and subdata parameter; Subdata parameter comprises: the description of subdata parameter, byte location, Bit position and Bit length, physical values maximal value, physical values minimum value, conversion formula, data type, default value and unit;
7th son file name definition unit 4607, for ECU diagnosis service reception response parameter definition the 7th son file title according to ODX standard (POS-RESPONSES in ODX-D), the 7th son file title comprises: diagnose service identifier, diagnose the description of service indications, subfunction identifier is served in diagnosis, diagnose the description of service subfunction identifier, diagnosis service reception response diagnostics data identifier, the description of diagnostic data identifier, the description of diagnostic data parameter, diagnostic data parameter, the total amount of byte diagnosing service reception response data and subdata parameter; Subdata parameter comprises: the description of subdata parameter, byte location, Bit position and Bit length, physical values maximal value, physical values minimum value, conversion formula, data type, default value and unit;
8th son file name definition unit 4608, for ECU diagnosis service negative response parameter definition the 8th son file title according to ODX standard (NEG-RESPONSES in ODX-D), 8th son file title comprises: negative response diagnosis service identifier, negative response diagnosis service identifier describes, and service identifier is diagnosed in request, request diagnosis service identifier describes, negative yardage value and description thereof are served in diagnosis;
9th son file name definition unit 4609, for ECU tracing trouble code parameters definition the 9th son file title according to ODX standard (DTC-DOPS in ODX-D), the 9th son file title comprises: the description of diagnostic trouble code hexadecimal values, diagnostic trouble code, diagnostic trouble code show code, trouble code attribute and the definition of diagnostic trouble code state etc.;
Tenth son file name definition unit 46010, for describing definition the tenth son file title according to the data uploading download of ODX standard (ODX-F), the tenth son file title comprises: start address, data length and refreshing block size etc.;
11 son file name definition unit 46011, for vehicle configuration information definition the 11 son file title according to ODX standard (ODX-E), the 11 son file title comprises: according to specific vehicle environmental, place, enable/to close optional function, setting characteristic curve etc.
Based on the diagnostic data description document of above-mentioned generation, in one embodiment, as shown in Figure 7, described diagnostic data correction verification module 410 can comprise:
First son file verification unit 4101, whether for verifying containing Business Name and company author in the first son file, namely whether the diagnostic data of Business Name and company author fills in the first son file;
Whether the second son file verification unit 4102, for verifying in the second son file containing manufacturer OEM information, vehicle information and vehicle bus topological structure;
Whether the 3rd son file verification unit 4103, meet preset range for the network layer timing parameters verified in the 3rd son file; Whether application layer timing parameters meets preset range; Whether baud rate meets preset range; Whether ECU unit physical addressing address meets preset range; Whether ECU unit diagnosis functional addressing address meets preset range;
Whether the 4th son file verification unit 4104, meet ODX format standard for the version information form verified in the 4th son file; Whether version establishment date format meets ODX format standard; Correctly whether, whether version modify content and version modify illustrate correct for version author and release status;
5th son file verification unit 4105, diagnoses service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition for verifying in the 5th son file; Diagnosis service identifier describes and whether diagnosis service subfunction identifier descriptor format meets ODX format standard; Whether correctly forbid that positive response state (support, do not support), the description of diagnostic session pattern, addressing mode, security access levels, diagnosis service operational phase (development phase, the stage of rolling off the production line, after sale stage) and negative response describe scope;
6th son file verification unit 4106, diagnoses service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition for verifying in the 6th son file; Whether diagnosis services request diagnostic data identifier meets the diagnosing protocol range of definition; Diagnosis service identifier describes, diagnosis service subfunction identifier describes, diagnostic data identifier describes, diagnostic data parameter describes and whether subdata parameter descriptor format meets the requirement of ODX format standard; Whether the total amount of byte of diagnosis service data equals the subdata total bytes defined; Whether Bit position and the Bit length of subdata byte location and subdata is consistent; Whether the conversion formula form of subdata meets ODX format standard; Whether the maximal value calculated according to conversion formula is consistent with the physical values maximal value defined and physical values minimum value with minimum value; Whether data type is correct; Whether unit form meets the requirement of ODX format standard;
7th son file verification unit 4107, diagnoses service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition for verifying in the 7th son file; Whether diagnosis service reception response diagnostics data identifier meets the diagnosing protocol range of definition; Diagnosis service identifier describes, diagnosis service subfunction identifier describes, diagnostic data identifier describes, diagnostic data parameter describes and whether subdata parameter descriptor format meets the requirement of ODX format standard; Whether the total amount of byte of diagnosis service reception response data equals the subdata total bytes defined; Whether Bit position and the Bit length of subdata byte location and subdata is consistent; Whether the conversion formula form of subdata meets ODX format standard; Whether the maximal value calculated according to conversion formula is consistent with the physical values maximal value defined and physical values minimum value with minimum value; Whether data type is correct; Whether unit form meets the requirement of ODX format standard;
Whether the 8th son file verification unit 4108, meet diagnosing protocol definition for verifying negative response diagnosis service identifier in the 8th son file, request diagnosis service identifier and diagnosis service negative yardage value; Negative response diagnosis service identifier describes, request diagnosis service identifier describes and whether diagnosis service negative yardage value descriptor format meets the requirement of ODX format standard;
Whether the 9th son file verification unit 4109, meet diagnosing protocol definition for verifying diagnostic trouble code hexadecimal values form and scope in the 9th son file; Whether diagnostic trouble code hexadecimal values is consistent with diagnostic trouble code show code; Diagnostic trouble code describes and whether trouble code attribute form meets ODX format standard; Whether the definition of diagnostic trouble code state meets diagnosing protocol definition;
Tenth son file verification unit 41010, refreshes block size whether meet diagnosing protocol requirement (being less than or equal to 4096) for verifying in the tenth son file; Whether start address and the data length of definition equal data in actual refreshing file;
11 son file verification unit 41011, for verifying according to specific vehicle environmental in the 11 son file, place, enable/to close optional function, whether setting characteristic curve is correct.
Each diagnostic data in diagnostic data correction verification module 410 pairs of diagnostic data description document verifies.When some diagnostic data is wrong, diagnostic data modified module 420, according to the miscue information ejected, is modified to corresponding diagnostic data, and then diagnostic data correction verification module 410 re-starts diagnostic data verification.When all diagnostic data verifications are errorless, diagnostic data parsing module 430 is resolved each diagnostic data according to the form of diagnostic data description document.After being parsed each diagnostic data, file generating module 440 generates XML format file based on uml model.Then database generation module 450 carries out XML Schema verification to the XML format file generated, and generates standardized ODX database.Wherein file generating module 440 generates XML format file and database generation module 450 pairs of XML format files and carries out XMLSchema verification and all can realize according to mode existing in prior art.
The present invention generates the method and apparatus of open diagnostic data switching database, diagnostic data description document is utilized automatically to generate ODX database, do not need again according to diagnostic data description document edit ODX database in diagnosis development, considerably reduce workload, improve work efficiency, and the method process is simple, shortens the construction cycle, solve the drawbacks such as the error rate height of traditional-handwork editor ODX database.
Each technical characteristic of the above embodiment can combine arbitrarily, for making description succinct, the all possible combination of each technical characteristic in above-described embodiment is not all described, but, as long as the combination of these technical characteristics does not exist contradiction, be all considered to be the scope that this instructions is recorded.
The above embodiment only have expressed several embodiment of the present invention, and it describes comparatively concrete and detailed, but can not therefore be construed as limiting the scope of the patent.It should be pointed out that for the person of ordinary skill of the art, without departing from the inventive concept of the premise, can also make some distortion and improvement, these all belong to protection scope of the present invention.Therefore, the protection domain of patent of the present invention should be as the criterion with claims.
Claims (10)
1. generate a method for open diagnostic data switching database, it is characterized in that, comprise step:
According to pre-conditioned, each diagnostic data in diagnostic data description document is verified;
If verify wrong, according to the miscue information of verification, corresponding diagnostic data is modified, and returns according to the pre-conditioned step verified each diagnostic data in diagnostic data description document;
If verify errorless, according to the form of described diagnostic data description document, described each diagnostic data is resolved;
Each diagnostic data after resolving is generated XML format file according to uml model;
XML Schema verification is carried out to described XML format file, generates ODX database.
2. the method for the open diagnostic data switching database of generation according to claim 1, is characterized in that, according to pre-conditioned each diagnostic data in diagnostic data description document verified before, also comprise step:
According to each son file title that ODX standard definition diagnostic data description document comprises;
According to the corresponding diagnostic data of each son file name acquiring, generate diagnostic data description document.
3. the method for the open diagnostic data switching database of generation according to claim 2, is characterized in that, the step defining the title of each son file that diagnostic data description document comprises according to ODX standard comprises:
ECU diagnostic data company information according to ODX standard defines the first son file title, and the first son file title comprises Business Name and company author;
Formulate definition second son file title according to the ECU diagnostic data information of vehicles of ODX standard, the second son file title comprises manufacturer OEM information, vehicle information and vehicle bus topological structure;
Support diagnosing protocol definition the 3rd son file title according to the ECU of ODX standard, the 3rd son file title comprises: network layer timing parameters, application layer timing parameters, baud rate, ECU unit physical addressing address and ECU unit diagnosis functional addressing address;
According to ECU diagnostic data version management information definition the 4th son file title of ODX standard, the 4th son file title comprises: version information, version establishment date, version author, release status, version modify content and version modify explanation;
Diagnose service parameter definition the 5th son file title according to the ECU of ODX standard, the 5th son file title comprises: diagnosis service identifier, diagnosis service identifier describe, diagnosis service subfunction identifier, diagnosis service subfunction identifier describe, forbid that positive response state, the description of diagnostic session pattern, addressing mode, security access levels, diagnosis service operational phase and negative response describe; Forbid that positive response state comprises to support and do not support; Addressing mode comprises physical addressing, functional addressing; Diagnosis service operational phase comprises development phase, the stage of rolling off the production line and stage after sale;
Diagnose service request parameter to define the 6th son file title according to the ECU of ODX standard, the 6th son file title comprises: diagnose service identifier, diagnose service identifier description, subfunction identifier is served in diagnosis, diagnose and serve the description of subfunction identifier, diagnosis services request diagnostic data identifier, the description of diagnostic data identifier, the description of diagnostic data parameter, diagnostic data parameter, the total amount of byte diagnosing service data and subdata parameter; Subdata parameter comprises: the description of subdata parameter, byte location, Bit position and Bit length, physical values maximal value, physical values minimum value, conversion formula, data type, default value and unit;
According to ECU diagnosis service reception response parameter definition the 7th son file title of ODX standard, the 7th son file title comprises: diagnose service identifier, diagnose the description of service indications, subfunction identifier is served in diagnosis, diagnose the description of service subfunction identifier, diagnosis service reception response diagnostics data identifier, the description of diagnostic data identifier, the description of diagnostic data parameter, diagnostic data parameter, the total amount of byte diagnosing service reception response data and subdata parameter; Subdata parameter comprises: the description of subdata parameter, byte location, Bit position and Bit length, physical values maximal value, physical values minimum value, conversion formula, data type, default value and unit;
According to ECU diagnosis service negative response parameter definition the 8th son file title of ODX standard, 8th son file title comprises: negative response diagnosis service identifier, negative response diagnosis service identifier describes, and service identifier is diagnosed in request, request diagnosis service identifier describes, negative yardage value and description thereof are served in diagnosis;
According to ECU tracing trouble code parameters definition the 9th son file title of ODX standard, the 9th son file title comprises: the description of diagnostic trouble code hexadecimal values, diagnostic trouble code, the definition of diagnostic trouble code show code, trouble code attribute and diagnostic trouble code state;
Describe definition the tenth son file title according to the data uploading download of ODX standard, the tenth son file title comprises: start address, data length and refreshing block size;
According to vehicle configuration information definition the 11 son file title of ODX standard, the 11 son file title comprises: according to specific vehicle environmental, place, enable/to close optional function, setting characteristic curve.
4. the method for the open diagnostic data switching database of generation according to claim 3, is characterized in that, comprises the step that each diagnostic data in diagnostic data description document verifies according to pre-conditioned:
Whether verify in the first son file containing Business Name and company author;
Whether verify in the second son file containing manufacturer OEM information, vehicle information and vehicle bus topological structure;
Whether the network layer timing parameters verified in the 3rd son file meets preset range; Whether application layer timing parameters meets preset range; Whether baud rate meets preset range; Whether ECU unit physical addressing address meets preset range; Whether ECU unit diagnosis functional addressing address meets preset range;
Whether the version information form verified in the 4th son file meets ODX format standard; Whether version establishment date format meets ODX format standard; Version author and release status whether correct; Whether version modify content and version modify illustrate correct;
Verify in the 5th son file and diagnose service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition; Diagnosis service identifier describes and whether diagnosis service subfunction identifier descriptor format meets ODX format standard; Whether correctly forbid that positive response state, the description of diagnostic session pattern, addressing mode, security access levels, diagnosis service operational phase and negative response describe scope;
Verify in the 6th son file and diagnose service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition; Whether diagnosis services request diagnostic data identifier meets the diagnosing protocol range of definition; Diagnosis service identifier describes, diagnosis service subfunction identifier describes, diagnostic data identifier describes, diagnostic data parameter describes and whether subdata parameter descriptor format meets the requirement of ODX format standard; Whether the total amount of byte of diagnosis service data equals the subdata total bytes defined; Whether Bit position and the Bit length of subdata byte location and subdata is consistent; Whether the conversion formula form of subdata meets ODX format standard; Whether the maximal value calculated according to conversion formula is consistent with the physical values maximal value defined and physical values minimum value with minimum value; Whether data type is correct; Whether unit form meets the requirement of ODX format standard;
Verify in the 7th son file and diagnose service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition; Whether diagnosis service reception response diagnostics data identifier meets the diagnosing protocol range of definition; Diagnosis service identifier describes, diagnosis service subfunction identifier describes, diagnostic data identifier describes, diagnostic data parameter describes and whether subdata parameter descriptor format meets the requirement of ODX format standard; Whether the total amount of byte of diagnosis service reception response data equals the subdata total bytes defined; Whether Bit position and the Bit length of subdata byte location and subdata is consistent; Whether the conversion formula form of subdata meets ODX format standard; Whether the maximal value calculated according to conversion formula is consistent with the physical values maximal value defined and physical values minimum value with minimum value; Whether data type is correct; Whether unit form meets the requirement of ODX format standard;
Verify negative response diagnosis service identifier in the 8th son file, request diagnosis service identifier and diagnosis service negative yardage value and whether meet diagnosing protocol definition; Negative response diagnosis service identifier describes, request diagnosis service identifier describes and whether diagnosis service negative yardage value descriptor format meets the requirement of ODX format standard;
Verify diagnostic trouble code hexadecimal values form and scope in the 9th son file and whether meet diagnosing protocol definition; Whether diagnostic trouble code hexadecimal values is consistent with diagnostic trouble code show code; Diagnostic trouble code describes and whether trouble code attribute form meets ODX format standard; Whether the definition of diagnostic trouble code state meets diagnosing protocol definition;
Verify and refresh block size in the tenth son file and whether meet diagnosing protocol requirement; Whether start address and the data length of definition equal data in actual refreshing file;
Verify according to specific vehicle environmental in the 11 son file, place, enable/to close optional function, whether setting characteristic curve is correct.
5. the method for the open diagnostic data switching database of the generation according to Claims 1-4 any one, is characterized in that, the form of described diagnostic data description document is WORD form or EXCEL form.
6. generate a device for open diagnostic data switching database, it is characterized in that, comprise diagnostic data correction verification module, diagnostic data modified module, diagnostic data parsing module, file generating module and database generation module; Diagnostic data modified module is connected with diagnostic data correction verification module respectively with diagnostic data parsing module, and diagnostic data parsing module is connected with database generation module by file generating module;
Diagnostic data correction verification module, for verifying each diagnostic data in diagnostic data description document according to pre-conditioned;
Diagnostic data modified module, for when verifying wrong, according to the miscue information of verification, modifying to corresponding diagnostic data, obtaining new described diagnostic data;
Diagnostic data parsing module, for when verifying errorless, according to the form of described diagnostic data description document, resolves described each diagnostic data;
File generating module, for generating XML format file by each diagnostic data after parsing according to uml model;
Database generation module, for carrying out XML Schema verification to described XML format file, generates ODX database.
7. the device of the open diagnostic data switching database of generation according to claim 6, it is characterized in that, also comprise son file name definition module and description document generation module, son file name definition module is connected with diagnostic data correction verification module by description document generation module;
Son file name definition module, for each son file title comprised according to ODX standard definition diagnostic data description document;
Description document generation module, for according to the corresponding diagnostic data of each son file name acquiring, generates diagnostic data description document.
8. the device of the open diagnostic data switching database of generation according to claim 7, is characterized in that, described son file name definition module comprises:
First son file name definition unit, define the first son file title for the ECU diagnostic data company information according to ODX standard, the first son file title comprises Business Name and company author;
Second son file name definition unit, for formulating definition second son file title according to the ECU diagnostic data information of vehicles of ODX standard, the second son file title comprises manufacturer OEM information, vehicle information and vehicle bus topological structure;
3rd son file name definition unit, for supporting diagnosing protocol definition the 3rd son file title according to the ECU of ODX standard, the 3rd son file title comprises: network layer timing parameters, application layer timing parameters, baud rate, ECU unit physical addressing address and ECU unit diagnosis functional addressing address;
4th son file name definition unit, for ECU diagnostic data version management information definition the 4th son file title according to ODX standard, the 4th son file title comprises: version information, version establishment date, version author, release status, version modify content and version modify explanation;
5th son file name definition unit, for diagnosing service parameter definition the 5th son file title according to the ECU of ODX standard, the 5th son file title comprises: diagnosis service identifier, diagnosis service identifier describe, diagnosis service subfunction identifier, diagnosis service subfunction identifier describe, forbid that positive response state, the description of diagnostic session pattern, addressing mode, security access levels, diagnosis service operational phase and negative response describe; Forbid that positive response state comprises to support and do not support; Addressing mode comprises physical addressing, functional addressing; Diagnosis service operational phase comprises development phase, the stage of rolling off the production line and stage after sale;
6th son file name definition unit, for diagnosing service request parameter to define the 6th son file title according to the ECU of ODX standard, the 6th son file title comprises: diagnose service identifier, diagnose service identifier description, subfunction identifier is served in diagnosis, diagnose and serve the description of subfunction identifier, diagnosis services request diagnostic data identifier, the description of diagnostic data identifier, the description of diagnostic data parameter, diagnostic data parameter, the total amount of byte diagnosing service data and subdata parameter; Subdata parameter comprises: the description of subdata parameter, byte location, Bit position and Bit length, physical values maximal value, physical values minimum value, conversion formula, data type, default value and unit;
7th son file name definition unit, for ECU diagnosis service reception response parameter definition the 7th son file title according to ODX standard, the 7th son file title comprises: diagnose service identifier, diagnose the description of service indications, subfunction identifier is served in diagnosis, diagnose the description of service subfunction identifier, diagnosis service reception response diagnostics data identifier, the description of diagnostic data identifier, the description of diagnostic data parameter, diagnostic data parameter, the total amount of byte diagnosing service reception response data and subdata parameter; Subdata parameter comprises: the description of subdata parameter, byte location, Bit position and Bit length, physical values maximal value, physical values minimum value, conversion formula, data type, default value and unit;
8th son file name definition unit, for ECU diagnosis service negative response parameter definition the 8th son file title according to ODX standard, 8th son file title comprises: negative response diagnosis service identifier, negative response diagnosis service identifier describes, and service identifier is diagnosed in request, request diagnosis service identifier describes, negative yardage value and description thereof are served in diagnosis;
9th son file name definition unit, for ECU tracing trouble code parameters definition the 9th son file title according to ODX standard, the 9th son file title comprises: the description of diagnostic trouble code hexadecimal values, diagnostic trouble code, the definition of diagnostic trouble code show code, trouble code attribute and diagnostic trouble code state;
Tenth son file name definition unit, for describing definition the tenth son file title according to the data uploading download of ODX standard, the tenth son file title comprises: start address, data length and refreshing block size;
11 son file name definition unit, for according to specific vehicle environmental, place, enable/to close optional function, setting characteristic curve.
9. the device of the open diagnostic data switching database of generation according to claim 8, is characterized in that, described diagnostic data correction verification module comprises:
Whether the first son file verification unit, for verifying in the first son file containing Business Name and company author;
Whether the second son file verification unit, for verifying in the second son file containing manufacturer OEM information, vehicle information and vehicle bus topological structure;
Whether the 3rd son file verification unit, meet preset range for the network layer timing parameters verified in the 3rd son file; Whether application layer timing parameters meets preset range; Whether baud rate meets preset range; Whether ECU unit physical addressing address meets preset range; Whether ECU unit diagnosis functional addressing address meets preset range;
Whether the 4th son file verification unit, meet ODX format standard for the version information form verified in the 4th son file; Whether version establishment date format meets ODX format standard; Correctly whether, whether version modify content and version modify illustrate correct for version author and release status;
5th son file verification unit, diagnoses service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition for verifying in the 5th son file; Diagnosis service identifier describes and whether diagnosis service subfunction identifier descriptor format meets ODX format standard; Whether correctly forbid that positive response state, the description of diagnostic session pattern, addressing mode, security access levels, diagnosis service operational phase and negative response describe scope;
6th son file verification unit, diagnoses service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition for verifying in the 6th son file; Whether diagnosis services request diagnostic data identifier meets the diagnosing protocol range of definition; Diagnosis service identifier describes, diagnosis service subfunction identifier describes, diagnostic data identifier describes, diagnostic data parameter describes and whether subdata parameter descriptor format meets the requirement of ODX format standard; Whether the total amount of byte of diagnosis service data equals the subdata total bytes defined; Whether Bit position and the Bit length of subdata byte location and subdata is consistent; Whether the conversion formula form of subdata meets ODX format standard; Whether the maximal value calculated according to conversion formula is consistent with the physical values maximal value defined and physical values minimum value with minimum value; Whether data type is correct; Whether unit form meets the requirement of ODX format standard;
7th son file verification unit, diagnoses service identifier and diagnosis service subfunction identifier whether to meet diagnosing protocol definition for verifying in the 7th son file; Whether diagnosis service reception response diagnostics data identifier meets the diagnosing protocol range of definition; Diagnosis service identifier describes, diagnosis service subfunction identifier describes, diagnostic data identifier describes, diagnostic data parameter describes and whether subdata parameter descriptor format meets the requirement of ODX format standard; Whether the total amount of byte of diagnosis service reception response data equals the subdata total bytes defined; Whether Bit position and the Bit length of subdata byte location and subdata is consistent; Whether the conversion formula form of subdata meets ODX format standard; Whether the maximal value calculated according to conversion formula is consistent with the physical values maximal value defined and physical values minimum value with minimum value; Whether data type is correct; Whether unit form meets the requirement of ODX format standard;
Whether the 8th son file verification unit, meet diagnosing protocol definition for verifying negative response diagnosis service identifier in the 8th son file, request diagnosis service identifier and diagnosis service negative yardage value; Negative response diagnosis service identifier describes, request diagnosis service identifier describes and whether diagnosis service negative yardage value descriptor format meets the requirement of ODX format standard;
Whether the 9th son file verification unit, meet diagnosing protocol definition for verifying diagnostic trouble code hexadecimal values form and scope in the 9th son file; Whether diagnostic trouble code hexadecimal values is consistent with diagnostic trouble code show code; Diagnostic trouble code describes and whether trouble code attribute form meets ODX format standard; Whether the definition of diagnostic trouble code state meets diagnosing protocol definition;
Tenth son file verification unit, refreshes block size in the tenth son file whether meet diagnosing protocol requirement for verifying; Whether start address and the data length of definition equal data in actual refreshing file;
11 son file verification unit, for verifying according to specific vehicle environmental in the 11 son file, place, enable/to close optional function, whether setting characteristic curve is correct.
10. the device of the open diagnostic data switching database of the generation according to claim 6 to 9 any one, is characterized in that, the form of described diagnostic data description document is WORD form or EXCEL form.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510374642.2A CN104965507B (en) | 2015-06-29 | 2015-06-29 | Generate the method and device of open diagnostic data switching database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510374642.2A CN104965507B (en) | 2015-06-29 | 2015-06-29 | Generate the method and device of open diagnostic data switching database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104965507A true CN104965507A (en) | 2015-10-07 |
| CN104965507B CN104965507B (en) | 2018-04-20 |
Family
ID=54219545
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510374642.2A Active CN104965507B (en) | 2015-06-29 | 2015-06-29 | Generate the method and device of open diagnostic data switching database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104965507B (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109515205A (en) * | 2018-10-30 | 2019-03-26 | 北京友信宏科电子科技股份有限公司 | Data verification method and controller |
| CN109634257A (en) * | 2018-11-29 | 2019-04-16 | 重庆圣眸科技开发有限公司 | Method, conformance test method and the system of diagnostic test case are generated using ODX |
| CN109918361A (en) * | 2019-03-11 | 2019-06-21 | 威马智慧出行科技（上海）有限公司 | The creation method and device and data-storage system of vehicle diagnosis database |
| CN110198254A (en) * | 2019-05-31 | 2019-09-03 | 卡斯柯信号有限公司 | A kind of communication protocol inline diagnosis method and diagnostic system |
| CN110989564A (en) * | 2019-12-27 | 2020-04-10 | 深圳市元征科技股份有限公司 | Automobile data diagnosis method and device |
| CN111090476A (en) * | 2019-12-06 | 2020-05-01 | 深圳市元征科技股份有限公司 | Data configuration method, equipment diagnosis method and related products |
| CN111103861A (en) * | 2018-10-25 | 2020-05-05 | 上汽通用汽车有限公司 | Method and apparatus for developing an integrated system based on vehicle after-market diagnostic needs |
| CN111221317A (en) * | 2018-11-27 | 2020-06-02 | 广州汽车集团股份有限公司 | Automobile diagnosis data processing method and system |
| CN111857103A (en) * | 2020-07-31 | 2020-10-30 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, device, equipment and storage medium |
| CN111930103A (en) * | 2020-08-14 | 2020-11-13 | 东南（福建）汽车工业有限公司 | Automatic vehicle configuration system and method |
| CN112148312A (en) * | 2020-09-15 | 2020-12-29 | 中国第一汽车股份有限公司 | Firmware upgrading management method, device, equipment and medium for electronic controller |
| CN112631228A (en) * | 2020-12-28 | 2021-04-09 | 浙江中控技术股份有限公司 | Data processing method and system |
| CN113065033A (en) * | 2021-03-22 | 2021-07-02 | 江铃汽车股份有限公司 | ODX file-based diagnosis method |
| US11295560B2 (en) * | 2018-08-01 | 2022-04-05 | Ford Global Technologies, Llc | Cloud-managed validation and execution for diagnostic requests |
| CN114756258A (en) * | 2022-01-04 | 2022-07-15 | 广州汽车集团股份有限公司 | ECU software refreshing method and system based on ODX |
| CN117574869A (en) * | 2023-10-19 | 2024-02-20 | 镁佳(北京)科技有限公司 | Method, device, equipment and medium for automatically generating diagnostic application data packet |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007068563A1 (en) * | 2005-12-14 | 2007-06-21 | Robert Bosch Gmbh | Method for processing and creating diagnostic data in a software development process |
| CN102073319A (en) * | 2011-01-25 | 2011-05-25 | 武汉理工大学 | Multifunctional comprehensive type electric control automobile fault diagnosis system |
| CN102645929A (en) * | 2012-05-04 | 2012-08-22 | 武汉英泰斯特电子技术有限公司 | General description method for vehicle fault diagnostic protocols |
| CN102981501A (en) * | 2012-11-30 | 2013-03-20 | 重庆邮电大学 | Automobile ECU (Electronic Control Unit) fault diagnosis information matching method based on XML (Extensive Makeup Language) |
| CN104216978A (en) * | 2014-09-01 | 2014-12-17 | 观致汽车有限公司 | Automatic generation method and system for vehicle diagnosis database |
-
2015
- 2015-06-29 CN CN201510374642.2A patent/CN104965507B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007068563A1 (en) * | 2005-12-14 | 2007-06-21 | Robert Bosch Gmbh | Method for processing and creating diagnostic data in a software development process |
| CN102073319A (en) * | 2011-01-25 | 2011-05-25 | 武汉理工大学 | Multifunctional comprehensive type electric control automobile fault diagnosis system |
| CN102645929A (en) * | 2012-05-04 | 2012-08-22 | 武汉英泰斯特电子技术有限公司 | General description method for vehicle fault diagnostic protocols |
| CN102981501A (en) * | 2012-11-30 | 2013-03-20 | 重庆邮电大学 | Automobile ECU (Electronic Control Unit) fault diagnosis information matching method based on XML (Extensive Makeup Language) |
| CN104216978A (en) * | 2014-09-01 | 2014-12-17 | 观致汽车有限公司 | Automatic generation method and system for vehicle diagnosis database |
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11295560B2 (en) * | 2018-08-01 | 2022-04-05 | Ford Global Technologies, Llc | Cloud-managed validation and execution for diagnostic requests |
| CN111103861B (en) * | 2018-10-25 | 2023-04-07 | 上汽通用汽车有限公司 | Method and apparatus for developing an integrated system based on vehicle after-market diagnostic needs |
| CN111103861A (en) * | 2018-10-25 | 2020-05-05 | 上汽通用汽车有限公司 | Method and apparatus for developing an integrated system based on vehicle after-market diagnostic needs |
| CN109515205A (en) * | 2018-10-30 | 2019-03-26 | 北京友信宏科电子科技股份有限公司 | Data verification method and controller |
| CN111221317B (en) * | 2018-11-27 | 2021-04-30 | 广州汽车集团股份有限公司 | Automobile diagnosis data processing method and system |
| CN111221317A (en) * | 2018-11-27 | 2020-06-02 | 广州汽车集团股份有限公司 | Automobile diagnosis data processing method and system |
| CN109634257A (en) * | 2018-11-29 | 2019-04-16 | 重庆圣眸科技开发有限公司 | Method, conformance test method and the system of diagnostic test case are generated using ODX |
| CN109918361A (en) * | 2019-03-11 | 2019-06-21 | 威马智慧出行科技（上海）有限公司 | The creation method and device and data-storage system of vehicle diagnosis database |
| CN110198254A (en) * | 2019-05-31 | 2019-09-03 | 卡斯柯信号有限公司 | A kind of communication protocol inline diagnosis method and diagnostic system |
| CN111090476A (en) * | 2019-12-06 | 2020-05-01 | 深圳市元征科技股份有限公司 | Data configuration method, equipment diagnosis method and related products |
| CN110989564B (en) * | 2019-12-27 | 2021-05-04 | 深圳市元征科技股份有限公司 | Automobile data diagnosis method and device |
| CN110989564A (en) * | 2019-12-27 | 2020-04-10 | 深圳市元征科技股份有限公司 | Automobile data diagnosis method and device |
| CN111857103A (en) * | 2020-07-31 | 2020-10-30 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, device, equipment and storage medium |
| CN111857103B (en) * | 2020-07-31 | 2022-04-19 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, device, equipment and storage medium |
| CN111930103A (en) * | 2020-08-14 | 2020-11-13 | 东南（福建）汽车工业有限公司 | Automatic vehicle configuration system and method |
| CN111930103B (en) * | 2020-08-14 | 2022-09-20 | 东南（福建）汽车工业有限公司 | Automatic vehicle configuration system and method |
| CN112148312A (en) * | 2020-09-15 | 2020-12-29 | 中国第一汽车股份有限公司 | Firmware upgrading management method, device, equipment and medium for electronic controller |
| CN112631228A (en) * | 2020-12-28 | 2021-04-09 | 浙江中控技术股份有限公司 | Data processing method and system |
| CN113065033A (en) * | 2021-03-22 | 2021-07-02 | 江铃汽车股份有限公司 | ODX file-based diagnosis method |
| CN114756258A (en) * | 2022-01-04 | 2022-07-15 | 广州汽车集团股份有限公司 | ECU software refreshing method and system based on ODX |
| CN117574869A (en) * | 2023-10-19 | 2024-02-20 | 镁佳(北京)科技有限公司 | Method, device, equipment and medium for automatically generating diagnostic application data packet |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104965507B (en) | 2018-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104965507A (en) | Method used for generating open diagnostic data exchange database and device | |
| CN105388893A (en) | CAN communication data monitoring method and system based on OBD interface | |
| WO2015154527A1 (en) | Automatic interlocking logic detection method based on goose communication mechanism | |
| CN102750301B (en) | Blueprint generating method for integrated avionic system model aiming at architecture analysis and design language (AADL) description | |
| CN103631255B (en) | For the Fault Insertion Equipment of avionics system Gernral Check-up | |
| CN102222043B (en) | Testing method and testing device | |
| CN103676939B (en) | A kind of Auto-Test System based on OSEK straight-forward network administrative mechanisms | |
| CN109840207A (en) | One kind being based on AUTOSAR network management automatization test system and test method | |
| CN107370637B (en) | Vehicle-mounted ECU communication function automatic test system and method | |
| CN113612654B (en) | Vehicle-mounted gateway function test method based on database | |
| CN111585344B (en) | Substation intelligent checking method and device based on total station IED simulation | |
| CN105224511A (en) | A kind of method of calibration of intelligent substation SCD file | |
| CN103439961B (en) | Automobile electronic control unit diagnostic function test method and system | |
| CN101369933A (en) | Automatic test method and system | |
| CN104319891B (en) | Maintenance O＆M device and method for transformer station process layer | |
| CN106100935A (en) | Charging equipment of electric automobile communication protocol consistency test device and method | |
| WO2015149594A1 (en) | Iec61850-based communication simulation method for partial discharge on-line monitoring device | |
| CN103077093B (en) | Substation configuration description (SCD) calibration method based on model objectification semantics | |
| CN109509239B (en) | SCD configuration-free generation method for secondary circuit configuration file of in-place protection device | |
| CN101145130A (en) | Simple network management protocol software test device and test method | |
| WO2019047070A1 (en) | Database maintenance method and system | |
| CN104935936A (en) | Entropy decoder authentication method based on UVM and device | |
| CN110209584A (en) | A kind of automatic generation of test data and relevant apparatus | |
| WO2023103248A1 (en) | Automatic device commissioning method, apparatus, device, system, and storage medium | |
| WO2014040488A1 (en) | Method and device for guaranteeing consistency of planning data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |