A vehicle off-line calibration method based on a vehicle terminal, a vehicle terminal and a vehicle

Abstract

The present application belongs to the technical field of vehicle calibration, and particularly relates to a vehicle offline calibration method based on a vehicle terminal, a vehicle terminal and a vehicle. The method comprises: calibrating a to-be-calibrated ECU of a to-be-calibrated vehicle according to received calibration file information; the calibration file information is information related to the to-be-calibrated ECU obtained by a cloud platform according to calibration instruction information sent by a mobile terminal; and the calibration instruction information is information sent by a calibration personnel to the cloud platform through the mobile terminal. The present application realizes wireless calibration of the ECU through the vehicle terminal based on the network connection characteristics of the vehicle terminal and the characteristics of communication with all ECUs of the vehicle, improves the calibration efficiency, and does not need to connect numerous calibration wire harnesses and frequently switch calibration tools, thereby improving the calibration efficiency and simplifying the calibration process. The present application solves the technical problems of complex calibration process and low efficiency in the prior art.

Description

Technical Field

[0001] This invention belongs to the field of vehicle calibration technology, specifically relating to a vehicle off-line calibration method based on an on-board terminal, as well as the on-board terminal and the vehicle. Background Technology

[0002] Currently, when calibrating vehicles off the production line, the variety of Electronic Control Units (ECUs) requiring calibration makes it impossible to guarantee production line cycle time using calibration tools provided by various suppliers on-line. Therefore, current vehicle off-line calibration often adopts a pre-process approach, meaning the ECUs are calibrated before assembly on the production line. For example... Figure 1 As shown, in the prior art, the ECUs that need to be calibrated are first calibrated at the calibration station, with some calibrations using large industrial control computers and others using calibration tools provided by suppliers; then the calibrated ECUs are assembled on the production line; and finally, functional verification is performed after the vehicle assembly is completed.

[0003] However, for commercial vehicles, orders are highly customized, with almost every order having a unique configuration. Furthermore, each model requires the calibration of multiple ECU types, each with its own calibration interface, calibration file format, calibration protocol, and calibration duration. Therefore, the following problems exist: 1) Due to the high degree of customization and numerous configuration types, a large number of configuration files need to be generated during the R&D and production stages, resulting in a heavy workload and a high risk of errors; 2) For ECUs calibrated using industrial control computers (ICCs), calibration personnel need to maintain all calibration files in the ICC in advance. Since the same ICC may calibrate ECUs for multiple orders and production lines, calibration files are prone to errors. Calibration files require manual management, and the large number of configurations and inconsistent storage lead to chaotic management and difficulty in retrieval; 3) For ECUs with integrated calibration processes on ICCs, due to inconsistent calibration interfaces and numerous configurations, constant switching of calibration harnesses and different calibration files is required during calibration using the ICC, resulting in low efficiency, complex operation, and a high risk of incorrect configurations; 4) 1) When using an industrial control computer for calibration, it is difficult to analyze the cause of anomalies during offline testing. The calibration operation record of the material at that time can only be queried on the corresponding industrial control computer according to the date, and it is not possible to trace the calibration result of a specific ECU, which may lead to ECU calibration omissions; 5) For ECU types that are not integrated into the industrial control computer, calibration is required using calibration tools provided by the supplier at the production line or specific locations. Different calibration tools and wiring harnesses need to be changed during the calibration process, which is complicated and requires a high level of expertise; 6) All operations require professional personnel to perform calibration in specific positions, resulting in high personnel redundancy, low calibration efficiency, and low level of intelligence; 7) Calibration anomalies can only be discovered at the offline testing stage, resulting in poor timeliness of handling. Summary of the Invention

[0004] The purpose of this invention is to provide a vehicle off-line calibration method based on an in-vehicle terminal, as well as the in-vehicle terminal and the vehicle, to solve the technical problems of complex and inefficient calibration processes in the prior art.

[0005] To address the aforementioned technical problems, the present invention provides a technical solution for a vehicle off-line calibration method based on an in-vehicle terminal: a vehicle off-line calibration method based on an in-vehicle terminal, the method comprising: calibrating the ECU to be calibrated of the vehicle to be calibrated according to received calibration file information; wherein the calibration file information is information related to the ECU to be calibrated obtained by a cloud platform based on calibration instruction information sent by a mobile terminal; wherein the calibration instruction information is information sent by calibration personnel to the cloud platform via a mobile terminal.

