Complete vehicle diagnosis database conversion method, system and device and medium

Abstract

The invention provides a conversion method, system and device of a vehicle diagnosis database and a medium, and belongs to the technical field of vehicles. The method comprises the following steps: initializing a data area of a data file according to a set parameter format, and writing an input diagnosis parameter into the corresponding data area; the data area is defined, the diagnosis parameters correspond to parameter interfaces in a diagnosis database, and the data file is converted into a diagnosis data file of the diagnosis database; based on a test conversion tool arranged in the diagnosis database, generating a test case and a test specification according to the diagnosis data file, and inputting a test project file; and according to the test project file, the test case and the test specification, performing a diagnostic test to obtain a test result and test data. The CDD manual development period and complexity are reduced, the accuracy is improved, and the diagnosis database development efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method, system, device, and medium for converting a whole vehicle diagnostic database. Background Technology

[0002] The diagnostic database CDD (CANdelaStudio Description) used in vehicle development is a standardized diagnostic database format developed by Vector Corporation to describe the diagnostic functions of vehicle ECUs (electronic control units).

[0003] With the rapid development of automotive electronics, vehicle functions are becoming increasingly complex, and the number of on-board controllers is also increasing. As a result, the diagnostic database files for controllers are becoming more complex to edit and have a wider range of applications. They are not only used in the development and testing phases, but also play an increasingly important role in the production and after-sales phases.

[0004] In the traditional approach, the diagnostic services and parameters of the CDD database files for different controllers need to be manually edited by developers. The development tool CANDdela Studio is used to edit the parameters of each controller, including thousands of parameters such as services, service parameters, session attributes and security levels. There are dozens of controllers at the vehicle level, and the number of parameters in the CDD database can reach tens of thousands or hundreds of thousands. Because there are too many parameters, it is difficult to avoid various filling errors and other problems during manual development, which will affect subsequent development. Summary of the Invention

[0005] The main objective of this application is to propose a method, system, device, and medium for converting a vehicle diagnostic database, thereby reducing the manual development cycle and complexity of CDD, improving accuracy, and increasing the efficiency of diagnostic database development.

[0006] To achieve the above objectives, one aspect of this application proposes a method for converting a vehicle diagnostic database, the method comprising: According to the set parameter format, initialize the data area of ​​the data file, and write the input diagnostic parameters into the corresponding data area; Define the data region, map the diagnostic parameters to the parameter interfaces in the diagnostic database, and convert the data file into a diagnostic data file of the diagnostic database; Based on the test conversion tool set in the diagnostic database, test cases and test specifications are generated according to the diagnostic data file and input into the test project file; Diagnostic testing is performed based on the test project files, test cases, and test specifications to obtain test results and test data.

[0007] In some embodiments, the method further includes: The diagnostic data file is converted using the provided file conversion tool to obtain a compiled data file. Compile the diagnostic parameters based on the data.

[0008] In some embodiments, mapping the diagnostic parameters to parameter interfaces in the diagnostic database includes: Traverse all the data regions and write the diagnostic parameters into the temporary storage data area; In the temporary storage data area, the diagnostic data file is generated by matching the parameter interface according to the parameter type of the diagnostic parameters through macro definition.

[0009] In some embodiments, generating test cases and test specifications based on the diagnostic data file includes: By combining the diagnostic database with the set test conversion tool, the test cases and the test specifications are generated based on the session patterns, security levels, and service parameters in the diagnostic database.

[0010] To achieve the above objectives, another aspect of this application proposes a conversion system for a vehicle diagnostic database, the system comprising: The data file generation module is used to initialize the data area of ​​the data file according to the set parameter format, and write the input diagnostic parameters into the corresponding data area; The first conversion module is used to define the data area, map the diagnostic parameters to the parameter interfaces in the diagnostic database, and convert the data file into a diagnostic data file of the diagnostic database. The test generation module is used to generate test cases and test specifications based on the test conversion tool set in the diagnostic database and the diagnostic data file, and input them into the test project file; The testing module is used to perform diagnostic tests based on the test project file, the test cases, and the test specifications, and to obtain test results and test data.

