Method for identifying and configuring different ECU calibration protocol files

Abstract

The embodiment of the invention relates to the technical field of file processing, and discloses a method for identifying and configuring different ECU calibration protocol files, which comprises the following steps of: firstly, disassembling an ECU file into a plurality of DCM files one by one according to a pre-configured disassembling rule, then verifying the plurality of DCM files according to a pre-configured verification rule, and when the DCM files are successfully verified, verifying the DCM files according to the verification rule. And synthesizing the plurality of DCM files according to a pre-configured synthesis rule to form a full file meeting requirements. Thus, according to the technical scheme, an effective solution can be provided for processing of different ECU calibration protocol files, the file processing accuracy and processing efficiency are improved, the flexibility is enhanced, and the quality of full files is guaranteed.

Description

Technical Field

[0001] The present invention relates to the technical field of file processing, and in particular to a method for identifying and configuring different ECU calibration protocol files. Background Art

[0002] In today's automotive industry, as the degree of automobile intelligence and automation continues to improve, the role of electronic control units (ECUs) in automobiles has become increasingly critical. Different models and different core components of the same model are often equipped with different ECUs, which makes the management of ECU files extremely complicated. For example, the ECU files used by engine management systems, brake systems, etc. of different models are different, and the ECU files of the power system and safety system of the same model are also different.

[0003] The existing ECU calibration protocol file processing methods have many drawbacks. On the one hand, there is a lack of a unified and effective identification and configuration method for ECU files of different models or different core components of the same model, which leads to confusion during the processing, resulting in low efficiency and accuracy of ECU file configuration. Summary of the invention

[0004] The main purpose of the present invention is to provide a method and system for identifying and configuring different ECU calibration protocol files, aiming to solve the technical problems of low efficiency and accuracy of ECU file configuration in the prior art.

[0005] To achieve the above objectives, in a first aspect, an embodiment of the present application provides a method for identifying and configuring different ECU calibration protocol files, the method comprising: Acquire multiple target ECU files, wherein the multiple target ECU files include at least a first ECU file and a second ECU file, the first ECU file and the second ECU file are ECU files of different vehicle models, or the first ECU file and the second ECU file are ECU files of different core components of the same vehicle model; Performing parameter configuration on the target ECU file, the parameter configuration includes one or more of a disassembly rule configuration, a file description configuration, a file parameter configuration, a file grouping configuration, a verification rule configuration, and a full file synthesis rule configuration, the verification rule configuration includes a first verification rule configuration and a second verification rule configuration, the verification rule obtained by the first verification rule configuration is a unified verification rule, and the verification rule obtained by the second verification rule configuration is an independent verification rule matching the target ECU file; Disassembling the multiple target ECU files according to the disassembly rules obtained by the disassembly rule configuration to obtain multiple DCM files; Verifying the plurality of DCM files according to the unified verification rule and the independent verification rule; When the DCM file verification succeeds, the multiple DCM files are synthesized according to the synthesis requirements obtained by configuring the full file synthesis rule to obtain the full file.

[0006] In a possible implementation, the disassembling of the plurality of target ECU files according to the disassembly rule configured to obtain the plurality of DCM files includes: Disassembling the first ECU file according to the disassembly rule to obtain a first DCM file and a second DCM file, wherein the first DCM file is a data file of a first target function module, and the second DCM file is a data file of a second target function module; Disassembling the second ECU file according to the disassembly rule to obtain a third DCM file and a fourth DCM file, wherein the third DCM file is a data file of the first target function module, and the fourth DCM file is a data file of the second target function module; In a possible implementation, when the DCM file verification succeeds, synthesizing the multiple DCM files according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain the full file includes: The first DCM file and the third DCM file are synthesized according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain a first full file, where the first full file is a full file that uniformly represents the first target functional module; The second DCM file and the fourth DCM file are synthesized according to the synthesis requirements obtained by configuring the full file synthesis rule to obtain a second full file, where the second full file is a full file that uniformly represents the second target functional module.

[0007] In a possible implementation, when the DCM file verification succeeds, synthesizing the multiple DCM files according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain the full file includes: Determine a first target DCM file in the first DCM file and the third DCM file according to the file parameter configuration, where the first target DCM file is a data file of a first target functional module; Determine a second target DCM file in the second DCM file and the fourth DCM file according to the file parameter configuration, where the second target DCM file is a data file of a second target function module; The first target DCM file and the second target DCM file are synthesized according to the synthesis requirements obtained by configuring the full file synthesis rule to obtain a full file.

[0008] In a possible implementation, the disassembling of the plurality of target ECU files according to the disassembly rule configured to obtain the plurality of DCM files includes: Disassembling the first ECU file according to the disassembly rule to obtain a fifth DCM file, wherein the fifth DCM file is a data file of a first target functional module of a target automobile system; The second ECU file is disassembled according to the disassembly rule to obtain a sixth DCM file, wherein the sixth DCM file is a data file of the second target functional module of the target automobile system.