[0006] The beneficial effects of the above technical solution are as follows: The technical solution of the vehicle off-line calibration method based on an in-vehicle terminal of the present invention belongs to an improved invention. Based on the network characteristics of the in-vehicle terminal and its ability to communicate with all ECUs of the vehicle, the present invention achieves wireless calibration of the ECUs through the in-vehicle terminal, improving calibration efficiency. It eliminates the need for numerous calibration harnesses and frequent switching of calibration tools, thus improving calibration efficiency and simplifying the calibration process. The present invention solves the technical problems of complex and inefficient calibration processes in the prior art.

[0007] Furthermore, the calibration process for the vehicle to be calibrated based on the received calibration file information is divided into multiple threads, including a calibration file acquisition thread, a calibration file parsing thread, and a calibration process control thread. The calibration file acquisition thread is used to acquire the calibration file from the cloud platform based on the ECU information to be calibrated and its calibration file address in the calibration file information. The calibration file parsing thread is used to parse the calibration file acquired by the calibration file acquisition thread to obtain calibration data for calibrating the ECU to be calibrated. The calibration process control thread is used to calibrate the ECU to be calibrated based on the calibration data.

[0008] Furthermore, the method of obtaining the calibration file from the cloud platform based on the ECU information to be calibrated and its calibration file address in the calibration file information includes: if obtaining the calibration file from the cloud platform fails, the calibration file is obtained again until the number of times the calibration file is obtained fails reaches a preset first set number, then the ECU corresponding to the calibration file is determined to have failed calibration; if obtaining the calibration file from the cloud platform is successful, a calibration file parsing thread is created and triggered when no ECU is being calibrated and the calibration file parsing thread does not exist.

[0009] Furthermore, the method for parsing the calibration file obtained by the calibration file acquisition thread includes: after parsing the calibration file, firstly placing the parsed calibration data into a structure corresponding to the ECU to be calibrated; then performing a validity check on the calibration data in the structure. If the structure passes the validity check, the calibration data in the structure is sent to the calibration process control thread; otherwise, the structure is cleared.

[0010] Furthermore, the method of calibrating the ECU to be calibrated according to the calibration data includes: calibrating the ECU according to the calibration data and the calibration method supported by the corresponding ECU to successfully write the calibration parameters in the calibration data into the corresponding ECU; if there is a step that fails to execute during the calibration process, the step is re-executed until the number of times the step fails to execute reaches a preset second set number, then the ECU is determined to have failed to calibrate.

[0011] Furthermore, the method of calibrating the ECU to be calibrated according to the calibration data also includes: after the calibration parameter in the calibration data is successfully written to the corresponding ECU, if the calibration parameter successfully written and read from the ECU is consistent with the value of the calibration parameter in the calibration information, then the calibration parameter is determined to be calibrated successfully; otherwise, the calibration parameter is determined to be calibrated unsuccessfully.

[0012] Furthermore, the calibration data used in the ECU calibration process is: calibration data that has passed the validity check of the calibration process control thread; if the calibration data fails the validity check of the calibration process control thread, the ECU calibration corresponding to the calibration data is determined to have failed.

[0013] Furthermore, the plurality of threads also includes a calibration service management thread; the calibration service management thread is used to: if the calibration service management thread receives a calibration start instruction issued by the cloud platform, then create and trigger the calibration file acquisition thread if the calibration file acquisition thread does not exist.

[0014] Furthermore, the calibration service management thread is also used to: if the calibration service management thread receives the calibration completion instruction sent by the calibration process control thread and detects that the calibration file corresponding to the ECU to be calibrated has been successfully downloaded, then the calibration file parsing thread is triggered until all ECUs are calibrated.

[0015] Furthermore, after all ECUs are calibrated, the vehicle terminal uploads the calibration results of all ECUs to the cloud platform, so that the cloud platform can send the list of ECUs that failed calibration, the reasons for the failure, and the corresponding handling solutions to the mobile terminal.