[0011] In some embodiments, the system further includes: The second conversion module is used to convert the diagnostic data file using the provided file conversion tool to obtain a data compilation file; The parameter compilation module compiles the diagnostic parameters based on the data compilation file.

[0012] In some embodiments, the first conversion module includes: The reading unit is used to traverse all the data areas and write the diagnostic parameters into the temporary storage data area; The matching unit, in the temporary storage data area, matches the parameter interface according to the parameter type of the diagnostic parameters using macro definition to generate the diagnostic data file.

[0013] In some embodiments, the test generation module includes: The conversion tool invocation unit is used to combine the diagnostic database with the set test conversion tool, and generate the test cases and the test specifications based on the session mode, the set security level and the set service parameters in the diagnostic database.

[0014] To achieve the above objectives, another aspect of this application provides a vehicle control device, including a memory, a processor, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the above-described method for converting the vehicle diagnostic database.

[0015] To achieve the above objectives, another aspect of the embodiments of this application proposes a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for converting a vehicle diagnostic database.

[0016] The embodiments of this application include at least the following beneficial effects: This application provides a method, apparatus, and medium for converting a vehicle diagnostic database. This solution initializes the data area of ​​the data file according to the set parameter format to standardize the data file format; it maps diagnostic parameters to parameter interfaces in the diagnostic database, which can be directly converted into diagnostic data files, shortening the time from standardization to database conversion, improving the development cycle, ensuring the development and conversion of the database, and adding a description of the process of generating diagnostic test cases from CDD diagnostic data files in the testing phase and using test project files to complete the test, obtaining test results and test data, reducing the manual development cycle and complexity of CDD, improving accuracy, and improving the development efficiency of the diagnostic database. Attached Figure Description

[0017] Figure 1 This is a flowchart of the method for converting the vehicle diagnostic database provided in the embodiments of this application; Figure 2 This is a schematic diagram of the framework of the vehicle diagnostic database conversion system provided in the embodiments of this application; Figure 3 This is a schematic diagram of the hardware structure framework of the vehicle control device provided in the embodiments of this application. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit it. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.

[0019] It is understood that the terms "first," "second," etc., used in this application may be used to describe various concepts herein, but unless otherwise specified, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of embodiments of this application, Ethernet signaling information may also be referred to as interface signaling information, and similarly, interface signaling information may also be referred to as Ethernet signaling information. Depending on the context, the words "if" or "when" as used herein may be interpreted as "when," "in response to a determination," or "in the event of a determination."

[0020] As used in this application, the terms "at least one", "multiple", "each", "any", etc., "at least one" includes one, two or more, "multiple" includes two or more, "each" refers to each of the corresponding multiples, and "any" refers to any one of the multiples.

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0022] Before providing a detailed description of the embodiments of this application, some of the nouns and terms involved in the embodiments of this application will be explained first. The nouns and terms involved in the embodiments of this application are subject to the following interpretations.

[0023] The diagnostic database CDD (CANdela Studio Description) used in vehicle development is a standardized diagnostic database format developed by Vector. It is used to describe the diagnostic functions of vehicle ECUs (electronic control units). The diagnostic service definitions supported by the CDD database conform to diagnostic standards such as UDS (ISO14229) and OBD (ISO15031) protocol service standards. It supports ECU parameter definitions (DID, DTC, etc.), communication and parameter configuration (channel selection, timing parameters, etc.), and is compatible with multiple toolchains (CANOE, Indigo, CANdela, etc.).

[0024] ODX (Open Diagnostic Data Exchange) is an internationally standardized diagnostic database format used for the diagnosis and programming of vehicle electronic systems. It is mainly used in the production and after-sales stages. ODX files are essentially structured XML and can be edited or parsed by tools such as CANoe and Vector toolchains.