[0009] In a possible implementation, when the DCM file verification succeeds, synthesizing the multiple DCM files according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain the full file includes: The fifth DCM file and the sixth DCM file are synthesized according to the synthesis requirements obtained by configuring the full file synthesis rule to obtain a third full file. The third full file is a full file that uniformly represents the target vehicle system. The third full file at least includes the full representation of the first target function module and the second target function module in the target vehicle system.

[0010] In a possible implementation, the parameter configuration of the target ECU file includes: Identify the file suffixes and the internal contents and formats of the multiple target ECU files; According to the file suffix and the internal content and format of the file, a pre-established parameter configuration mapping table is searched to perform parameter configuration on the target ECU file.

[0011] In a possible implementation, verifying the multiple DCM files according to the unified verification rule and the independent verification rule includes: Perform parameter verification of common sensor data according to the unified verification rules, and if the parameter verification of the unified sensor data passes, perform targeted verification based on specific sensor data of DCM files of different sources or functions; and / or, CRC check is used to determine whether there is data loss in all DCM files. When there is no data loss in each DCM file, the integrity of key data fields is verified according to the specific integrity requirements of DCM files from different sources or functions.

[0012] In a possible implementation, the performing parameter verification of common sensor data according to a unified verification rule includes: Extracting common sensor data from a plurality of DCM files, wherein the common sensor data includes temperature sensor data and pressure sensor data; For the temperature sensor data, the temperature deviation coefficient K is calculated according to formula (1): T , when the temperature deviation coefficient K T Satisfy the inequality K min ≤ K T ≤K max When the temperature sensor data passes the verification, K min and K max It is the lower and upper limits of the temperature deviation coefficient that are pre-set according to the sensor performance specifications and system stability requirements; For the pressure sensor data, the pressure normalization value Np is calculated according to formula (2). When Np satisfies the inequality N Pmin ≤N P ≤N Pmax When the pressure sensor data passes the verification, N Pmin and N Pmax It is the lower and upper limits of the pressure normalization value pre-set according to the allowable range of system pressure and safety requirements; ; Among them, T i represents the temperature sensor measurement value in the i-th DCM file, n is the number of DCM files involved in the calculation, T ref is the preset reference temperature value, which is determined according to the nominal operating temperature range of the sensor and system requirements; P is the pressure sensor data in the DCM file, P min and P max They are the minimum and maximum working pressure values ​​of this type of pressure sensor.

[0013] In a second aspect, an embodiment of the present application further provides a file identification and configuration system, comprising a memory and a processor, wherein the memory is used to store program code, and the processor is used to call the program code to execute the method described in the first aspect.

[0014] Different from the prior art, the embodiment of the present application provides a method for identifying and configuring different ECU calibration protocol files. The method first obtains multiple target ECU files, and then performs parameter configuration on the multiple target ECU files. The parameter configuration includes one or more of disassembly rule configuration, file description configuration, file parameter configuration, file grouping configuration, verification rule configuration, and full file synthesis rule configuration. The verification rule configuration includes a first verification rule configuration and a second verification rule configuration. The verification rule obtained by the first verification rule configuration is a unified verification rule, and the verification rule obtained by the second verification rule configuration is an independent verification rule that matches the target ECU file; then, the multiple target ECU files are disassembled according to the disassembly rules obtained by the disassembly rule configuration to obtain multiple DCM files; then, the multiple DCM files are verified according to the unified verification rules and the independent verification rules; finally, when the DCM file verification is successful, the multiple DCM files are synthesized according to the synthesis requirements obtained by the full file synthesis rule configuration to obtain a full file. That is, first, the ECU file is disassembled into multiple DCM files one by one according to the pre-configured disassembly rules, and then the multiple DCM files are verified according to the pre-configured verification rules. When the DCM file verification is successful, the multiple DCM files are synthesized according to the pre-configured synthesis rules to form a full file that meets the requirements. In this way, the technical solution of the present application can provide an effective solution for the processing of different ECU calibration protocol files, improve the accuracy and efficiency of file processing, enhance flexibility and ensure the quality of full files. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying creative work.

[0016] Figure 1 This is a flowchart of a method for identifying and configuring different ECU calibration protocol files in some embodiments of the present application; Figure 2 A flowchart of a method for identifying and configuring different ECU calibration protocol files in other embodiments of the present application; Figure 3 This is a schematic diagram of ECU calibration protocol file configuration in some embodiments of the present application; Figure 4 This is a schematic diagram of the hardware structure of the file identification and configuration system in some embodiments of the present application.

