Variable batch calibration method and device, electronic equipment and medium
By receiving calibration header files and generating calibration configuration files, the problem of variable calibration in the prior art is solved, batch calibration is realized, calibration testing efficiency and accuracy are improved, and resources are saved.
Patent Information
- Application Number
- CN202411150629.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-21
- Publication Date
- 2024-11-29
AI Technical Summary
In the prior art, variable calibration must be carried out successively, resulting in an increase in time, labor and economic costs, affecting the efficiency of calibration testing.
By receiving the calibration header file, determining the target variables and target storage addresses, generating calibration configuration files, and burning them to the target storage addresses, batch calibration multiple calibration data is realized, and the efficiency of the calibration test process is improved.
Achieve batch calibration of multiple calibration data, improve the work efficiency of calibration test engineers, ensure the accuracy and reliability of calibration data, greatly save time, manpower and economic costs, and ensure that the progress of the product will not be affected by calibration tests. .
Smart Images

Figure CN119046153A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of calibration and testing technology, and in particular to a variable batch calibration method, device, electronic equipment and medium. Background Art
[0002] Calibration testing is an important part of the automotive R&D and production process, including the process of accurately setting and adjusting various control systems on the vehicle to ensure that the corresponding indicators in the vehicle meet the design requirements, including performance, fuel economy, emissions, safety and comfort, etc. Automobile calibration testing is usually carried out under various working conditions. Based on the test results, a set of detailed parameter settings will be formed and written into the vehicle's electronic control unit to ensure that the vehicle performs at its best.
[0003] The specific calibration test needs to use one or more variables of the electronic control unit as calibration test variables, perform calibration tests on the calibration test variables with different calibration values, and obtain the corresponding test verification results. At present, for different calibration values of the same calibration test variable, each calibration variable must be calibrated one by one, which will increase time, manpower, and economic costs, and at the same time, the work efficiency is low, which affects the production progress of the product.
[0004] Therefore, how to provide a solution to the above technical problems is a problem that those skilled in the art need to solve. Summary of the invention
[0005] In view of this, the embodiments of the present application provide a variable batch calibration method, device, electronic device and medium to solve the problem in the prior art that variable calibration must be performed one by one, affecting the efficiency of calibration testing.
[0006] A first aspect of an embodiment of the present application provides a variable batch calibration method, comprising:
[0007] receiving a calibration header file, and determining a target variable and a target storage address based on the calibration header file;
[0008] Determine multiple calibration data for each target variable;
[0009] Generate a calibration configuration file based on the calibration data of all target variables;
[0010] Burn the calibration configuration file to the target storage address so as to perform calibration test using various calibration data by calling the calibration configuration file in the target storage address.
[0011] A second aspect of the embodiment of the present application provides a variable batch calibration device, including:
[0012] A file receiving module, used for receiving a calibration header file, and determining a target variable and a target storage address based on the calibration header file;
[0013] A data determination module, used for determining a plurality of calibration data for each target variable;
[0014] A file generation module, used to generate a calibration configuration file based on the calibration data of all target variables;
[0015] The file burning module is used to burn the calibration configuration file to the target storage address, so as to perform calibration test using various calibration data by calling the calibration configuration file in the target storage address.
[0016] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.
[0017] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.
[0018] Compared with the prior art, the beneficial effects of the embodiments of the present application include at least the following: the embodiments of the present application determine the target variables that need to set calibration data in batches through the calibration header file, and then determine the corresponding multiple calibration data for each target variable, generate a calibration configuration file based on all the calibration data and burn it to the target storage address, the calibration configuration file burned to the target storage address ensures that each calibration data can be used for calibration testing, and this solution realizes batch calibration of multiple calibration data, improves the work efficiency of calibration test engineers by standardizing the calibration test process, efficiently completes the variable calibration requirements before the calibration test, and at the same time ensures the accuracy and reliability of the calibration data, greatly saves time, manpower and economic costs, ensures that the product progress will not be affected by the calibration test, and effectively accelerates the rapid iteration of the product. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application, 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 application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0020] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application;
[0021] Figure 2It is a flow chart of a variable batch calibration method provided in an embodiment of the present application;
[0022] Figure 3 is a schematic diagram of an electronic table provided in an embodiment of the present application;
[0023] Figure 4 is a schematic diagram of another electronic spreadsheet provided in an embodiment of the present application;
[0024] Figure 5 It is a flowchart of a calibration instruction provided in an embodiment of the present application;
[0025] Figure 6 is an example schematic diagram of a calibration instruction provided in an embodiment of the present application;
[0026] Figure 7 is an example schematic diagram of another calibration instruction provided in an embodiment of the present application;
[0027] Figure 8 is an example schematic diagram of another calibration instruction provided in an embodiment of the present application;
[0028] Fig. 9 It is a structural schematic diagram of a variable batch calibration device provided in an embodiment of the present application;
[0029] Fig.10 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0030] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.
[0031] A variable batch calibration method, device, electronic device and medium according to an embodiment of the present application will be described in detail below with reference to the accompanying drawings.
[0032] Figure 1 1 is a schematic diagram of an application scenario of an embodiment of the present application. The application scenario may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a server 104 and a network 105.
[0033] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be hardware or software. When the first terminal device 101, the second terminal device 102, and the third terminal device 103 are hardware, they can be various electronic devices with display screens and support communication with the server 104, including but not limited to vehicle systems, smart phones, tablet computers, laptop portable computers, and desktop computers; when the first terminal device 101, the second terminal device 102, and the third terminal device 103 are software, they can be installed in the above electronic devices. The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be implemented as multiple software or software modules, or as a single software or software module, which is not limited in the embodiment of the present application. Further, various applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as data processing applications, instant messaging tools, social platform software, search applications, shopping applications, etc.
[0034] The server 104 may be a server that provides various services, for example, a background server that receives a request sent by a terminal device that establishes a communication connection with the server, and the background server may receive and analyze the request sent by the terminal device, and generate a processing result. The server 104 may be a single server, or a server cluster composed of several servers, or a cloud computing service center, which is not limited in the present embodiment of the application.
[0035] It should be noted that the server 104 can be hardware or software. When the server 104 is hardware, it can be various electronic devices that provide various services for the first terminal device 101, the second terminal device 102, and the third terminal device 103. When the server 104 is software, it can be multiple software or software modules that provide various services for the first terminal device 101, the second terminal device 102, and the third terminal device 103, or it can be a single software or software module that provides various services for the first terminal device 101, the second terminal device 102, and the third terminal device 103, and the embodiment of the present application does not limit this.
[0036] The network 105 can be a wired network connected by coaxial cable, twisted pair and optical fiber, or it can be a wireless network that can interconnect various communication devices without wiring, such as Bluetooth, Near Field Communication (NFC), infrared, etc., which is not limited in the embodiments of the present application.
[0037] It should be noted that the specific types, quantities and combinations of the first terminal device 101, the second terminal device 102, the third terminal device 103, the server 104 and the network 105 can be adjusted according to the actual needs of the application scenario, and the embodiments of the present application do not limit this.
[0038] Figure 2 It is a flow chart of a variable batch calibration method provided in an embodiment of the present application. Figure 2 The variable batch calibration method can be obtained by Figure 1 The first terminal device, the second terminal device, or the third terminal device is executed. Figure 2 As shown, the variable batch calibration method includes:
[0039] S201: receiving a calibration header file, and determining a target variable and a target storage address based on the calibration header file;
[0040] S202: Determine multiple calibration data for each target variable;
[0041] S203: Generate a calibration configuration file based on the calibration data of all target variables;
[0042] S204: Burn the calibration configuration file to the target storage address, so as to perform calibration test using various calibration data by calling the calibration configuration file in the target storage address.
[0043] It can be understood that the variable batch calibration method in this embodiment is based on the script program running on the test side. The software developer on the development side calibrates all parameter variables that need to be calibrated as target variables in the calibration header file, specifies the target storage address in the calibration header file, and then sends it to the test side. Figure 1 The first terminal device or the second terminal device or the third terminal device is implemented. After the test side receives the calibration header file from the sending side, it runs the script to execute the method of this embodiment, determines the target variable and the target storage address from the calibration header file, and then generates multiple calibration data for each target variable. Finally, it combines all the determined calibration data to generate a calibration configuration file that meets the burning requirements, and burns the calibration configuration file to the target storage address, that is, the batch calibration of the calibration data of the target variable is completed. The target storage address is located in the calibration test object, and the calibration test object is also the object of the calibration test. The test side burns the calibration configuration file to the target storage address of the calibration test object, thereby realizing the test of the calibration test object, that is, calling the calibration configuration file in the target storage address to realize the calibration test of the calibration test object based on each calibration data.
[0044] After the batch calibration is completed in the method of this embodiment, the test side can perform calibration test based on the calibration configuration file burned into the target storage address. The specific means is to call the calibration configuration file in the target storage address to obtain calibration data, and use the calibration data to perform calibration test. Since the calibration data in this embodiment is calibrated in batches at one time, compared with multiple calibrations in the prior art, the efficiency of this embodiment is significantly improved, effectively saving time, manpower, and economic costs, ensuring that the progress of the product calibration test will not be delayed.
[0045] Specifically, the software developer defines all parameter variables that need to be calibrated as a large structure global variable in the calibration header file.h and specifies the target storage address. The method of this embodiment can determine the specific target variable by analyzing the structure global variable. The target storage address can be specified by the C language keyword attribute. For example, the calibration structure type Demarcate_Header is defined as a global variable in the calibration header file.h and the target storage address is specified as 0X20001000. The format is as follows:
[0046] typedef struct{
[0047] char Temperature, / / temperature calibration
[0048] int velocity, / / vehicle speed calibration
[0049] }Demarcate_Header;
[0050] Demarcate_Header Demarcate_data__attribute__((at(0X20001000))).
[0051] The target variables specified by the global variables include temperature and vehicle speed, and the data types of the target variables are further specified, where the data type of temperature is char and the data type of vehicle speed is int.
[0052] It can be understood that the appearance of the calibration header file serves as a trigger for the test side to execute the batch calibration method of variables in this embodiment. However, if the calibration header file is a repeated transmission without updated content and the calibration test object has not changed, since the calibration test object has already executed the batch calibration method of variables of the current calibration header file, there is no need to execute it again. Therefore, the method of this embodiment can compare the received new calibration header file and the current calibration header file that has been executed in advance to see if they are the same. If they are different, the subsequent steps are executed. If they are the same, the execution of this method is stopped. Specifically, the process of receiving the calibration header file and determining the target variable and the target storage address based on the calibration header file includes:
[0053] Receive the calibration header file, and compare whether the calibration header file is the same as the pre-stored calibration header file;
[0054] If not, determine the target variable and the target storage address based on the calibration header file, and update the pre-stored calibration header file to the calibration header file;
[0055] If so, the calibration completion information is returned, and the calibration completion information is used to indicate that the calibration header file has completed the batch calibration of the variables.
[0056] It can be understood that the pre-stored calibration header file here is a historical calibration header file stored in the historical record. The pre-stored calibration header file can be the most recent historical calibration header file or all historical calibration header files in the current calibration test project. The specific setting can be made according to actual needs.
[0057] If the historical calibration header files in the historical records are all calibration header files that have executed the variable batch calibration method, as long as the newly received calibration header file is the same as any pre-stored calibration header file, it will no longer be executed and the calibration completion information will be returned. If the newly received calibration header file is different from all pre-stored calibration header files, continue to execute subsequent steps.
[0058] Specifically, the comparison of whether the calibration header file is identical to the preset calibration header file can be performed by comparing the digest, such as the value of md5.
[0059] If all received historical calibration header files are stored in the historical record without considering the execution progress of the variable batch calibration method, the historical calibration header files include not only the calibration header files whose execution progress is completed, that is, the calibration header files whose variable batch calibration method has been executed, but also the calibration header files whose execution progress is a step to be executed S201-S204 due to user requirements or program failures. At this time, if there is a preset calibration header file that is the same as the calibration header file, the subsequent steps can be continued for the calibration header file according to the specific execution progress of the preset calibration header file and the obtained progress data. Therefore, there is:
[0060] Before determining the target variable and target storage address based on the calibration header file, it also includes:
[0061] Compare whether there is a pre-stored calibration header file that is the same as the calibration header file;
[0062] If not, then executing the action of determining the target variable and the target storage address based on the calibration header file;
[0063] If so, a pre-stored calibration header file identical to the calibration header file is used as a backup calibration header file, and the target variable, target storage address, calibration data and calibration configuration file of the calibration header file are updated according to the progress data of the backup calibration header file.
[0064] Further, the process of updating the target variable, target storage address, calibration data and calibration configuration file of the calibration header file according to the progress data of the standby calibration header file includes:
[0065] If the progress data of the standby calibration header file is empty, executing step S201 to determine the target variable and the target storage address based on the calibration header file;
[0066] If the progress data only includes the target variable and the target storage address, then based on the progress data, step S202 is executed to determine a plurality of calibration data for each target variable;
[0067] If the progress data only includes the target variable, the target storage address and the calibration data, then based on the progress data, step S203 is executed to generate a calibration configuration file based on the calibration data of all the target variables;
[0068] If the progress data includes a target variable, a target storage address, calibration data and a calibration configuration file, based on the progress data, step S204 is executed to burn the calibration configuration file to the target storage address, so as to perform calibration test using each calibration data by calling the calibration configuration file in the target storage address.
[0069] It can be understood that the progress data of the stored backup calibration header file can be directly updated to the corresponding data of the calibration header file. The complete progress data should include the target variable, the target storage address, the calibration data and the calibration configuration file. If the progress data of the backup calibration header file is incomplete, that is, the corresponding data obtained by the calibration header file based on the progress data of the backup calibration header file is not complete enough, it is necessary to continue to execute the corresponding steps of the method of this embodiment to finally obtain the complete corresponding data.
[0070] It can be understood that if the calibration test object has not changed and the calibration test of the calibration test object based on the backup calibration header file has been completed, the progress data must be complete, including the target variable, target storage address, calibration data and calibration configuration file, and the calibration completion information can be directly returned; if the calibration test object has changed, even if the progress data is complete, it is still necessary to execute step S204 on the new calibration test object and burn the calibration configuration file into the target storage address of the new calibration test object.
[0071] It can be understood that in order to improve the efficiency of data management and calibration testing, the progress data of the pre-stored calibration header file can be updated each time the complete progress data of the calibration header file is obtained. The update action can be addition or replacement. If there is no preset calibration header file that is the same as the current calibration header file, the current calibration header file must be recorded as a new preset calibration header file, and then the corresponding progress data must be stored.
[0072] Therefore, based on the calibration data of all target variables, after generating the calibration configuration file, it also includes:
[0073] When there is no pre-stored calibration header file that is identical to the calibration header file, the calibration header file is used as a preset calibration header file to store the corresponding progress data;
[0074] When there is a pre-stored calibration header file that is identical to the calibration header file and the progress data of the pre-stored calibration header file does not include the calibration configuration file, the progress data is updated corresponding to the calibration header file.
[0075] It is understandable that after receiving the calibration header file, the script program is run to execute the variable batch calibration method of this embodiment. The script here can be implemented in Python language, C language or other programming languages, which are not limited here.
[0076] It can be understood that in this embodiment, the script is run to analyze the calibration header file to determine the target variable and the target storage address, and the calibration data of each target variable is determined based on the known target variable. The calibration data is also the calibration value, and multiple calibration data will be generated according to a certain data change rule, such as gradually increasing or decreasing according to a preset step size, and for example, determining the calibration data of another target variable from the known calibration data of one target variable according to the association relationship between the target variables. Specifically, the process of determining multiple calibration data of each target variable includes:
[0077] According to the data variation rules of each target variable, multiple calibration data of each target variable are determined;
[0078] The data variation rule includes at least one of a variation step and a variation relationship between target variables.
[0079] It is understandable that the calibration data, in the process of determining the target variable, needs to be based on necessary constraints, such as data type, data unit, data range, etc. These constraints may exist in the calibration header file, or in the physical relationship of the target variable, or in the script program set in advance to run the method of this embodiment. Specifically, the process of determining multiple calibration data for each target variable includes:
[0080] According to the constraints of all target variables, multiple calibration data of each target variable are determined;
[0081] The constraint condition includes at least one of a data type, a data unit, and a data range of a target variable determined based on a target header file.
[0082] It can be understood that the data type is the data type of the target variable set in the structure global variable in the calibration header file mentioned above; the data unit can be determined by looking up the preset variable-unit relationship table to determine the unit of the target variable. For example, if the target variable is temperature, its data unit is degrees Celsius; if the target variable is vehicle speed, its data unit is km / h; the data range is determined by the content of the calibration test project, indicating the possible value range of the calibration data.
[0083] Furthermore, in order to emphasize the visualization of the method of this embodiment, the target variables and calibration data determined in this embodiment can be displayed on the front end in the form of a specific data table. The specific process of determining multiple calibration data of each target variable includes:
[0084] Based on the data header corresponding to the target variable in the data table, a plurality of calibration data of each target variable is determined in the data table;
[0085] The data table includes any form of data table in electronic form, online web page, or database.
[0086] It is understandable that a spreadsheet is a table that conforms to the format of office Excel software or is compatible with the format of office Excel software, which is not limited here, and the database can select a database type suitable for reading and writing calibration data, which is not limited here.
[0087] Specifically, taking a spreadsheet as an example, the target variable and target storage address determined based on the calibration header file are represented in the spreadsheet as follows: Figure 3 As shown, when determining the calibration data for each target variable in the spreadsheet, the display can be as follows Figure 4 As shown, Figure 4 In the example, the calibration data of temperature is 10 degrees Celsius and the calibration data of vehicle speed is 3 km / h.
[0088] Further, the script is run to execute the step of generating a calibration configuration file. The calibration configuration file is usually a binary file with a suffix of .bin. Binary files use binary encoding to represent the contents of the file and are applied to fields that require files in binary format, such as the storage and loading of program codes of embedded systems, software or firmware upgrades, data storage or loading, data transmission and network communications, etc.
[0089] The reason for generating the calibration configuration file in this embodiment is to convert the target variable and the corresponding calibration data into data that can be directly read and applied in subsequent calibration tests.
[0090] Further, when the generated calibration configuration file is burned into the target storage address, since the target storage address in the method of this embodiment is used for calibration test, a relevant protocol that conforms to the calibration test is used, namely XCP (Universal Measurement And Calibration Protocol), where X represents a variable transport layer protocol. The burning action in this embodiment is executed, and the specific process of burning the calibration configuration file into the target storage address includes:
[0091] Based on the standard protocol specification of XCP, the calibration configuration file is burned to the target storage address.
[0092] It is understandable that the action of burning the calibration configuration file based on the standard protocol specification of XCP can be implemented by a calibration tool that supports the standard protocol specification of XCP, and the calibration requires calibration instructions that support the standard protocol specification of XCP.
[0093] The following is the relevant content about XCP calibration instructions:
[0094] Among them, the instruction 0xF0:DOWNLOAD must be implemented, such as Figure 5 As shown, the DOWNLOAD instruction is executed to download data from the master device to the slave device. Whether the element is BYTE, WORD or DWORD is determined by the number of data AG. When AG>2, the element is determined to be DWORD, and the data has alignment requirements.
[0095] The data block of the specified length contained in the instruction CMD will be copied to the memory starting from the memory transfer address MTA, and MTA will be increased by the number of data.
[0096] Depending on whether the slave device supports block transfer mode, it can be divided into two categories:
[0097] If the slave device does not support block transfer mode, all downloaded data is transferred in a single command packet. Therefore, the value in the number of data elements parameter request must be in the range [1..MAX_CTO-2]. If the number of data elements is greater than MAX_CTO-2, the error message ERR_OUT_OF_RANGE is returned.
[0098] If the slave device supports block transfer mode, the downloaded data will be divided into multiple transmission command packets. For the slave device, there may be a maximum number of consecutive command packets MAX_BS. Therefore, the value range of the number of data elements n is [1..min(MAX_BS*(MAX_CTO-2) / AG,255)]. The master device must transmit (n*AG / (MAX_CTO-2))-1 DOWNLOAD_NEXT command packets continuously, and the slave device will only reply to the last DOWNLOAD_NEXT command packet. The separation time between command packets is specified in the response of CONNECT with the maximum number of packets (MAX_BS,MIN_ST). Figure 6 This is an example of MAX_CTO=8.
[0099] Among them, optional implementation instructions such as 0xEF:DOWNLOAD_NEXT, such as Figure 7 Execute the DOWNLOAD_NEXT instruction to download data from the master device to the slave device.
[0100] If AG = DWORD, 2 alignment bytes must be used to satisfy the alignment requirement. Whether an element is BYTE, WORD or DWORD can be determined by AG. This instruction is used to transfer consecutive data elements for the DOWNLOAD command. The structure of the DOWNLOAD_NEXT command is exactly the same as DOWNLOAD. Number contains the remaining number of data elements to be transferred. The slave device will use this information to detect lost packets. If a sequence error is detected, the error code ERR_SEQUENCE will be returned. If the number of data elements does not match the expected value, the error will return ERR_SEQUENCE. The response will contain the expected number of data elements. Figure 8 This is an example of MAX_CTO=8.
[0101] It can be understood that after the calibration configuration file is burned to the target storage address, the subsequent test end can call the calibration configuration file of the target storage address to perform calibration test using various calibration data. The test result of the calibration test can reflect whether the current calibration data meets the current working condition. If not, feedback adjustment can be performed. Therefore, after the calibration configuration file is burned to the target storage address, the calibration test is performed using various calibration data by calling the calibration configuration file in the target storage address, and further includes:
[0102] Obtaining calibration test results of a calibration test;
[0103] Based on the calibration test results, analyze whether each calibration data meets the test conditions and obtain the analysis results;
[0104] Feedback adjustment is performed on the calibration data based on the analysis results.
[0105] Specifically, the feedback adjustment here includes marking the calibration data that does not meet the working conditions as invalid and no longer using it, deleting the calibration data that does not meet the working conditions, modifying the calibration data that does not meet the working conditions, re-executing steps S201-S204, etc., which are set according to actual conditions and user needs and are not limited here.
[0106] The method of the embodiment of the present application determines the target variables that need to set calibration data in batches through the calibration header file, and then determines the corresponding multiple calibration data for each target variable, generates a calibration configuration file based on all the calibration data and burns it to the target storage address. The calibration configuration file burned to the target storage address ensures that each calibration data can be used for calibration testing. This solution realizes batch calibration of multiple calibration data, improves the work efficiency of calibration test engineers by standardizing the calibration test process, and efficiently completes the variable calibration requirements before the calibration test. At the same time, it ensures the accuracy and reliability of the calibration data, greatly saves time, manpower and economic costs, ensures that the progress of the product will not be affected by the calibration test, and effectively accelerates the rapid iteration of the product.
[0107] All the above optional technical solutions can be combined in any way to form optional embodiments of the present application, and will not be described in detail here. It should be understood that the size of the sequence number of each step in the above embodiment does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
[0108] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.
[0109] Fig. 9 Schematic diagram of a variable batch calibration device provided in an embodiment of the present application. Fig. 9 As shown, the variable batch calibration device includes:
[0110] A file receiving module 901 is used to receive a calibration header file and determine a target variable and a target storage address based on the calibration header file;
[0111] A data determination module 902 is used to determine a plurality of calibration data for each target variable;
[0112] A file generation module 903, used to generate a calibration configuration file based on the calibration data of all target variables;
[0113] The file burning module 904 is used to burn the calibration configuration file to the target storage address, so as to perform calibration test by using various calibration data by calling the calibration configuration file in the target storage address.
[0114] The device of the embodiment of the present application determines the target variables that need to set calibration data in batches through the calibration header file, and then determines the corresponding multiple calibration data for each target variable, generates a calibration configuration file based on all the calibration data and burns it to the target storage address. The calibration configuration file burned to the target storage address ensures that each calibration data can be used for calibration testing. This solution realizes batch calibration of multiple calibration data, improves the work efficiency of calibration test engineers by standardizing the calibration test process, and efficiently completes the variable calibration requirements before the calibration test. At the same time, it ensures the accuracy and reliability of the calibration data, greatly saves time, manpower and economic costs, ensures that the progress of the product will not be affected by the calibration test, and effectively accelerates the rapid iteration of the product.
[0115] In an exemplary embodiment, the data determination module is specifically used to:
[0116] According to the data variation rules of each target variable, multiple calibration data of each target variable are determined;
[0117] The data variation rule includes at least one of a variation step and a variation relationship between target variables.
[0118] In an exemplary embodiment, the data determination module is specifically used to:
[0119] According to the constraints of all target variables, multiple calibration data of each target variable are determined;
[0120] The constraint condition includes at least one of a data type, a data unit, and a data range of a target variable determined based on a target header file.
[0121] In an exemplary embodiment, the data determination module is specifically used to:
[0122] Based on the data header corresponding to the target variable in the data table, determine a plurality of calibration data for each target variable in the data table;
[0123] The data table includes any form of data table in electronic form, online web page, or database.
[0124] In an exemplary embodiment, the file burning module is specifically used for:
[0125] Based on the standard protocol specification of XCP, the calibration configuration file is burned to the target storage address.
[0126] In an exemplary embodiment, the data determination module is further configured to:
[0127] Obtaining calibration test results of a calibration test;
[0128] Based on the calibration test results, analyze whether each calibration data meets the test conditions and obtain the analysis results;
[0129] Feedback adjustment is performed on the calibration data based on the analysis results.
[0130] In an exemplary embodiment, before the file receiving module determines the target variable and the target storage address based on the calibration header file, it is further configured to:
[0131] Compare whether there is a pre-stored calibration header file that is the same as the calibration header file;
[0132] If not, then executing the action of determining the target variable and the target storage address based on the calibration header file;
[0133] If so, a pre-stored calibration header file that is the same as the calibration header file is used as a backup calibration header file, triggering the data determination module, the file generation module or the file burning module to update the target variable, the target storage address, the calibration data and the calibration configuration file of the calibration header file according to the progress data of the backup calibration header file.
[0134] In an exemplary embodiment, the file receiving module is specifically used for:
[0135] If the progress data of the standby calibration header file is empty, an action of determining the target variable and the target storage address based on the calibration header file is performed;
[0136] If the progress data only includes the target variable and the target storage address, a data determination module is triggered based on the progress data;
[0137] If the progress data only includes the target variable, the target storage address and the calibration data, then based on the progress data, the file generation module is triggered;
[0138] If the progress data includes a target variable, a target storage address, calibration data and a calibration configuration file, the file burning module is triggered based on the progress data.
[0139] In an exemplary embodiment, the file generation module is further used to:
[0140] When there is no pre-stored calibration header file that is identical to the calibration header file, the calibration header file is used as a preset calibration header file to store the corresponding progress data;
[0141] When there is a pre-stored calibration header file that is identical to the calibration header file and the progress data of the pre-stored calibration header file does not include the calibration configuration file, the progress data is updated corresponding to the calibration header file.
[0142] It can be understood that the variable batch calibration device in this embodiment is based on the test side. The software developer on the development side calibrates all parameter variables that need to be calibrated as target variables in the calibration header file, specifies the target storage address in the calibration header file, and then sends it to the test side. After receiving the calibration header file from the sending side, the variable batch calibration device on the test side determines the target variable and the target storage address from the calibration header file, and then generates multiple calibration data for each target variable. Finally, a calibration configuration file that meets the burning requirements is generated in combination with all the determined calibration data, and the calibration configuration file is burned to the target storage address, that is, the batch calibration of the calibration data of the target variable is completed. After the device of this embodiment completes the batch calibration, the test side can perform a calibration test based on the calibration configuration file burned to the target storage address. The specific means is to call the calibration configuration file in the target storage address to obtain the calibration data, and use the calibration data to perform a calibration test. Since the calibration data in this embodiment is calibrated in batches at one time, compared with multiple calibrations in the prior art, the efficiency of this embodiment is significantly improved, effectively saving time, manpower, and economic costs, ensuring that the progress of product calibration testing will not be delayed.
[0143] Fig.10 Schematic diagram of an electronic device 10 provided in an embodiment of the present application. Fig.10 As shown, the electronic device 10 of this embodiment includes: a processor 1001, a memory 1002, and a computer program 1003 stored in the memory 1002 and executable on the processor 1001. When the processor 1001 executes the computer program 1003, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 1001 executes the computer program 1003, the functions of the modules / units in the above-mentioned device embodiments are implemented.
[0144] The electronic device 10 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 10 may include, but is not limited to, a processor 1001 and a memory 1002. Those skilled in the art will appreciate that Fig.10 The electronic device 10 is merely an example and does not limit the electronic device 10 . The electronic device 10 may include more or fewer components than shown in the figure, or different components.
[0145] Processor 1001 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
[0146] The memory 1002 may be an internal storage unit of the electronic device 10, for example, a hard disk or memory of the electronic device 10. The memory 1002 may also be an external storage device of the electronic device 10, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card (FlashCard), etc. equipped on the electronic device 10. The memory 1002 may also include both an internal storage unit of the electronic device 10 and an external storage device. The memory 1002 is used to store computer programs and other programs and data required by the electronic device.
[0147] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.
[0148] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. Computer-readable storage media may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.
[0149] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.
Claims
1. A variable batch calibration method, characterized in that: include: receiving a calibration header file, and determining a target variable and a target storage address based on the calibration header file; Determining a plurality of calibration data for each of the target variables; generating a calibration configuration file based on the calibration data of all the target variables; The calibration configuration file is burned into the target storage address, so as to perform a calibration test using each calibration data by calling the calibration configuration file in the target storage address.
2. The method according to claim 1, characterized in that The process of determining a plurality of calibration data for each of the target variables comprises: Determine a plurality of calibration data of each target variable according to the data variation rule of each target variable; The data change rule includes at least one of a change step and a change relationship between each of the target variables.
3. The method according to claim 1, characterized in that The process of determining a plurality of calibration data for each of the target variables comprises: According to the constraints of all the target variables, determining a plurality of calibration data for each of the target variables; The constraint condition includes at least one of a data type, a data unit, and a data range of the target variable determined based on the target header file.
4. The method according to claim 1, characterized in that: The process of determining a plurality of calibration data for each of the target variables comprises: Based on the data header corresponding to the target variable in the data table, determining a plurality of calibration data of each target variable in the data table; The data table includes any form of data table in an electronic table, an online webpage, or a database.
5. The method according to any one of claims 1 to 4, characterized in that: Before determining the target variable and the target storage address based on the calibration header file, the method further includes: Comparing whether there is a pre-stored calibration header file that is identical to the calibration header file; If not, then performing an action of determining a target variable and a target storage address based on the calibration header file; If so, the pre-stored calibration header file that is the same as the calibration header file is used as the standby calibration header file, and the target variable, the target storage address, the calibration data and the calibration configuration file of the calibration header file are updated according to the progress data of the standby calibration header file.
6. The method according to claim 5, characterized in that The process of updating the target variable, the target storage address, the calibration data and the calibration configuration file of the calibration header file according to the progress data of the standby calibration header file comprises: If the progress data of the standby calibration header file is empty, an action of determining a target variable and a target storage address based on the calibration header file is performed; If the progress data only includes the target variable and the target storage address, then based on the progress data, performing an action of determining a plurality of calibration data for each of the target variables; If the progress data only includes the target variable, the target storage address and the calibration data, then based on the progress data, executing the action of generating a calibration configuration file based on the calibration data of all the target variables; If the progress data includes the target variable, the target storage address, the calibration data and the calibration configuration file, then based on the progress data, the action of burning the calibration configuration file to the target storage address is executed, so as to perform a calibration test using each calibration data by calling the calibration configuration file in the target storage address.
7. The method according to claim 5, characterized in that After generating a calibration configuration file based on the calibration data of all the target variables, the method further includes: When there is no pre-stored calibration header file that is identical to the calibration header file, taking the calibration header file as a preset calibration header file and storing the corresponding progress data; When the pre-stored calibration header file exists and is identical to the calibration header file and the progress data of the pre-stored calibration header file does not include the calibration configuration file, the progress data is updated accordingly according to the calibration header file.
8. A variable batch calibration device, characterized in that: include: A file receiving module, used for receiving a calibration header file, and determining a target variable and a target storage address based on the calibration header file; A data determination module, used for determining a plurality of calibration data for each of the target variables; A file generating module, used for generating a calibration configuration file based on the calibration data of all the target variables; The file burning module is used to burn the calibration configuration file to the target storage address, so as to perform calibration test by using each calibration data by calling the calibration configuration file in the target storage address.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
