Calibration description file generation method and device, storage medium and equipment

Abstract

The invention provides a calibration description file generation method and device, a storage medium and equipment, and the method comprises the steps: obtaining a header file which records ECU memory allocation and calibration parameters in a target platform, obtaining a data dictionary and compilation products of software engineering at the same time, and then building a new blank description file; and copying the obtained information in the header file to the beginning part of the blank description file, obtaining variable description information according to the data dictionary and the compiled product, and updating the variable description information to the description file containing the header file to obtain a calibration description file. Therefore, automatic generation of the calibration description file is realized, and platform compatibility is improved, so that convenience is provided for development of calibration work, and project development efficiency is effectively improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and more specifically, to a method, apparatus, storage medium, and device for generating calibration description files. Background Technology

[0002] The calibration description file used by the vehicle controller, such as the A2L file, is a description file for observing and calibrating ECU (Electronic Control Unit) information. In related technologies, calibration description files generally rely on third-party tools to generate. Existing third-party tools have poor platform compatibility. For different hardware platforms, engineers need to select or configure matching third-party tools, which brings great inconvenience to engineers in carrying out calibration work. Summary of the Invention

[0003] The purpose of this application is to provide a calibration description file generation method, apparatus, storage medium, and device, aiming to solve the problem that the calibration description file generation methods in related technologies have poor platform compatibility, which brings great inconvenience to engineers in carrying out calibration work.

[0004] In a first aspect, this application provides a method for generating a calibration description file, comprising: acquiring a data dictionary, a header file of a target platform, and compilation products of various software engineering projects; the header file being a file recording ECU memory allocation and calibration parameters; copying the information in the header file to the beginning of a blank description file to obtain an initial description file; acquiring variable description information based on the data dictionary and the compilation products; and updating the variable description information to the initial description file to obtain a calibration description file name.

[0005] In the above implementation process, the header file recording ECU memory allocation and calibration parameters from the target platform is obtained, along with the data dictionary and the compilation artifacts of each software engineering project. Then, a blank description file is created, and the information from the obtained header file is copied to the beginning of the blank description file. Next, variable description information is obtained based on the data dictionary and compilation artifacts, and this variable description information is updated in the description file that already includes the header file, resulting in the calibration description file. This achieves automated generation of the calibration description file, improves platform compatibility, facilitates calibration work, and effectively improves project development efficiency.

[0006] Furthermore, in some examples, the header file is obtained from a pre-configured or user-specified software project root directory via an automated script.

[0007] In the above implementation process, the generator integrates an automated script. This script is configured to receive an input parameter pointing to the root directory path of the target software project. When retrieving header files for the target platform, the script automatically searches for and collects the header files in the root directory and all its subdirectories corresponding to that root directory path. This reduces manual intervention and improves the efficiency of generating calibration description files.

[0008] Furthermore, in some examples, before obtaining variable description information based on the data dictionary and the compilation output, the process includes: classifying the data quantities defined in the data dictionary into observation quantities and calibration quantities; the observation quantities include model input quantities, model output quantities, and model internal observation quantities defined in the data dictionary; the calibration quantities include single calibration parameters, one-dimensional arrays, and three-dimensional tables.

[0009] In the above implementation process, the generator categorizes the data quantities defined in the data dictionary into two categories: one category is observations, which corresponds to the input quantities, output quantities, and internal model observations in the data dictionary; the other category is calibration quantities, which includes individual calibration parameters, one-dimensional arrays, and three-dimensional tables. This ensures that the final generated calibration description file can fully preserve the original structure of the one-dimensional arrays and three-dimensional tables, thereby improving the efficiency and accuracy of the calibration work.

[0010] Furthermore, in some examples, the variable description information includes the attribute information, data conversion rules, and corresponding address information of the observed quantity, as well as the attribute information, data conversion rules, and corresponding address information of the calibration quantity; obtaining the variable description information according to the data dictionary and the compilation product includes: obtaining the attribute information of each observed quantity and the attribute information of each calibration quantity according to the data dictionary, converting the attribute information into a description file format, and generating the data conversion rules for the observed quantity and the data conversion rules for the calibration quantity; obtaining the address information corresponding to the observed quantity and the address information corresponding to the calibration quantity according to the compilation product.