[0017] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0018] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0019] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0020] In addition, the descriptions of "first", "second", etc. in the present invention are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, "and / or" in the full text includes three solutions. Taking A and / or B as an example, it includes technical solution A, technical solution B, and technical solution that satisfies both A and B. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on the ability of ordinary technicians in this field to implement. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0021] In today's automotive industry, as the degree of automobile intelligence and automation continues to improve, the role of electronic control units (ECUs) in automobiles has become increasingly critical. Different models and different core components of the same model are often equipped with different ECUs, which makes the management of ECU files extremely complicated. For example, the ECU files used by engine management systems, brake systems, etc. of different models are different, and the ECU files of the power system and safety system of the same model are also different.

[0022] The existing ECU calibration protocol file processing methods have many drawbacks. On the one hand, there is a lack of a unified and effective identification and configuration method for ECU files of different models or different core components of the same model, which leads to confusion during the processing, resulting in low efficiency and accuracy of ECU file configuration.

[0023] like Figure 1-Figure 3As shown, the following takes the file identification and configuration system executing the different ECU calibration protocol file identification and configuration method as an example for explanation. It should be noted that although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here. Please refer to the attached Figure 1 The method includes the following steps S200 to S800: Step S200, obtaining a plurality of target ECU files, wherein the plurality of target ECU files include at least a first ECU file and a second ECU file, the first ECU file and the second ECU file are ECU files of different vehicle models, or the first ECU file and the second ECU file are ECU files of different core components of the same vehicle model; In the embodiment of the present application, the acquisition of multiple target ECU files can be active acquisition, such as actively sending an acquisition request instruction to the file data terminal for active acquisition. It can also be passive acquisition, such as a user uploading a corresponding ECU file on the system, and after the system detects the ECU file, the ECU file uploaded by the user is used as the current target ECU file.

[0024] It is understandable that for different file management requirements, the sources or types of different ECU files may be different. For example, the multiple target ECU files include the first ECU file and the second ECU file. The first ECU file and the second ECU file can be ECU files of different models, such as ECU files of model A and model B; or the first ECU file and the second ECU file can be ECU files of the same model but different core components, such as the first ECU file is the ECU file of the power system, and the second ECU file is the ECU file of the safety system. The power system can be the engine management system, and the safety system can be the braking system.

[0025] For example, for automobile manufacturers, unified management of numerous ECU files according to vehicle models can improve file management efficiency and vehicle production efficiency.

[0026] Step S400, performing parameter configuration on the target ECU file, the parameter configuration including one or more of a disassembly rule configuration, a file description configuration, a file parameter configuration, a file grouping configuration, a verification rule configuration, and a full file synthesis rule configuration, the verification rule configuration including a first verification rule configuration and a second verification rule configuration, the verification rule obtained by the first verification rule configuration is a unified verification rule, and the verification rule obtained by the second verification rule configuration is an independent verification rule matching the target ECU file; In an embodiment of the present application, parameter configuration of the target ECU file may be performed autonomously by the system or jointly by the user and the system. The parameter configuration includes one or more of disassembly rule configuration, file description configuration, file parameter configuration, file grouping configuration, verification rule configuration, and full file synthesis rule configuration.

[0027] In one embodiment, if Figure 3 As described above, after the user uploads the ECU file on the system and clicks "Confirm", the system automatically triggers the rule configuration, such as popping up configuration function options such as "disassembly rule configuration", "verification rule configuration" and "full file synthesis rule configuration". After the user completes the configuration of all rules, the system can obtain each configuration rule.

[0028] It should be noted that the verification rule configuration may include a first verification rule configuration and a second verification rule configuration. The verification rule obtained by the first verification rule configuration is a unified verification rule, and the verification rule obtained by the second verification rule configuration is an independent verification rule that matches the target ECU file. The unified verification rule is a verification that performs unified characterization on all files, and the independent verification rule is a differentiated verification on different files.

[0029] Exemplarily, a unified voltage value parameter check is performed on the files corresponding to the engine management system ECU and the brake system ECU, while a separate engine temperature parameter value check is performed on the files corresponding to the engine management system ECU, and a friction temperature parameter value check is performed on the files corresponding to the brake system ECU.

[0030] In other embodiments, step S400: parameter configuration of the target ECU file includes: identifying the file suffixes and the internal content and format of the multiple target ECU files; searching a pre-established parameter configuration mapping table according to the file suffixes and the internal content and format of the files to parameter configure the target ECU file.

[0031] Specifically, the embodiment of the present application pre-establishes a parameter configuration mapping table, which is the core of the entire step. It is a data structure that stores the relationship between different file suffixes, internal content and formats and corresponding parameter configurations. The function of the mapping table is to associate the identified file features (suffix, internal content and format) with specific parameter configurations.