[0025] In some embodiments of one aspect of the present invention Figure 1 This is an optional flowchart of the method for converting the vehicle diagnostic database provided in the embodiments of this application. Figure 1 The method may include, but is not limited to, steps S100 to S400.

[0026] Step S100: Initialize the data area of ​​the data file according to the set parameter format, and write the input diagnostic parameters into the corresponding data area.

[0027] Step S200: Define the data area, map the diagnostic parameters to the parameter interfaces in the diagnostic database, and convert the data file into a diagnostic data file in the diagnostic database.

[0028] Step S300: Based on the test conversion tool set in the diagnostic database, generate test cases and test specifications according to the diagnostic data file, and input them into the test project file.

[0029] Step S400: Perform diagnostic testing based on the test project documents, test cases, and test specifications to obtain test results and test data.

[0030] Steps S100 to S400 as shown in the embodiments of this application initialize the data area of ​​the data file according to the set parameter format to standardize the data file format; the diagnostic parameters are mapped to the parameter interfaces in the diagnostic database, which can be directly converted into a diagnostic data file, shortening the time from standardization to database conversion, improving the development cycle, ensuring the development of the database is finalized, and adding a description of the process of generating diagnostic test cases from CDD diagnostic data files in the testing phase and using test project files to complete the test, obtaining test results and test data, reducing the manual development cycle and complexity of CDD, improving accuracy, and improving the development efficiency of the diagnostic database.

[0031] In some embodiments of S100, the data area in the data file is initialized according to the set parameter format in order to complete the formulation of diagnostic specifications.

[0032] Input the diagnostic parameters, and write them into the corresponding data area based on the initialized data area.

[0033] For example, by modifying the standard format Excel file according to the set parameter format, each cell in the Excel file is initialized, thus completing the formulation of diagnostic specifications using Excel during the design and development phase. Based on the initialized cells, the input diagnostic parameters are written into the corresponding cells.

[0034] In some embodiments of S200, a data region is defined, and diagnostic parameters are mapped to CDD parameter interfaces in the diagnostic database through macro definitions. That is, the diagnostic parameters in the data file are mapped to service variables in the diagnostic database, thereby converting the data file into a diagnostic data file for code and test case development.

[0035] For example, by using macro definitions and other methods to achieve the correspondence between diagnostic parameters and CDD parameter interfaces in the diagnostic database, Excel files can be directly converted into diagnostic database CDD files, which shortens the time for conversion from specifications to database, improves the development cycle, and ensures the development of the database.

[0036] In some embodiments of S300, the test conversion tool in the diagnostic database generates diagnostic test cases and test specifications from the diagnostic parameters in the diagnostic data file, and then imports the test project file.

[0037] The test conversion tool used is CANDIVA. The diagnostic data file is a CDD file.

[0038] For example, by combining a diagnostic database with CANDIVA, diagnostic test cases and test specifications can be generated using CANDIVA tools during the testing phase via CDD files.

[0039] In some embodiments of S400, diagnostic tests are performed using the test project files, test cases, and test specifications of S300 to obtain test results and test data.

[0040] For example, based on diagnostic test cases and test specifications, import test project files into CANOE to complete diagnostic tests and view test results and test data.

[0041] In some embodiments of this invention, the conversion method further includes: The S500 uses the provided file conversion tool to convert the diagnostic data file into a compiled data file. S510 compiles diagnostic parameters based on the data compilation file.

[0042] In this embodiment, during the production and after-sales stages, the provided file conversion tool is used to convert the diagnostic data file into a data compilation file, which can be edited or parsed to modify the diagnostic parameters.

[0043] For example, during the production and after-sales phases, the file conversion tool in CANDELA is used to convert CDD files into ODX files for the development of production and after-sales diagnostic equipment. These files can be edited or parsed using compilation tools such as CANoe or the Vector toolchain.

[0044] In some embodiments of the present invention, S200, mapping diagnostic parameters to parameter interfaces in the diagnostic database includes the following steps: S210, Traverse all data areas and write diagnostic parameters to the temporary storage data area; S220 generates diagnostic data files by matching parameter interfaces according to the parameter types of diagnostic parameters in the temporary storage data area through macro definition.