[0011] In the above implementation process, a specific method is provided to obtain variable description information based on the data dictionary and compilation products.

[0012] Furthermore, in some examples, the compilation output includes a memory-mapped file; the attribute information includes a name; obtaining the address information corresponding to the observation and the address information corresponding to the calibration quantity based on the compilation output includes: parsing the memory-mapped file, searching for the corresponding address information in the memory-mapped file according to the name of the observation and the name of the calibration quantity, respectively, to obtain the address information corresponding to the observation and the address information corresponding to the calibration quantity.

[0013] In the above implementation process, the generator parses the obtained Map file, searches for the corresponding address information in the Map file based on the name information of the observations and calibrations, and updates the address of each observation and calibration in the description file accordingly. This avoids errors that may arise from manually searching and inputting addresses, and can adapt to different hardware platforms and compilation environments.

[0014] Secondly, this application provides a calibration description file generation apparatus, comprising: an acquisition module for acquiring a data dictionary, a header file of a target platform, and compilation products of various software engineering projects; the header file being a file recording ECU memory allocation and calibration parameters; a copy module for copying information from the header file to the beginning of a blank description file to obtain an initial description file, and acquiring variable description information based on the data dictionary and the compilation products; and an update module for updating the variable description information to the initial description file to obtain a calibration description file.

[0015] Furthermore, in some examples, the copy module includes a classification submodule; the classification submodule is used to classify the data quantities defined in the data dictionary into observations and calibration quantities; the observations include model input quantities, model output quantities, and model internal observations defined in the data dictionary; the calibration quantities include a single calibration parameter, a one-dimensional array, and a three-dimensional table.

[0016] Furthermore, in some examples, the variable description information includes the attribute information, data conversion rules, and corresponding address information of the observed quantity, as well as the attribute information, data conversion rules, and corresponding address information of the calibration quantity; the copy module further includes a conversion submodule and an acquisition submodule; the copy submodule is used to: acquire the attribute information of each observed quantity and the attribute information of each calibration quantity according to the data dictionary, convert the attribute information into a description file format, and generate the data conversion rules of the observed quantity and the data conversion rules of the calibration quantity; the acquisition submodule is used to: acquire the address information corresponding to the observed quantity and the address information corresponding to the calibration quantity according to the compilation product.

[0017] Thirdly, this application provides an electronic device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the method described in any of the first aspects.

[0018] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method described in any of the first aspects.

[0019] Fifthly, this application provides a computer program product that, when run on a computer, causes the computer to perform the method described in any of the first aspects.

[0020] Other features and advantages disclosed in this application will be set forth in the following description, or some features and advantages may be inferred from the description or determined without doubt, or may be learned by practicing the above-described technology disclosed in this application.

[0021] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0022] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 A flowchart illustrating a calibration description file generation method provided in this application embodiment; Figure 2 A schematic diagram illustrating an ASAM standard format observation description provided in an embodiment of this application; Figure 3 A schematic diagram illustrating a standard quantification description in ASAM format provided for an embodiment of this application; Figure 4 A block diagram of a calibration description file generation apparatus provided in an embodiment of this application; Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0024] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0025] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0026] In the software development and calibration of automotive ECUs, generating a calibration description file is a crucial step. This file serves as a bridge connecting the ECU's internal memory data with the host computer calibration tools, and its completeness and accuracy directly impact the efficiency and quality of the calibration work. Currently, the industry generally relies on dedicated third-party tools to generate calibration description files. However, existing third-party tools have poor platform compatibility. For different hardware platforms, engineers need to select or configure compatible third-party tools, which greatly inconveniences engineers in carrying out calibration work.

[0027] To address the aforementioned issues, this application provides a calibration description file generation scheme. It obtains the header file recording ECU memory allocation and calibration parameters from the target platform, along with the data dictionary and compilation artifacts of each software engineering project. A new blank description file is created, and the information from the header file is copied to the beginning of the blank description file. Then, variable description information is obtained based on the data dictionary and compilation artifacts, and this variable description information is updated in the description file that already includes the header file, thus obtaining the calibration description file. This achieves automated generation of the calibration description file, improves platform compatibility, and effectively enhances project development efficiency.