[0032] The file suffix is ​​an important identifier of the file type, and different suffixes may represent different file storage structures and encoding methods. For example, some ECU files may have a .bin suffix, indicating that it may be a binary file, and a .xml suffix may mean that the file uses XML format to store information. Identifying the file suffix helps to initially understand the type of the file and provide clues for subsequent searches for corresponding parameter configurations. However, the file suffix alone may not be enough to fully grasp the detailed information of the file, so the embodiment of the present application also needs to view the internal content and format of the file. The internal content of the file may contain some special identifiers, data structures, or key information, which can help determine the function and nature of the file. The format of the file may involve the organization of the data, such as whether the data is arranged in byte order, the size of the data block, whether it contains specific header information, etc. By identifying the internal content and format of the file, the file can be classified and processed more accurately.

[0033] Once the file suffix, internal content and format of the target ECU file are identified, the matching entry can be found in the parameter configuration mapping table, and then the corresponding parameter configuration can be applied to the ECU file. For example, if an ECU file is identified as a .bin suffix and contains a specific identifier, the corresponding parameter configuration in the mapping table can include disassembly rules (how to split the binary file into multiple DCM files), verification rules (such as checking the data range of certain specific byte positions), and file description information.

[0034] Step S600, disassembling the plurality of target ECU files according to the disassembly rules obtained by the disassembly rule configuration to obtain a plurality of DCM files; In one embodiment, the step S600: disassembling the multiple target ECU files according to the disassembly rules obtained by the disassembly rule configuration to obtain multiple DCM files, including: disassembling the first ECU file according to the disassembly rules to obtain a first DCM file and a second DCM file, the first DCM file is a data file of a first target function module, and the second DCM file is a data file of a second target function module; disassembling the second ECU file according to the disassembly rules to obtain a third DCM file and a fourth DCM file, the third DCM file is a data file of the first target function module, and the fourth DCM file is a data file of the second target function module.

[0035] Specifically, if the disassembly rule configured in step S500 is "disassembling the ECU file according to different vehicle models and different functional modules to obtain a DCM file", for example, the ECU files of different functional modules of different vehicle models are disassembled. Therefore, the first ECU file (corresponding to vehicle model A) can be disassembled to obtain the first DCM file and the second DCM file; wherein the first DCM file is the data file of the first target functional module of vehicle model A, and the second DCM file is the data file of the second target functional module of vehicle model A. The first target functional module can be the power module of the vehicle, and the second target functional module can be the brake module of the vehicle. Similarly, the second ECU file (corresponding to vehicle model B) can be disassembled to obtain the third DCM file and the fourth DCM file; wherein the third DCM file is the data file of the first target functional module of vehicle model B, and the fourth DCM file is the data file of the second target functional module of vehicle model B.

[0036] In another embodiment, the step S600: disassembling the multiple target ECU files according to the disassembly rules obtained by the disassembly rule configuration to obtain multiple DCM files, including: disassembling the first ECU file according to the disassembly rules to obtain a fifth DCM file, wherein the fifth DCM file is a data file of the first target functional module of the target automobile system; disassembling the second ECU file according to the disassembly rules to obtain a sixth DCM file, wherein the sixth DCM file is a data file of the second target functional module of the target automobile system.

[0037] Specifically, if the disassembly rule configured in step S500 is "disassembling the ECU file according to the functional module to obtain the DCM file", for example, the ECU files of different functional modules of the same vehicle model are disassembled. Therefore, the first ECU file can be disassembled to obtain the fifth DCM file, and the second ECU file can be disassembled to obtain the sixth DCM file. The first ECU file and the fifth DCM file can correspond to the first target functional module of the vehicle, such as the vehicle power module; the second ECU file and the sixth DCM file can correspond to the second target functional module of the vehicle, such as the vehicle brake module.

[0038] Exemplarily, the first ECU file and the second ECU file corresponding to the power module and the brake module of the vehicle, respectively, can be disassembled according to the rule to obtain respective DCM files (fifth DCM file and sixth DCM file).

[0039] Step S800: verifying the multiple DCM files according to the unified verification rule and the independent verification rule; In the embodiment of the present application, unified verification rules and independent verification rules are used to verify the multiple DCM files formed by disassembly, providing a more comprehensive inspection mechanism for different types of DCM files, ensuring the quality and correctness of DCM files, and thus providing a basis for the accuracy of subsequent full files.

[0040] In one embodiment, the step S800: verifying the plurality of DCM files according to the unified verification rule and the independent verification rule includes: Perform parameter verification of common sensor data according to the unified verification rules, and if the parameter verification of the unified sensor data passes, perform targeted verification based on specific sensor data of DCM files of different sources or functions; and / or, CRC check is used to determine whether there is data loss in all DCM files. When there is no data loss in each DCM file, the integrity of key data fields is verified according to the specific integrity requirements of DCM files from different sources or functions.