[0016] The present invention also provides a technical solution for an in-vehicle terminal: an in-vehicle terminal including a processor, the processor being used to execute a computer program to implement the steps of the vehicle off-line calibration method based on the in-vehicle terminal as described above.

[0017] The present invention also provides a technical solution for a vehicle: a vehicle including an on-board terminal, wherein the on-board terminal is the on-board terminal as described above. Attached Figure Description

[0018] Figure 1 A flowchart for calibrating the off-line production of vehicles using existing technologies; Figure 2 This is a flowchart illustrating the vehicle off-line calibration process according to an embodiment of the vehicle off-line calibration method based on an in-vehicle terminal of the present invention. Figure 3 This is a schematic diagram of the overall thread of the T-BOX in an embodiment of the vehicle off-line calibration method based on an in-vehicle terminal of the present invention; Figure 4 This is a flowchart of the V+ platform instruction receiving thread in an embodiment of the vehicle off-line calibration method based on an in-vehicle terminal of the present invention. Figure 5 This is a flowchart of the calibration business management thread in an embodiment of the vehicle off-line calibration method based on an in-vehicle terminal of the present invention. Figure 6 This is a flowchart of the calibration process control thread in an embodiment of the vehicle off-line calibration method based on an in-vehicle terminal of the present invention. Figure 7 This is a flowchart of the calibration file download thread in an embodiment of the vehicle off-line calibration method based on an in-vehicle terminal of the present invention. Figure 8 This is a flowchart of the calibration file parsing thread in an embodiment of the vehicle off-line calibration method based on an in-vehicle terminal of the present invention. Detailed Implementation

[0019] This invention leverages the connectivity of in-vehicle terminals and their ability to communicate with all ECUs in the vehicle. It enables wireless calibration of ECUs via the in-vehicle terminal, improving calibration efficiency. This eliminates the need for numerous calibration harnesses and frequent tool switching, thus simplifying the calibration process and improving overall efficiency. This invention addresses the technical problems of complex and inefficient calibration processes in existing technologies.

[0020] Example of a vehicle off-line calibration method based on an in-vehicle terminal: The vehicle off-line calibration method based on the in-vehicle terminal in this embodiment can be implemented based on a calibration system that includes a cloud platform, an in-vehicle terminal, and a mobile terminal.

[0021] This embodiment of the vehicle off-line calibration method based on the above-mentioned calibration system includes: calibrating the ECU to be calibrated of the vehicle to be calibrated according to the received calibration file information; the calibration file information is information related to the ECU to be calibrated obtained by the cloud platform according to the calibration instruction information sent by the mobile terminal; the calibration instruction information is information sent by the calibration personnel to the cloud platform through the mobile terminal.

[0022] The hardware device used to calibrate the ECU of the vehicle to be calibrated based on the received calibration file information is an in-vehicle terminal that enables communication between the vehicle and the cloud platform.

[0023] In this embodiment, the cloud platform is the V+ platform, the vehicle terminal is a smart vehicle terminal (Telematics BOX, T-BOX), and the mobile terminal is a tablet computer.

[0024] T-BOX is a device installed inside the vehicle to enable information transmission between the cloud and the entire vehicle. It has functions such as power management, CAN communication, 3G / 4G / 5G communication, and positioning, and can realize time information reporting, remote query, and remote control functions.

[0025] The V+ platform is a cloud platform for vehicle networking systems, providing a communication and operation interface between people and vehicles. It is used to collect, store, statistically analyze, and perform analysis of vehicle operation status data and maintenance data, issue remote vehicle control commands, and provide an interactive interface between people and vehicles.

[0026] In other embodiments, the mobile terminal may also be a portable laptop computer or other portable mobile terminal.

[0027] In this embodiment, the ECU is the vehicle's electronic control unit, responsible for controlling related modules and functions, recording status, and other functions.

[0028] The production line calibration process based on the vehicle off-line calibration method of this embodiment is as follows: Figure 2 As shown, firstly, technicians fill in the parameter data to be calibrated through the Intelligent Bill of Materials (iBOM) system according to the order requirements; on the production line, each ECU to be calibrated is assembled first. After assembly, the calibration personnel issue calibration instructions through the Manufacturing Execution System (MES) APP on the tablet to complete the calibration; after calibration is completed and the vehicle is off the production line, the vehicle's functions are verified according to the order requirements to ensure that the requirements are met.