[0028] The embodiments of this application will be described below: like Figure 1 As shown, Figure 1 This is a flowchart illustrating a calibration description file generation method provided in an embodiment of this application. The method can be implemented as an automatic calibration description file generator. The method includes: Step 101: Obtain the data dictionary, the header file of the target platform, and the compilation output of each software project; the header file is a file that records ECU memory allocation and calibration parameters; The data dictionary mentioned in this step is a core metadata management tool in the field of ECU calibration, and it is an essential document for developing application-layer software based on the model. In its implementation, the data dictionary defines all input quantities, output quantities, internal model observations, and calibration quantities required for ECU application-layer software model development. The attributes of these defined quantities include name, meaning description, data type, data dimension, data attribute, associated functional module, calibration description, etc. Data dimensions include arrays, three-dimensional tables, etc. Typically, in the forward software development process, the model framework is generated based on these defined quantities; therefore, the definitions of the data dictionary and the various quantities in the model are completely consistent.

[0029] The target platform mentioned in this step can refer to the hardware platform corresponding to the project to be developed. In related technologies, different hardware platforms use different third-party tools, and the ECU memory allocation and calibration parameters also differ. In this embodiment, the generator is compatible with multiple platforms. During implementation, the generator automatically identifies the platform and automatically obtains the file recording the ECU memory allocation and calibration parameters, i.e., the header file, from that platform. Underlying software developed based on the AUTOSAR (AUTomotive OpenSystem Architecture) standard will include this file. In some embodiments, the header file can be obtained from a pre-configured or user-specified software project root directory via an automated script. That is, the generator can integrate an automated script configured to receive an input parameter pointing to the root directory path of the target software project. When obtaining the header file for the target platform, the automated script automatically searches for and collects the header file in the root directory and all its subdirectories corresponding to that root directory path. This reduces manual intervention and improves the efficiency of generating calibration description files.

[0030] The compilation artifacts mentioned in this step are indispensable input sources for generating the calibration description file, providing low-level physical information. These artifacts include memory-mapped files, or Map files, which record the addresses of all variables and functions in the ECU's physical memory, reflecting the final memory layout. The generator can read the Map file to obtain the address information of the variables.

[0031] Step 102: Copy the information from the header file to the beginning of the blank description file to obtain the initial description file, and obtain the variable description information according to the data dictionary and the compilation product; This step refers to: the generator creating a new blank description file, which can be a file with only a framework, where the framework can refer to the basic structure of an A2L file; the generator copying the obtained header file information to the beginning of the blank description file, thereby establishing an accurate and consistent basic framework and addressing benchmark for the calibration description file; then, the generator obtaining variable description information based on the data dictionary and compilation artifacts, and using this information to fill in the core content of the file.

[0032] In related technologies, the generated calibration description file directly expands the arrays or tables defined in the code into individual calibration values, which is inconvenient for calibration engineers. Therefore, in some embodiments, before obtaining variable description information based on the data dictionary and the compilation product, the step mentioned in this section may include: classifying the data quantities defined in the data dictionary into observations and calibration values; the observations include model inputs, model outputs, and internal model observations defined in the data dictionary; the calibration values ​​include individual calibration parameters, one-dimensional arrays, and three-dimensional tables. In other words, the generator classifies all inputs, outputs, internal model observations, and calibration values ​​defined in the data dictionary into two categories: one category is observations, corresponding to the inputs, outputs, and internal model observations in the data dictionary; the other category is calibration values, including individual calibration parameters, one-dimensional arrays, and three-dimensional tables. This allows the final generated calibration description file to fully retain the original structure of the one-dimensional arrays and three-dimensional tables, thereby improving the efficiency and accuracy of the calibration work.