[0041] Specifically, first determine which are common sensor data. Common sensor data refers to sensor data that exists in multiple DCM files and is universal or related. For example, data such as vehicle speed sensors and temperature sensors may be involved in different functional modules or DCM files from different sources. For these common sensor data, parameter verification is performed according to unified verification rules. The unified verification rules may include checking the value range, data type, data accuracy, etc. of these data. For example, for vehicle speed sensor data, it can be specified that its value range is between 0 and the maximum allowed vehicle speed (assuming it is 200km / h), the data type is a floating point number, and the accuracy is one decimal place. If the parameter verification of the common sensor data fails, the corresponding DCM file is marked as verification failure, and the error information is recorded to facilitate subsequent processing. After the parameter verification of the common sensor data passes, the specific sensor data in the DCM files of different sources or functions is verified. For each DCM file, according to its source (such as different models, different core components) or function (such as engine control, brake control), find the corresponding independent verification rule. For example, for the DCM file of engine control, it may contain oxygen sensor data. The independent verification rules will specify the parameter range and update frequency of the oxygen sensor data to check whether the data meets the requirements of the engine control module. For different DCM files, the corresponding specific sensor data is checked one by one according to its specific independent verification rules to ensure that it meets the performance and safety requirements of the respective functional modules.

[0042] Similarly, CRC (cyclic redundancy check) can be performed on all DCM files to check whether there is any data loss. CRC check is a common data integrity check method. By calculating the CRC value of the file and comparing it with the expected CRC value, if the two do not match, it means that the file may have data loss. After confirming that each DCM file passes the CRC check (that is, there is no data loss), the integrity of the key data fields is verified according to the specific integrity requirements of DCM files from different sources or functions. For different DCM files, check whether the key data fields are complete according to their specific integrity requirements. For example, for the DCM file of brake control, it may be required that key data fields such as brake pressure and braking distance must be complete, and no missing values ​​are allowed; for the DCM file of engine control, it may be required that key data fields such as injection amount and ignition advance angle cannot be missing.

[0043] In one embodiment, the step of performing parameter verification of common sensor data according to a unified verification rule includes: Extracting common sensor data from a plurality of DCM files, wherein the common sensor data includes temperature sensor data and pressure sensor data; For the temperature sensor data, the temperature deviation coefficient K is calculated according to formula (1): T , when the temperature deviation coefficient K T Satisfy the inequality K min ≤ K T ≤K max When the temperature sensor data passes the verification, K min and K max It is the lower and upper limits of the temperature deviation coefficient that are pre-set according to the sensor performance specifications and system stability requirements; For the pressure sensor data, the pressure normalization value Np is calculated according to formula (2). When Np satisfies the inequality N Pmin ≤N P ≤N Pmax When the pressure sensor data passes the verification, N Pmin and N Pmax It is the lower and upper limits of the pressure normalization value pre-set according to the allowable range of system pressure and safety requirements; ; Among them, T i represents the temperature sensor measurement value in the i-th DCM file, n is the number of DCM files involved in the calculation, T ref is the preset reference temperature value, which is determined according to the nominal operating temperature range of the sensor and system requirements; P is the pressure sensor data in the DCM file, P min and P maxThey are the minimum and maximum working pressure values ​​of this type of pressure sensor.

[0044] It is understandable that in the same vehicle system, different DCM files may record the temperature sensor data of different parts of the vehicle or at different times. Therefore, for the same vehicle system, the matching of sensor data of common sensors in different DCM files and their own accuracy are crucial to the stability of the vehicle. The sensor performance specification determines the fluctuation range of the measured value of the sensor itself under normal working conditions, and the system stability requirements take into account the requirements of the entire system for the accuracy and stability of temperature sensor data. If KT exceeds this range, it means that there may be anomalies in the temperature sensor data or the range of temperature sensor data that needs to be controlled (or the temperature sensor data in each DCM file does not match), which may affect the normal operation and performance of the system, so it does not pass the verification; on the contrary, if it is within the range, the data is considered reliable and passes the verification.

[0045] The allowable range of system pressure refers to the pressure range that the system can withstand during normal operation. Safety requirements take into account the damage that may be caused to the system if the pressure exceeds or falls below a certain range, such as component damage, system performance degradation, or safety accidents. If Np is not within this range, it means that the pressure sensor measurement value or the pressure sensor data to be controlled may be inaccurate and requires further inspection and processing, so it fails the verification; if it is within the range, it means that the pressure sensor data meets the system requirements and passes the verification.

[0046] Step S1000: When the DCM file verification succeeds, the multiple DCM files are synthesized according to the synthesis requirements obtained by configuring the full file synthesis rule to obtain a full file.