[0029] iBOM refers to the extraction and unified management of core business elements related to products throughout an enterprise, forming an enterprise-level product data management system. This system supports the entire product development process from planning, R&D, manufacturing to production, and supports the maintenance of BOMs at different business stages, including early BOMs, EBOMs, P / MBOMs, cost BOMs, procurement BOMs, and other BOMs. It also supports the distribution and reconstruction of BOM data, including the management of product configuration changes, engineering changes, manufacturing changes, after-sales changes, overseas changes, temporary changes, and breakpoints. iBOM manages changes in various business areas and achieves tight coupling and closed-loop change management between change orders and data.

[0030] MES is a production information management system for the shop floor execution layer of manufacturing enterprises. It can provide enterprises with management modules including manufacturing data management, planning and scheduling management, production scheduling management, inventory management, quality management, human resource management, work center / equipment management, tooling management, procurement management, cost management, project dashboard management, production process control, lower-level data integration and analysis, and upper-level data integration and decomposition, creating a solid, reliable, comprehensive, and feasible manufacturing collaborative management platform for enterprises.

[0031] The following is a detailed description of the vehicle off-line calibration method based on the vehicle terminal in this embodiment.

[0032] In this embodiment, a visual configuration interface is developed in the iBOM system beforehand, which includes information such as parameter item name, parameter ID, parameter type, parameter value, and calibration channel. The parameter name, parameter ID, and parameter type are preset and do not need to be changed during maintenance, thereby reducing the workload and convenience of technicians in maintaining calibration parameters.

[0033] The first step is preparation before the vehicle goes on the production line. Before the ordered vehicle goes on the production line, technicians first fill in the data items that need to be calibrated in the iBOM system. After completion, the iBOM system automatically generates a JSON format data stream and the file name information to be generated, and pushes it to the V+ platform through the interface provided by the V+ platform. After receiving the pushed data stream through the communication interface with iBOM, the V+ platform creates a JSON format file to store the corresponding calibration data according to the received file name information, generating a JSON format calibration file.

[0034] Calibration is performed by the calibration function in the MES APP on the PAD (i.e., tablet computer). The operation method is to select the date, order, and vehicle. MES will obtain the list of ECUs that need to be calibrated for the vehicle in that order from the Enterprise Resource Management System (Systems Application and Products in Data Processing, SAP). It can support the selection of one or more ECUs for calibration, and also supports one-click calibration of the whole vehicle. After the operator clicks the calibration or one-click calibration button, the MES APP will automatically transmit the calibration instruction information to the V+ platform through the interface provided by the V+ platform.

[0035] In this embodiment, the ECU list includes the address of the ECU to be calibrated, the calibration method, the list of Data Identifiers (DIDs), prerequisites, and the vehicle lock address. The ECU address refers to the ECU's address in the vehicle's Controller Area Network (CAN). Calibration methods include DID calibration, file calibration, and address calibration. Prerequisites refer to the requirements the vehicle must meet before formal calibration, such as whether the vehicle is locked.

[0036] After receiving the calibration instruction information, the V+ platform generates a vehicle-cloud calibration message (i.e., calibration file information) for interaction with the T-BOX by generating a list of information such as the ECU information to be calibrated, the calibration file address, and the calibration method. The calibration message is then sent to the T-BOX of the corresponding vehicle via a long connection.

[0037] like Figure 3 As shown, the T-BOX, as the calibration master node, has four threads related to calibration: a calibration business management thread, a calibration file acquisition thread, a calibration file parsing thread, and a calibration process control thread. The calibration business management thread handles calibration business management; the calibration file download thread (i.e., the calibration file acquisition thread) downloads calibration files sequentially, stores the downloaded results in the corresponding structure, and triggers the calibration parsing thread; the calibration file parsing thread parses the successfully downloaded calibration files and triggers the calibration process; and the calibration process control thread controls the calibration interaction protocol and process execution with the ECU.