[0033] In some embodiments, the variable description information mentioned in this step may include the attribute information, data conversion rules, and corresponding address information of the observed quantities, as well as the attribute information, data conversion rules, and corresponding address information of the calibration quantities. Accordingly, obtaining the variable description information based on the data dictionary and the compilation output mentioned in this step may include: obtaining the attribute information of each observed quantity and the attribute information of each calibration quantity based on the data dictionary; converting the attribute information into a description file format; and generating the data conversion rules for the observed quantities and the calibration quantities; and obtaining the address information corresponding to the observed quantities and the calibration quantities based on the compilation output. That is, the generator traverses all observed quantities and calibration quantities in each category and obtains the attribute information of each observed quantity and calibration quantity, such as name, meaning description, data type, data dimension, etc., and then converts them into a standard description file format according to the ASAM (Association for Standardization of Automation and Measuring Systems) standard, while generating corresponding data conversion rules; furthermore, the generator obtains the address information of each observed quantity and calibration quantity in the description file based on the compilation output. Thus, the automated generation of the calibration description file is achieved.

[0034] Furthermore, in some embodiments, the compilation artifacts mentioned in this step include memory-mapped files, and the attribute information mentioned earlier includes names. Accordingly, obtaining the address information corresponding to the observation and the address information corresponding to the calibration quantity based on the compilation artifacts may include: parsing the memory-mapped file, searching for the corresponding address information in the memory-mapped file based on the names of the observation and the calibration quantity, respectively, to obtain the address information corresponding to the observation and the calibration quantity. In other words, the generator parses the obtained Map file, searches for the corresponding address information in the Map file based on the names of the observation and calibration quantity, and updates the address of each observation and calibration quantity in the description file accordingly. This avoids errors that may arise from manually searching and inputting addresses and can adapt to different hardware platforms and compilation environments.

[0035] Step 103: Update the variable description information to the initial description file to obtain the calibration description file.

[0036] In this embodiment, all the obtained variable description information is updated in the description file that already contains the header file, thus obtaining a calibration description file that can adapt to the target platform. Calibration engineers can complete the calibration work based on this calibration description file, thereby improving the efficiency of project development.

[0037] In this embodiment, the header file recording ECU memory allocation and calibration parameters from the target platform is obtained, along with the data dictionary and compilation artifacts of each software engineering project. A new blank description file is then created, and the information from the obtained header file is copied to the beginning of the blank description file. Variable description information is then obtained based on the data dictionary and compilation artifacts, and this variable description information is updated in the description file that already includes the header file, resulting in the calibration description file. This achieves automated generation of the calibration description file and improves platform compatibility, thereby effectively increasing project development efficiency.

[0038] To provide a more detailed explanation of the solution in this application, a specific embodiment is described below: This embodiment provides a multi-platform compatible automatic calibration description file generation scheme. The scheme designs an automatic calibration file generator that can automatically identify the platform and automatically obtain the platform's ECU memory allocation and calibration parameters, data dictionary, address information, etc., to automatically generate the corresponding calibration description file. The calibration description file contains descriptive information such as the meaning of the observed and calibrated quantities, and is displayed in arrays or tables, consistent with the software design, with strong readability, and is very convenient for carrying out calibration work.

[0039] Specifically, the workflow of this generator in generating calibration description files includes: S201. Obtain the data dictionary; the data dictionary defines all input quantities, output quantities, internal observations of the model, and calibration quantities required for model development. The attributes of these defined quantities include name, meaning description, data type, data dimension (such as array, three-dimensional table, etc.), data attributes (used to distinguish variables, calibration quantities, storage capacity, etc.), functional module to which they belong, calibration description, etc. S202. Obtain the file containing the ECU memory allocation and calibration parameters for the target platform. This file will be referred to as the header file below. S203. Obtain the compilation artifacts from each software project, including Map files; S204. Create a new blank description file and automatically copy the obtained header information to the very beginning of the blank description file; S205. Classify all input / output quantities, model internal observations, and calibration quantities defined in the data dictionary into observations and calibration quantities. The observations correspond to the input quantities, output quantities, and model internal observations in the data dictionary, while the calibration quantities include a single calibration parameter, a one-dimensional array, and a three-dimensional table. S206. Traverse all observations and calibrations in each category, and obtain the attribute information for each observation and calibration. Convert them into a standard description file format according to the ASAM standard format. The ASAM standard format observation description is as follows: Figure 2 As shown, the ASAM standard format calibrated quantity description is as follows: Figure 3 As shown; S207. Generate data conversion rules corresponding to observations and standardization quantities. These data conversion rules include conversion type and data display format. S208. Based on the name information of the observation and calibration quantities, find the corresponding address information in the obtained Map file, and update the address of each observation and calibration quantity in the description file accordingly. S209. Update all observations and calibration values ​​after conversion and update to the description file that already contains the header file, save and close the file; S210, Calibration description file generation complete.