[0047] In one embodiment, step S1000: when the DCM file verification is successful, the multiple DCM files are synthesized according to the synthesis requirements obtained by the full file synthesis rule configuration to obtain a full file, including: according to the synthesis requirements obtained by the full file synthesis rule configuration, the first DCM file and the third DCM file are synthesized to obtain a first full file, the first full file is a full file that uniformly represents the first target functional module; according to the synthesis requirements obtained by the full file synthesis rule configuration, the second DCM file and the fourth DCM file are synthesized to obtain a second full file, the second full file is a full file that uniformly represents the second target functional module.

[0048] Specifically, after obtaining the first DCM file, the second DCM file, the third DCM file and the fourth DCM file in step S600, the first DCM file and the third DCM file can be synthesized according to the synthesis requirements to obtain the first full file, and the first full file is a full file that uniformly represents the first target functional module. The second DCM file and the fourth DCM file can also be synthesized to obtain a second full file, and the second full file is a full file that uniformly represents the second target functional module. In other words, the ECU files of a specific functional module of different models can be integrated to form a full file according to the configuration requirements. For automobile manufacturers or R&D personnel, this unified representation helps to compare, analyze and manage different models from the perspective of functional modules, which facilitates subsequent development and maintenance work. For example, if the first target functional module is an engine control system, then the first full file can integrate the ECU information of the engine control systems of different models to make it easier to understand and process.

[0049] In another embodiment, the step S1000: when the DCM file verification succeeds, synthesizing the multiple DCM files according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain the full file includes: Step S1100: determining a first target DCM file in the first DCM file and the third DCM file according to the file parameter configuration, wherein the first target DCM file is a data file of a first target functional module; Step S1200: Determine a second target DCM file in the second DCM file and the fourth DCM file according to the file parameter configuration, where the second target DCM file is a data file of a second target functional module.

[0050] Step S1300: synthesize the first target DCM file and the second target DCM file according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain a full file.

[0051] Specifically, after obtaining the first DCM file, the second DCM file, the third DCM file and the fourth DCM file in step S600, the first target DCM file can be determined in the first DCM file and the third DCM file according to time or importance. For example, the first DCM file and the third DCM file are both engine management system files, and the first DCM file is a file equipped with the latest control algorithm, then the first DCM file can be used as a representative file of the engine management system. Similarly, the second target DCM file can be determined in the second DCM file and the fourth DCM file, and the second target DCM file can be used as a representative file of the second target functional module. Finally, the first target DCM file and the second target DCM file are synthesized to obtain a full file. In this way, since the use of the latest control algorithm means better fuel efficiency, lower emissions or better power performance, the above-mentioned file synthesis scheme can ensure that the final synthesized full file contains the most advanced functions and performance information. For automobile manufacturers or R&D personnel, the optimal full file can be applied to automobile production, which helps to improve the performance and efficiency of the entire system.

[0052] In another embodiment, when the DCM file verification is successful, the multiple DCM files are synthesized according to the synthesis requirements obtained by the full file synthesis rule configuration to obtain a full file, including: according to the synthesis requirements obtained by the full file synthesis rule configuration, the fifth DCM file and the sixth DCM file are synthesized to obtain a third full file, the third full file is a full file that uniformly represents the target vehicle system, and the third full file at least includes the full representation of the first target functional module and the second target functional module in the target vehicle system.

[0053] Specifically, after obtaining the fifth DCM file and the sixth DCM file in step S600, the fifth DCM file and the sixth DCM file can be synthesized to obtain a third full file, which is a full file that uniformly represents the target vehicle system. In other words, the generated third full file uniformly represents the target vehicle system, including the full representation of the first target functional module and the second target functional module. This provides a convenient way for automobile manufacturers or R&D personnel to concentrate the information of different functional modules in one file, which is convenient for unified management of the entire automobile system.

[0054] like Figure 4 As shown, Figure 4This is a hardware structure diagram of the file identification and configuration system in some embodiments of the present application. The file identification and configuration system provided in the embodiments of the present application also includes a memory 1000 and a processor 2000, wherein the memory 1000 is used to store computer-readable instructions, and the processor 2000 is used to call the computer-readable instructions to execute the different ECU calibration protocol file identification and configuration methods as described above.