[0038] In this embodiment, the calibration file acquisition thread is a calibration file download thread, meaning the T-BOX obtains the calibration file from the V+ platform via download. In other embodiments, for better calibration efficiency, the V+ platform can also proactively send the required calibration file to the T-BOX and store it in a designated path on the T-BOX's local machine. In this case, the calibration file address mentioned above should be the storage path of the calibration file, and the calibration file acquisition thread can retrieve the calibration file locally through the storage path.

[0039] In addition, there is a V+ platform instruction receiving thread for receiving V+ platform instructions, such as... Figure 4 As shown, upon receiving the calibration instruction message sent by the V+ platform, the system parses the message and determines whether it is valid. If valid, the calibration service management thread is triggered to begin calibration.

[0040] like Figure 5 As shown, after receiving the calibration start command, the calibration business management thread initializes the global structures related to calibration if a calibration file download thread exists; otherwise, it creates a new calibration file download thread. Then, the calibration file download thread is triggered to start working. It should be noted that the global structures are initialized synchronously when a new calibration file download thread is created.

[0041] like Figure 7 As shown, the calibration file download thread downloads calibration files one by one according to the file address in the ECU list in the calibration instruction, in the order of the ECU list. Files that fail to download will be retried twice. If all three attempts (i.e., the first set number of attempts) fail, the calibration of that ECU is recorded as failed, and the reason for failure is that the calibration file download failed. If the download is successful, the number of successfully downloaded files is recorded, and it is determined whether there is an ECU being calibrated (i.e., in the calibration process control thread). If not, the calibration file parsing thread is triggered.

[0042] like Figure 8 As shown, after receiving the start parsing command, the calibration file parsing process reads the ECU information to be calibrated and the calibration file content, parses the JSON format calibration file, and places the parsed calibration data and preconditions into the corresponding memory structure; then, it performs a validation of the calibration data (i.e., ...). Figure 8 (Whether there is valid calibration information in the data). If the validity check fails, the corresponding structure will be cleared; if the validity check passes, the calibration instruction will be sent to the calibration process control thread.

[0043] Specifically, the calibration data includes data type, data length, and data value. Validity checks include whether the data type and data value are consistent, and whether the data length and data value length are consistent. If the data type and data value are consistent, and the data length and data value length are consistent, then the calibration parameter corresponding to the data value is considered valid calibration information, and the structure to which the calibration parameter belongs is valid.

[0044] For a valid structure that has both valid calibration information and invalid calibration information, only the valid calibration information is calibrated during calibration, and the invalid calibration information is not calibrated.

[0045] like Figure 6As shown, after receiving the calibration message, the calibration process control thread verifies the validity of the calibration parameters (i.e., the validity check of the calibration process control thread). If invalid, it returns a calibration failure for the ECU, indicating that the calibration parameters are invalid. Otherwise, it begins to gradually interact with the ECU to perform calibration process data according to the calibration method supported by the ECU. If a step fails during the process (such as mode switching failure, failure to disable non-diagnostic communication, etc.), it retryes twice. If all three attempts (i.e., the second set number of attempts) fail, a calibration failure is reported, and the reason for failure is reported as the reason for the last execution. After the calibration parameters are written, each successfully written parameter is read, and the data read from the ECU is compared with the data to be written. If they match, the parameter is marked as calibrated successfully; otherwise, the parameter is marked as calibrated failed.

[0046] In this embodiment, both the first set number of times and the second set number of times are 3. In other embodiments, the first set number of times and the second set number of times can also be set to other values ​​based on experience and actual calibration tools or methods, and the values ​​of the first set number of times and the second set number of times do not have to be equal.

[0047] like Figure 5 As shown, after the calibration process control thread returns the calibration results to the calibration business management thread, the calibration management thread generates a calibration result file based on the calibration results and uploads it to a designated directory on the specified server, which is then queried by subsequent calibration results. After the calibration result file is successfully uploaded, when a calibration file is successfully downloaded for an ECU to be calibrated, the calibration file parsing thread is triggered again to start the calibration process for the next ECU, until all ECUs are calibrated (including calibration failures). The calibration results of all ECUs are then compiled and uploaded to the V+ platform. The V+ platform parses the calibration results, matches the corresponding failure handling solutions, and then sends the calibration results and failure handling solutions back to the MES APP for display.