[0040] This embodiment of the solution automates the generation of calibration description files by developing an automatic calibration description file generator. It also platformizes the project, making one tool compatible with multiple platforms, which effectively improves the efficiency of project development. Furthermore, it automatically generates the files in strict accordance with standard formats, which effectively improves compatibility and robustness.

[0041] Corresponding to the embodiments of the aforementioned methods, this application also provides embodiments of a calibration description document generation apparatus and a terminal for its application: like Figure 4 As shown, Figure 4 This is a block diagram of a calibration description file generation apparatus provided in an embodiment of this application. The apparatus includes: The acquisition module 41 is used to acquire the data dictionary, the header file of the target platform, and the compilation products of each software project; the header file is a file that records ECU memory allocation and calibration parameters. Copy module 42 is used to copy the information in the header file to the beginning of the blank description file to obtain the initial description file, and to obtain variable description information according to the data dictionary and the compilation product; The update module 43 is used to update the variable description information to the initial description file to obtain the calibration description file.

[0042] In some embodiments, the copy module 42 includes a classification submodule; the classification submodule is used to classify the data quantities defined in the data dictionary into observation quantities and calibration quantities; the observation quantities include model input quantities, model output quantities, and model internal observation quantities defined in the data dictionary; the calibration quantities include a single calibration parameter, a one-dimensional array, and a three-dimensional table.

[0043] In some embodiments, the variable description information includes the attribute information, data conversion rules, and corresponding address information of the observed quantity, as well as the attribute information, data conversion rules, and corresponding address information of the calibration quantity; the copy module 42 further includes a conversion submodule and an acquisition submodule; the copy submodule is used to: acquire the attribute information of each observed quantity and the attribute information of each calibration quantity according to the data dictionary, convert the attribute information into a description file format, and generate the data conversion rules of the observed quantity and the data conversion rules of the calibration quantity; the acquisition submodule is used to: acquire the address information corresponding to the observed quantity and the address information corresponding to the calibration quantity according to the compilation product.

[0044] The specific implementation process of the functions and roles of each module in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0045] This application also provides an electronic device, please refer to [link to application]. Figure 5 , Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of this application. The electronic device may include a processor 510, a communication interface 520, a memory 530, and at least one communication bus 540. The communication bus 540 is used to enable direct communication between these components. In this embodiment, the communication interface 520 of the electronic device is used for signaling or data communication with other node devices. The processor 510 may be an integrated circuit chip with signal processing capabilities.

[0046] The processor 510 described above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor, or the processor 510 can be any conventional processor.

[0047] The memory 530 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc. The memory 530 stores computer-readable instructions. When these computer-readable instructions are executed by the processor 510, the electronic device can perform the aforementioned operations. Figure 1 The various steps involved in the method implementation examples.

[0048] Alternatively, the electronic device may also include a storage controller and an input / output unit.

[0049] The memory 530, storage controller, processor 510, peripheral interface, and input / output unit are electrically connected directly or indirectly to achieve data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses 540. The processor 510 is used to execute executable modules stored in the memory 530, such as software function modules or computer programs included in electronic devices.

[0050] The input / output unit is used to provide users with the ability to create tasks and to set optional start periods or preset execution times for those tasks, thereby enabling user-server interaction. The input / output unit may be, but is not limited to, a mouse and keyboard.