[0055] Among them, the processor 2000 is used to provide computing and control capabilities to control the file identification and configuration system to perform corresponding tasks, for example, the control file identification and configuration system performs different ECU calibration protocol file identification and configuration methods in any of the above method embodiments, the method comprising: obtaining multiple target ECU files, wherein the multiple target ECU files at least include a first ECU file and a second ECU file, the first ECU file and the second ECU file are ECU files of different vehicle models, or the first ECU file and the second ECU file are ECU files of different core components of the same vehicle model; performing parameter configuration on the target ECU file, the parameter configuration including disassembly rule configuration, file description configuration, file parameter configuration, file classification configuration, and file classification configuration. One or more of group configuration, verification rule configuration, and full file synthesis rule configuration, the verification rule configuration includes a first verification rule configuration and a second verification rule configuration, the verification rule obtained by the first verification rule configuration is a unified verification rule, and the verification rule obtained by the second verification rule configuration is an independent verification rule that matches the target ECU file; the multiple target ECU files are disassembled according to the disassembly rules obtained by the disassembly rule configuration to obtain multiple DCM files; the multiple DCM files are verified according to the unified verification rules and the independent verification rules; when the DCM file verification is successful, the multiple DCM files are synthesized according to the synthesis requirements obtained by the full file synthesis rule configuration to obtain a full file.

[0056] The processor 2000 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), a hardware chip, or any combination thereof; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or any combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0057] The memory 1000, as a non-transient computer-readable storage medium, can be used to store non-transient software programs, non-transient computer executable programs and modules, such as program instructions / modules corresponding to the different ECU calibration protocol file identification and configuration methods in the embodiments of the present application. The processor 2000 can implement the different ECU calibration protocol file identification and configuration methods in any of the above method embodiments by running the non-transient software programs, instructions and modules stored in the memory 1000.

[0058] Specifically, the memory 1000 may include a volatile memory (VM), such as a random access memory (RAM); the memory 1000 may also include a non-volatile memory (NVM), such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD) or other non-transitory solid-state storage device; the memory 1000 may also include a combination of the above-mentioned types of memory.

[0059] To sum up, the file identification and configuration system of the present application adopts the technical solution of any one of the above-mentioned different ECU calibration protocol file identification and configuration method embodiments. Therefore, it has at least the beneficial effects brought by the technical solution of the above-mentioned embodiments, which will not be repeated here one by one.

[0060] The embodiment of the present application also provides a computer-readable storage medium, such as a memory including a program code, and the program code can be executed by a processor to complete the different ECU calibration protocol file identification and configuration methods in the above embodiment. For example, the computer-readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CDROM), a magnetic tape, a floppy disk, and an optical data storage device.

[0061] The present application also provides a computer program product, which includes one or more program codes stored in a computer-readable storage medium. The processor of the file identification and configuration system reads the program code from the computer-readable storage medium, and the processor executes the program code to complete the steps of the different ECU calibration protocol file identification and configuration method provided in the above embodiment.

[0062] A person skilled in the art will appreciate that all or part of the steps for implementing the above embodiments may be accomplished by hardware or by hardware associated with a program code, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0063] It should be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0064] Through the description of the above embodiments, it can be clearly understood by those skilled in the art that each embodiment can be implemented by means of software plus a general hardware platform, or by hardware. It can be understood by those skilled in the art that all or part of the processes in the above embodiment methods can be completed by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above methods. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0065] The above description is only a preferred embodiment of the present invention, and does not limit the patent scope of the present invention. All equivalent structural changes made by using the contents of the present invention specification and drawings under the inventive concept of the present invention, or directly / indirectly applied in other related technical fields are included in the patent protection scope of the present invention.

Claims

1. A method for identifying and configuring different ECU calibration protocol files, characterized in that: The method comprises: Acquire multiple target ECU files, wherein the multiple target ECU files include at least a first ECU file and a second ECU file, the first ECU file and the second ECU file are ECU files of different vehicle models, or the first ECU file and the second ECU file are ECU files of different core components of the same vehicle model; Performing parameter configuration on the target ECU file, the parameter configuration includes one or more of a disassembly rule configuration, a file description configuration, a file parameter configuration, a file grouping configuration, a verification rule configuration, and a full file synthesis rule configuration, the verification rule configuration includes a first verification rule configuration and a second verification rule configuration, the verification rule obtained by the first verification rule configuration is a unified verification rule, and the verification rule obtained by the second verification rule configuration is an independent verification rule matching the target ECU file; Disassembling the multiple target ECU files according to the disassembly rules obtained by the disassembly rule configuration to obtain multiple DCM files; Verifying the plurality of DCM files according to the unified verification rule and the independent verification rule; When the DCM file verification succeeds, the multiple DCM files are synthesized according to the synthesis requirements obtained by configuring the full file synthesis rule to obtain the full file.

2. The method for identifying and configuring different ECU calibration protocol files according to claim 1, characterized in that: The disassembling rules obtained by the disassembling rule configuration are used to disassemble the multiple target ECU files to obtain multiple DCM files, including: Disassembling the first ECU file according to the disassembly rule to obtain a first DCM file and a second DCM file, wherein the first DCM file is a data file of a first target function module, and the second DCM file is a data file of a second target function module; The second ECU file is disassembled according to the disassembly rule to obtain a third DCM file and a fourth DCM file, wherein the third DCM file is a data file of the first target function module, and the fourth DCM file is a data file of the second target function module.