[0048] The production line directly installs the uncalibrated ECUs into the vehicle. After the vehicle assembly is completed, the calibration personnel use the MES APP to select the order and vehicle and click one-click calibration. After waiting a few minutes according to the number of parts to be calibrated, they check the calibration results displayed on the APP. If the calibration fails, they follow the prompts to handle it. If it succeeds, the calibration is complete.

[0049] The MES APP allows users to check the last calibration status of a vehicle at any time, and also to view the parameters and results of each calibration, facilitating the traceability of vehicle ECU parameters.

[0050] Vehicle-mounted terminal example: An in-vehicle terminal includes a processor for executing a computer program to implement the steps of the vehicle off-line calibration method based on the in-vehicle terminal as described above. The in-vehicle terminal is used to transmit information between the vehicle and a cloud platform to calibrate the ECU of the vehicle to be calibrated based on calibration file information received by the in-vehicle terminal. The specific vehicle off-line calibration method based on the in-vehicle terminal has been described in sufficient detail in the above embodiments and will not be repeated here.

[0051] Specifically, a processor can be a CPU, or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor. A processor can also be a processor that supports the Advanced Reduced Instruction Set Machine (ARM) architecture.

[0052] Specifically, the vehicle-mounted terminal is a T-BOX.

[0053] Vehicle Example: A vehicle includes an on-board terminal, which includes a processor for executing a computer program to implement the steps of the vehicle off-line calibration method based on the on-board terminal as described above. The on-board terminal is used to transmit information between the vehicle and a cloud platform to calibrate the ECU of the vehicle to be calibrated based on calibration file information received by the on-board terminal. The specific vehicle off-line calibration method based on the on-board terminal has been described in sufficient detail in the above embodiments and will not be repeated here.

[0054] Specifically, a processor can be a CPU, or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor. A processor can also be a processor that supports the Advanced Reduced Instruction Set Machine (ARM) architecture.

[0055] This invention has the following characteristics: 1. Develop a visual configuration tool in iBOM to generate configuration files in a fixed format, simplifying the generation of diverse configurations, and ensuring all operations are traceable; 2. Intelligent calibration system: Uses a unified platform for calibration file management, solving the problem of chaotic calibration file management; 3. The intelligent calibration system is easy to operate, addressing the challenges of high professional requirements for calibration workers and complex calibration operations.

[0056] 4. Intelligent calibration system: The T-BOX is used for calibration via the vehicle's CAN network and in-vehicle Ethernet, eliminating the need for numerous calibration harnesses and frequent tool switching, thus improving calibration efficiency and simplifying the calibration process.

[0057] 5. T-BOX can be compatible with and automatically process the calibration protocol and process of each ECU. After calibration is completed, it will automatically perform a readback operation on the calibrated parameters and perform readback verification to ensure the accuracy of the uploaded calibration results.

[0058] 6. T-BOX generates calibration results for each ECU, with the results detailed down to the calibration results of each parameter. If calibration fails, the generated failure reason details the specific steps and causes of the failure. The V+ platform can generate operation suggestions based on the reported failure reasons, simplifying the analysis process and professional requirements of calibration failure. It can also solve the problem of delayed discovery of calibration anomalies, prevent problems from flowing to the testing stage, and improve vehicle off-line efficiency.

[0059] Finally, it should be noted that the above descriptions are merely preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still make modifications to the technical solutions described in the foregoing embodiments without creative effort, or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A vehicle off-line calibration method based on an in-vehicle terminal, characterized in that, The method includes: calibrating the ECU of the vehicle to be calibrated according to the received calibration file information; the calibration file information is information related to the ECU to be calibrated obtained by the cloud platform according to the calibration instruction information sent by the mobile terminal; the calibration instruction information is information sent by the calibration personnel to the cloud platform through the mobile terminal.