[0045] In this embodiment, all data areas in the data file are traversed, and diagnostic parameters are written to a temporary storage data area.

[0046] The temporary data storage area can be a VBA array or a dictionary.

[0047] In the temporary storage area, using macro definitions, the parameter types of the diagnostic parameters, such as parameter names or IDs, are matched with the parameter interfaces in the diagnostic data file. The diagnostic data file is then generated according to the defined file structure.

[0048] In one embodiment, when the diagnostic parameter is a newly added parameter, the corresponding node is generated according to the CDD structure specification.

[0049] For example, diagnostic parameters are entered in Excel using a standard structured format (e.g., one parameter per row, one attribute per column), such as: ID, parameter, session mode, security level, data type, value range, and negative response code (NRC). Dependencies. Write a VBA macro to implement matching and exporting, reading cell data from an Excel file: iterate through the Excel file, reading parameters into a VBA array or dictionary. Match existing diagnostic services, DIDs, RIDs, etc., in the CDD based on parameter names or IDs. Dynamically generate an XML file according to the CDD's XML structure, thus obtaining the CDD file.

[0050] In some embodiments of this invention, S300, generating test cases and test specifications includes the following steps: S310 combines the diagnostic database with the set test transformation tools to generate test cases and test specifications based on the session patterns, security levels, and service parameters in the diagnostic database.

[0051] In this embodiment, the diagnostic database is combined with the set test conversion tool. By setting the session mode, security level, and service parameters in the diagnostic database, diagnostic test cases and test specifications are generated for use in diagnostic testing.

[0052] For example, a diagnostic database is combined with CANDIVA to generate diagnostic test cases and test specifications based on the session patterns, security levels, and service parameter settings in the database.

[0053] Reference Figure 2 Another embodiment of this application also provides a conversion system for a vehicle diagnostic database, the system comprising: The data file generation module is used to initialize the data area of ​​the data file according to the set parameter format, and write the input diagnostic parameters into the corresponding data area; The first conversion module is used to define the data area, map the diagnostic parameters to the parameter interfaces in the diagnostic database, and convert the data file into a diagnostic data file in the diagnostic database. The test generation module is used to generate test cases and test specifications based on the test conversion tools set in the diagnostic database and the diagnostic data files, and input them into the test project files; The testing module is used to perform diagnostic tests based on the test project files, test cases, and test specifications, and to obtain test results and test data. The second conversion module is used to convert diagnostic data files using the provided file conversion tool to obtain compiled data files; The parameter compilation module is used to compile diagnostic parameters based on data files.

[0054] In this embodiment, the data file generation module can initialize the data area in the data file according to the set parameter format to complete the formulation of diagnostic specifications. Diagnostic parameters are input, and based on the initialized data area, the diagnostic parameters are written into the corresponding data area.

[0055] The first conversion module can define the data area and map the diagnostic parameters to the CDD parameter interface in the diagnostic database through macro definition. That is, the diagnostic parameters in the data file correspond to the service variables in the diagnostic database, thereby converting the data file into a diagnostic data file for code and test case development.

[0056] The test generation module can use the test conversion tool in the diagnostic database to generate diagnostic test cases and test specifications from the diagnostic parameters in the diagnostic data files, and then import the test project files.

[0057] The test conversion tool used is CANDIVA. The diagnostic data file is a CDD file.

[0058] The testing module can perform diagnostic tests and obtain test results and test data by using test project files, test cases, and test specifications.

[0059] The second conversion module can use the provided file conversion tools to convert diagnostic data files into compiled data files during the production and after-sales stages.

[0060] The parameter compilation module can edit or parse the data compilation file, enabling modification of diagnostic parameters.

[0061] For example, by modifying the standard format Excel file according to the set parameter format, each cell in the Excel file is initialized, thus completing the formulation of diagnostic specifications using Excel during the design and development phase. Based on the initialized cells, the input diagnostic parameters are written into the corresponding cells.