3. The method for identifying and configuring different ECU calibration protocol files as claimed in claim 2, characterized in that: In the case where the DCM file verification succeeds, synthesizing the multiple DCM files according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain the full file includes: The first DCM file and the third DCM file are synthesized according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain a first full file, where the first full file is a full file that uniformly represents the first target functional module; The second DCM file and the fourth DCM file are synthesized according to the synthesis requirements obtained by configuring the full file synthesis rule to obtain a second full file, where the second full file is a full file that uniformly represents the second target functional module.

4. The method for identifying and configuring different ECU calibration protocol files as claimed in claim 2, characterized in that: In the case where the DCM file verification succeeds, synthesizing the multiple DCM files according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain the full file includes: Determine a first target DCM file in the first DCM file and the third DCM file according to the file parameter configuration, where the first target DCM file is a data file of a first target functional module; Determine a second target DCM file in the second DCM file and the fourth DCM file according to the file parameter configuration, where the second target DCM file is a data file of a second target function module; The first target DCM file and the second target DCM file are synthesized according to the synthesis requirements obtained by configuring the full file synthesis rule to obtain a full file.

5. The method for identifying and configuring different ECU calibration protocol files as claimed in claim 1, characterized in that: The disassembling rules obtained by the disassembling rule configuration are used to disassemble the multiple target ECU files to obtain multiple DCM files, including: Disassembling the first ECU file according to the disassembly rule to obtain a fifth DCM file, wherein the fifth DCM file is a data file of a first target functional module of a target automobile system; The second ECU file is disassembled according to the disassembly rule to obtain a sixth DCM file, wherein the sixth DCM file is a data file of the second target functional module of the target automobile system.

6. The method for identifying and configuring different ECU calibration protocol files as claimed in claim 5, characterized in that: In the case where the DCM file verification succeeds, synthesizing the multiple DCM files according to the synthesis requirement obtained by configuring the full file synthesis rule to obtain the full file includes: The fifth DCM file and the sixth DCM file are synthesized according to the synthesis requirements obtained by configuring the full file synthesis rule to obtain a third full file. The third full file is a full file that uniformly represents the target vehicle system. The third full file at least includes the full representation of the first target function module and the second target function module in the target vehicle system.

7. The method for identifying and configuring different ECU calibration protocol files as claimed in claim 1, characterized in that: The parameter configuration of the target ECU file includes: Identify the file suffixes and the internal contents and formats of the multiple target ECU files; According to the file suffix and the internal content and format of the file, a pre-established parameter configuration mapping table is searched to perform parameter configuration on the target ECU file.

8. The method for identifying and configuring different ECU calibration protocol files as claimed in claim 1, characterized in that: The verifying the plurality of DCM files according to the unified verification rule and the independent verification rule includes: Perform parameter verification of common sensor data according to the unified verification rules, and if the parameter verification of the unified sensor data passes, perform targeted verification based on specific sensor data of DCM files of different sources or functions; and / or, CRC check is used to determine whether there is data loss in all DCM files. When there is no data loss in each DCM file, the integrity of key data fields is verified according to the specific integrity requirements of DCM files from different sources or functions.

9. The method for identifying and configuring different ECU calibration protocol files as claimed in claim 8, characterized in that: The parameter verification of the common sensor data according to the unified verification rule includes: Extracting common sensor data from a plurality of DCM files, wherein the common sensor data includes temperature sensor data and pressure sensor data; For the temperature sensor data, the temperature deviation coefficient K is calculated according to formula (1): T , when the temperature deviation coefficient K T Satisfy the inequality K min ≤ K T ≤K max When the temperature sensor data passes the verification, K min and K max It is the lower and upper limits of the temperature deviation coefficient that are pre-set according to the sensor performance specifications and system stability requirements; For the pressure sensor data, the pressure normalization value Np is calculated according to formula (2). When Np satisfies the inequality N Pmin ≤N P ≤N Pmax When the pressure sensor data passes the verification, N Pmin and N Pmax It is the lower and upper limits of the pressure normalization value pre-set according to the allowable range of system pressure and safety requirements; ； Among them, T i represents the temperature sensor measurement value in the i-th DCM file, n is the number of DCM files involved in the calculation, T ref is a preset reference temperature value, which is determined according to the nominal operating temperature range of the sensor and system requirements; P is the pressure sensor data in the DCM file, P min and P max are the minimum and maximum working pressure values ​​of the pressure sensor respectively.

10. A file identification and configuration system, characterized in that: The method comprises a memory and a processor, wherein the memory is used to store program codes, and the processor is used to call the program codes to execute the method according to any one of claims 1 to 9.

Images