2. The vehicle off-line calibration method based on an in-vehicle terminal according to claim 1, characterized in that, The calibration process for the vehicle to be calibrated based on the received calibration file information is divided into multiple threads, including a calibration file acquisition thread, a calibration file parsing thread, and a calibration process control thread. The calibration file acquisition thread is used to obtain the calibration file from the cloud platform based on the ECU information to be calibrated and its calibration file address in the calibration file information. The calibration file parsing thread is used to parse the calibration file obtained by the calibration file acquisition thread to obtain calibration data for calibrating the ECU to be calibrated. The calibration process control thread is used to calibrate the ECU to be calibrated based on the calibration data.

3. The vehicle off-line calibration method based on an on-board terminal according to claim 2, characterized in that, The methods for obtaining the calibration file from the cloud platform based on the ECU information to be calibrated and its calibration file address in the calibration file information include: if obtaining the calibration file from the cloud platform fails, the calibration file is obtained again until the number of times the calibration file is obtained fails reaches a preset first set number, then the ECU corresponding to the calibration file is determined to have failed calibration; if obtaining the calibration file from the cloud platform is successful, a calibration file parsing thread is created and triggered when no ECU is being calibrated and the calibration file parsing thread does not exist.

4. The vehicle off-line calibration method based on an on-board terminal according to claim 2, characterized in that, The method for parsing the calibration file obtained by the calibration file acquisition thread includes: after parsing the calibration file, firstly placing the parsed calibration data into a structure corresponding to the ECU to be calibrated; then performing a validity check on the calibration data in the structure. If the structure passes the validity check, the calibration data in the structure is sent to the calibration process control thread; otherwise, the structure is cleared.

5. The vehicle off-line calibration method based on an on-board terminal according to claim 2, characterized in that, The calibration method for the ECU to be calibrated according to the calibration data includes: calibrating the ECU according to the calibration data and the calibration method supported by the corresponding ECU to successfully write the calibration parameters in the calibration data into the corresponding ECU; if there is a step that fails to execute during the calibration process, the step is re-executed until the number of times the step fails to execute reaches a preset second set number, then the ECU is determined to have failed to calibrate.

6. The vehicle off-line calibration method based on an in-vehicle terminal according to claim 5, characterized in that, The method of calibrating the ECU to be calibrated according to the calibration data also includes: after the calibration parameters in the calibration data are successfully written to the corresponding ECU, if the calibration parameters successfully written from the ECU are consistent with the value of the calibration parameters in the calibration information, then the calibration parameters are determined to be calibrated successfully; otherwise, the calibration parameters are determined to be calibrated unsuccessfully.

7. The vehicle off-line calibration method based on an in-vehicle terminal according to claim 5, characterized in that, The calibration data used in the ECU calibration process is the calibration data that has passed the validity check of the calibration process control thread; if the calibration data fails the validity check of the calibration process control thread, the ECU calibration corresponding to the calibration data is determined to have failed.

8. The vehicle off-line calibration method based on an in-vehicle terminal according to claim 2, characterized in that, The plurality of threads also includes a calibration service management thread; the calibration service management thread is used to: if the calibration service management thread receives a calibration start instruction issued by the cloud platform, create and trigger the calibration file acquisition thread if the calibration file acquisition thread does not exist.

9. The vehicle off-line calibration method based on an in-vehicle terminal according to claim 8, characterized in that, The calibration business management thread is also used to: if the calibration business management thread receives the calibration completion instruction sent by the calibration process control thread and detects that the calibration file corresponding to the ECU to be calibrated has been successfully downloaded, then the calibration file parsing thread is triggered until all ECUs are calibrated.

10. The vehicle off-line calibration method based on an in-vehicle terminal according to claim 1, characterized in that, After all ECUs are calibrated, the vehicle terminal uploads the calibration results of all ECUs to the cloud platform, so that the cloud platform can send the list of ECUs that failed calibration, the reasons for the failure, and the corresponding handling solutions to the mobile terminal.

11. A vehicle-mounted terminal, comprising a processor, characterized in that, The processor is used to execute a computer program to implement the steps of the vehicle off-line calibration method based on an in-vehicle terminal as described in any one of claims 1 to 10.

12. A vehicle, comprising an on-board terminal, characterized in that, The vehicle-mounted terminal is the vehicle-mounted terminal as described in claim 11.

Images