[0062] By using macro definitions and other methods, the correspondence between diagnostic parameters and CDD parameters in the diagnostic database is achieved. Excel files can be directly converted into diagnostic database CDD files, which shortens the time for conversion from specifications to database, improves the development cycle, and ensures the development of the database.

[0063] By combining the diagnostic database with CANDIVA, and using CDD files, the CANDIVA tool is used during the testing phase to generate diagnostic test cases and test specifications. Based on the diagnostic test cases and test specifications, the test project files are imported into CANOE to complete the diagnostic tests, and the test results and test data are then viewed.

[0064] Another embodiment of this application also provides a conversion system for a vehicle diagnostic database, wherein the first conversion module includes: The read unit is used to traverse all data areas and write diagnostic parameters into the temporary storage data area; The matching unit, in the temporary storage data area, uses macro definitions to match parameter interfaces based on the parameter types of diagnostic parameters in order to generate diagnostic data files.

[0065] In this embodiment, the reading unit can traverse all data areas in the data file and write diagnostic parameters into the temporary storage data area.

[0066] The temporary data storage area can be a VBA array or a dictionary.

[0067] The matching unit can match parameter interfaces in the diagnostic data file using macro definitions in the temporary storage data area, based on the parameter type of the diagnostic parameters, such as parameter name or ID. It then generates the diagnostic data file according to the set file structure.

[0068] In one embodiment, when the diagnostic parameter is a newly added parameter, the corresponding node is generated according to the CDD structure specification.

[0069] For example, diagnostic parameters are entered in Excel using a standard structured format (e.g., one parameter per row, one attribute per column), such as: ID, parameter, session mode, security level, data type, value range, and negative response code (NRC). Dependencies. Write a VBA macro to implement matching and exporting, reading cell data from an Excel file: iterate through the Excel file, reading parameters into a VBA array or dictionary. Match existing diagnostic services, DIDs, RIDs, etc., in the CDD based on parameter names or IDs. Dynamically generate an XML file according to the CDD's XML structure, thus obtaining the CDD file.

[0070] Another embodiment of this application also provides a conversion system for a vehicle diagnostic database, wherein the test generation module includes: The conversion tool invocation unit is used to combine the diagnostic database with the set test conversion tool, and generate test cases and test specifications based on the session mode, set security level and set service parameters in the diagnostic database.

[0071] In this embodiment, the conversion tool calling unit can combine the diagnostic database with the set test conversion tool, and generate diagnostic test cases and test specifications through the settings of session mode, security level and service parameters in the diagnostic database for use in diagnostic testing.

[0072] Another embodiment of this application provides a vehicle control device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described method for converting the vehicle diagnostic database. This vehicle control device can be any smart terminal, including a tablet computer or an in-vehicle computer.

[0073] It is understood that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented by this device embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0074] Please see Figure 3 , Figure 3 The hardware structure of a vehicle control device according to another embodiment is illustrated. The vehicle control device includes: The processor can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to achieve the technical solutions provided in the embodiments of this application. The memory can be implemented in the form of read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory and called by the processor to execute the vehicle diagnostic database conversion method of the embodiments of this application. Input / output interfaces are used to implement information input and output; The communication interface is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). A bus is used to transfer information between various components of a device, such as processors, memory, input / output interfaces, and communication interfaces. The processor, memory, input / output interfaces, and communication interfaces communicate with each other within the device via a bus.

[0075] This invention also provides a vehicle, including the method for converting the vehicle diagnostic database described in the above embodiments.

[0076] The vehicle can be a private car, such as a sedan, SUV, MPV, or pickup truck. It can also be a commercial vehicle, such as a van, bus, small truck, or large semi-trailer. The vehicle must have an electric motor capable of outputting power or acting as a generator to store mechanical energy. When the vehicle is a new energy vehicle, it can be a hybrid or a pure electric vehicle.