[0051] Understandable. Figure 5 The structure shown is for illustrative purposes only; the electronic device may also include components that are more advanced than those shown. Figure 5 The more or fewer components shown, or having the same Figure 5 The different configurations shown. Figure 5 The components shown can be implemented using hardware, software, or a combination thereof.

[0052] This application also provides a storage medium storing instructions. When the instructions are run on a computer, the computer program is executed by a processor to implement the method described in the method embodiment. To avoid repetition, the method will not be described again here.

[0053] This application also provides a computer program product that, when run on a computer, causes the computer to perform the method described in the method embodiment.

[0054] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0055] In addition, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0056] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0057] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application. It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0058] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0059] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A method for generating a calibration description file, characterized in that, include: Obtain the data dictionary, header files for the target platform, and compilation artifacts of each software project; The header file is a file that records ECU memory allocation and calibration parameters; Copy the information from the header file to the beginning of the blank description file to obtain the initial description file, and obtain the variable description information based on the data dictionary and the compilation product. The variable description information is updated to the initial description file to obtain the calibration description file.

2. The method according to claim 1, characterized in that, The header file is obtained from the pre-configured or user-specified software project root directory via an automated script.

3. The method according to claim 1, characterized in that, Before obtaining variable description information based on the data dictionary and the compilation output, the process includes: The data quantities defined in the data dictionary are classified into observation quantities and calibration quantities; the observation quantities include model input quantities, model output quantities, and model internal observation quantities defined in the data dictionary; the calibration quantities include single calibration parameters, one-dimensional arrays, and three-dimensional tables.

4. The method according to claim 3, characterized in that, The variable description information includes the attribute information, data transformation rules, and corresponding address information of the observed quantity, as well as the attribute information, data transformation rules, and corresponding address information of the calibrated quantity; The step of obtaining variable description information based on the data dictionary and the compilation output includes: Based on the data dictionary, obtain the attribute information of each observation and the attribute information of each standardization quantity, convert the attribute information into a description file format, and generate the data conversion rules for the observation and the standardization quantity. Based on the compiled output, obtain the address information corresponding to the observation and the address information corresponding to the calibration.

5. The method according to claim 4, characterized in that, The compilation output includes a memory-mapped file; the attribute information includes a name; The step of obtaining the address information corresponding to the observation and the address information corresponding to the calibration quantity based on the compilation output includes: The memory-mapped file is parsed, and the corresponding address information is searched from the memory-mapped file according to the name of the observation and the name of the calibration, respectively, to obtain the address information corresponding to the observation and the address information corresponding to the calibration.

6. A calibration description file generation apparatus, characterized in that, include: The acquisition module is used to acquire the data dictionary, the header files of the target platform, and the compilation artifacts of various software projects; The header file is a file that records ECU memory allocation and calibration parameters; The copy module is used to copy the information in the header file to the beginning of the blank description file to obtain the initial description file, and to obtain variable description information based on the data dictionary and the compilation product. The update module is used to update the variable description information to the initial description file to obtain the calibration description file.

7. The apparatus according to claim 6, characterized in that, The copy module includes a classification submodule; the classification submodule is used to classify the data quantities defined in the data dictionary into observation quantities and calibration quantities; the observation quantities include model input quantities, model output quantities, and model internal observation quantities defined in the data dictionary; the calibration quantities include a single calibration parameter, a one-dimensional array, and a three-dimensional table.

8. The apparatus according to claim 7, characterized in that, The variable description information includes the attribute information, data transformation rules, and corresponding address information of the observed quantity, as well as the attribute information, data transformation rules, and corresponding address information of the calibrated quantity; The copy module further includes a conversion submodule and an acquisition submodule; The copy submodule is used to: obtain the attribute information of each observation and the attribute information of each calibration quantity according to the data dictionary, convert the attribute information into a description file format, and generate the data conversion rules for the observation and the calibration quantity; The acquisition submodule is used to: acquire the address information corresponding to the observation and the address information corresponding to the calibration quantity based on the compilation product.

9. A computer-readable storage medium, characterized in that, It stores a computer program thereon, which, when executed by a processor, implements the method as described in any one of claims 1 to 5.

10. An electronic device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in any one of claims 1 to 5.

Images