[0077] Since the vehicle applies all the technical solutions of the above-described vehicle control device, it has at least all the beneficial effects brought about by the technical solutions of the above embodiments, which will not be repeated here.

[0078] Another embodiment of the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for converting a vehicle diagnostic database.

[0079] It is understood that the content of the above method embodiments is applicable to this storage medium embodiment. The specific functions implemented in this storage medium embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0080] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0081] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0082] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0083] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0084] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0085] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0086] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0087] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0088] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0089] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A method of transforming a vehicle diagnostic database, characterized by, The method comprises: initializing data areas of a data file according to a set parameter format, and writing input diagnostic parameters into corresponding data areas; defining the data areas, corresponding the diagnostic parameters with parameter interfaces in a diagnostic database, and converting the data file into a diagnostic data file of the diagnostic database; generating test cases and test specifications according to the diagnostic data file based on a set test conversion tool in the diagnostic database, and inputting a test engineering file; performing diagnostic testing according to the test engineering file, the test cases and the test specifications, and obtaining test results and test data.

2. The method of claim 1, wherein the vehicle diagnosis database is converted into a format of a vehicle diagnosis database of a vehicle manufacturer. The method further comprises: converting the diagnostic data file by using a set file conversion tool to obtain a data compilation file; compiling the diagnostic parameters according to the data compilation file.

3. The method of claim 1, wherein the vehicle diagnosis database is converted into a format of a vehicle diagnosis database of a vehicle manufacturer. The corresponding of the diagnostic parameters with the parameter interfaces in the diagnostic database comprises: traversing all the data areas, and writing the diagnostic parameters into a temporary storage data area; in the temporary storage data area, matching the parameter interfaces according to parameter types of the diagnostic parameters by a macro definition method to generate the diagnostic data file.

4. The method of claim 1, wherein the vehicle diagnosis database is converted into a format of a vehicle diagnosis database of a vehicle manufacturer. The generation of the test cases and the test specifications according to the diagnostic data file comprises: combining the diagnostic database with the set test conversion tool, generating the test cases and the test specifications according to session modes, set security levels and set service parameters in the diagnostic database.

5. A vehicle control device characterized by comprising: The computer program is executed by the processor to implement the conversion method of the whole vehicle diagnostic database according to any one of claims 1 to 4.

6. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 5. The computer program is executed by the processor to implement the conversion method of the whole vehicle diagnostic database according to any one of claims 1 to 4.

7. A system for transforming a vehicle diagnostic database, characterized by The system comprises: a data file generation module for initializing data areas of a data file according to a set parameter format, and writing input diagnostic parameters into corresponding data areas; a first conversion module for defining the data areas, corresponding the diagnostic parameters with parameter interfaces in a diagnostic database, and converting the data file into a diagnostic data file of the diagnostic database; a test generation module for generating test cases and test specifications according to the diagnostic data file based on a set test conversion tool in the diagnostic database, and inputting a test engineering file; a test module for performing diagnostic testing according to the test engineering file, the test cases and the test specifications, and obtaining test results and test data.

8. The conversion system of an on-vehicle diagnosis database according to claim 7, characterized by, The system further comprises: a second conversion module for converting the diagnostic data file by using a set file conversion tool to obtain a data compilation file; a parameter compilation module for compiling the diagnostic parameters according to the data compilation file.

9. The conversion system of an on-vehicle diagnosis database according to claim 7, characterized by, The first conversion module comprises: a reading unit for traversing all the data areas, and writing the diagnostic parameters into a temporary storage data area; The matching unit matches the parameter interface according to the parameter type of the diagnostic parameter in the temporary storage data area by macro definition to generate the diagnostic data file.

10. The conversion system of an on-vehicle diagnosis database according to claim 7, characterized by, The test generation module comprises: The conversion tool calling unit combines the diagnostic database with a set test conversion tool to generate the test case and the test specification according to the session mode, the set security level and the set service parameter in the diagnostic database.

Images