CN111781909A

CN111781909A - Control method based on CCP or XCP protocol

Info

Publication number: CN111781909A
Application number: CN202010299665.2A
Authority: CN
Inventors: 曹翔
Original assignee: Ningbo Purui Junsheng Automotive Electronics Co ltd
Current assignee: Ningbo Purui Junsheng Automotive Electronics Co ltd
Priority date: 2020-04-16
Filing date: 2020-04-16
Publication date: 2020-10-16

Abstract

The invention provides a method for calibrating an Electronic Control Unit (ECU) based on a CCP (common control processor) or XCP (XCP protocol), which is characterized by comprising the following steps: invoking a diagnostic engineering tool to unlock the target ECU; activating and maintaining CAN communication between a host and a target unit based on CCP or XCP protocol by sending a diagnosis message; analyzing the calibration parameter file to obtain information of calibration parameters of the ECU; and acquiring and/or setting the value of the calibration parameter of the target ECU based on the acquired information of the calibration parameter. The invention also relates to an ECU calibration system and an electronic device and a computer readable medium capable of implementing the calibration method according to the invention. The method and the system can still facilitate the operation under the condition of ensuring the safety, and realize a realization scheme for the decryption, CCP analysis, search and setting of the set target equipment with extremely high integration level.

Description

Control method based on CCP or XCP protocol

Technical Field

The invention relates to the field of automobiles, in particular to communication and control of an electronic control device of an automobile.

Background

With the development of technology, Electronic Control Units (ECUs) are widely used in current automobiles for controlling various components of the vehicles. In order to solve the problem of communication among a large number of electronic control devices in an automobile and reduce the number of signal lines which are increased continuously, the automobile adopts a Controller Area Network (CAN) bus to realize the communication and control of a vehicle-mounted electronic control system.

For this purpose, the automation and measurement system standards association (ASAM) proposes a CAN-based ECU Calibration Protocol, namely the CCP Protocol (CAN Calibration Protocol).

In the current art, there are numerous schemes for calibrating the ECU of a vehicle using the CCP protocol.

In CN110166337A, a calibration communication method based on CCP protocol is proposed, which uses CANape as an upper computer, modifies RAM data to implement modification of online calibration parameters, monitors CAN signals at the same time, sees whether the CAN signals reach a target value after the calibration parameters are modified on line, and downloads the modified calibration parameters into an ECU EEPROM after the target value is reached, thereby achieving the function of online calibration. However, the use of CANape as a specific tool software limits the broad application of the calibration communication method, and in particular cannot be used in combination with a widely applicable bus development tool.

In addition, in some schemes, calibration based on the CCP protocol often requires a bus analysis tool to activate CCP connection by sending a CCP key through a vehicle diagnostic function, and then reading related calibration parameter data through a calibration tool. However, as the degree of vehicle informatization is improved, the security level of the automobile network is continuously upgraded, and the fixed simple method for activating the CCP by using the CCP secret key cannot meet the requirement of network security. In some solutions it is also proposed to perform CCP activation with software assistance of the customer, which leads to a complication of the process of reading calibration data.

Further, the parameters or attributes of the data used by the ECU program are described by an A2L format file, including but not limited to parameter display name, length, physical unit, translation relationship, and address mapped to the ECU.

In CN108415406A, a CCP calibration system of BCU based on LabVIEW is provided, which includes an initialization PCAN module, where the initialization PCAN module is respectively connected to an A2L file reading module, a calibration amount searching module, a DAQ _ List initialization module, a setting module, an initial value restoring module, a calibration amount reading module, and a stopping module in communication, and the A2L file reading module, the calibration amount searching module, the DAQ _ List initialization module, the setting module, the initial value restoring module, the calibration amount reading module, and the stopping module are all connected to a PCAN anti-initialization module in communication. However, the reading of the A2L file in the CCP calibration system is not automated. Methods for processing variables in A2L documents and methods for producing documents are proposed in CN110262289A and CN110362361A, respectively, and their reading and processing are not performed in an automated manner.

Accordingly, it is desirable to provide a calibration control system and method that is easy to operate while ensuring safety.

This background is only for convenience in understanding the relevant art in this field and is not to be taken as an admission of prior art.

Disclosure of Invention

The embodiment of the invention aims to provide a calibration control system and a calibration control method which can still be conveniently operated under the condition of ensuring the safety.

Advantageously, but not by way of limitation, embodiments of the present invention also contemplate that the calibration control system and method may have broad applicability and/or have a higher degree of integration.

Advantageously, but not by way of limitation, embodiments of the present invention also desirably increase the degree of automation of calibration control systems and methods.

In one aspect, a method for calibrating an Electronic Control Unit (ECU) based on a CCP or XCP protocol is provided, including:

invoking a diagnostic engineering tool to unlock the target ECU;

activating and maintaining CAN communication between a host and a target unit based on CCP or XCP protocol by sending a diagnosis message;

analyzing the calibration parameter file to obtain information of calibration parameters of the ECU;

and acquiring and/or setting the value of the calibration parameter of the target ECU based on the acquired information of the calibration parameter.

In the embodiment, an implementation scheme for decryption, CCP analysis, search and setting of the set target equipment is realized with extremely high integration level, and meanwhile, the safety of calibration operation can be ensured.

In one embodiment, the above described scheme may be implemented in an ad hoc or retrofitted software platform or application tool. According to a preferred embodiment, the Electronic Control Unit (ECU) calibration method can be implemented in various conventionally used bus development tools, such as in CANoe. In some embodiments, this may be accomplished by modifying or invoking a CANoe or other bus development tool.

According to one embodiment, parsing the calibration parameter file into a parsed A2L file includes reading at least some of physical memory addresses, lengths, physical units, and conversion formulas of the calibration parameters within the A2L file and storing them in the form of a structure.

According to one embodiment, the obtaining of the calibration parameters of the target ECU comprises:

responding to the received calibration parameters, inquiring the structural body to obtain the physical memory address and the conversion formula of the received calibration parameters;

loading the physical address and the conversion formula of the received calibration parameter in a diagnosis message to inquire the value of the calibration parameter from a target ECU;

and extracting and analyzing the communication message content replied by the target ECU, obtaining the actual value of the received calibration parameter and updating the value of the received calibration parameter.

According to one embodiment, the setting of the calibration parameters of the target ECU comprises:

querying the structure to determine whether the received calibration parameters are settable in response to the received calibration parameters and predetermined values for the calibration parameters;

if the calibration parameter can be set, loading the physical address of the received calibration parameter and the preset value of the calibration parameter in a diagnostic message to send to a target ECU;

and setting the value of the corresponding calibration parameter of the target ECU to be the preset value.

According to one embodiment, the method is arranged to be carried out in an automated manner, comprising: invoking an automated test script to perform the unlocking, activating and maintaining, parsing, obtaining, and/or setting steps.

In the described embodiment, the requirements for highly automated testing are fulfilled.

In one embodiment, an ECU calibration system based on CCP or XCP protocol is provided, which includes: a host; at least one target ECU, wherein each target ECU comprises a respective CAN communication module with CCP or XCP protocol; and the CAN bus analysis tool is connected with the host and the CAN communication module, wherein the host is provided with a CANoe and a diagnosis engineering tool.

According to one embodiment, the host is configured to invoke the diagnostic engineering tool to unlock the CAN communication module.

According to one embodiment, the host is configured to send a diagnostic message by means of the diagnostic engineering tool to activate and maintain communication between the host and the CAN communication module via the CAN bus analysis tool.

According to one embodiment, the host is configured to parse the at least one calibration parameter file by means of the CANoe to obtain information of the calibration parameters of the at least one target ECU.

According to one embodiment, the host is configured to obtain and/or set a value of a calibration parameter of the at least one target ECU by means of CANoe based on the obtained information of the calibration parameter.

According to one embodiment, the host further comprises an operator interface integrated in or communicatively connected to the CANoe, the operator interface being configured to receive user input of calibration parameters and predetermined values thereof and/or to display calibration parameters and actual values thereof read from the at least one target ECU.

According to one embodiment, the host further comprises an automated test script reading interface integrated in or communicatively connected to the CANoe, the automated test script reading interface configured to read an automated test script to automatically unlock the CAN communication module, activate and maintain the communication, obtain and/or set calibration parameters.

In one aspect, an electronic device is provided, which includes a processor and a memory communicatively coupled to the processor, where the memory stores instructions executable by the processor, and the processor is configured to execute the instructions in the memory to implement the method according to the embodiment of the present invention.

In one aspect, a computer-readable storage medium is provided that stores computer-executable instructions configured to perform a method according to an embodiment of the invention when executed.

In one embodiment, the computer readable storage medium stores a CANoe software tool that incorporates the functionality of embodiments of the present invention.

Preferred features of the invention are described in part below and in part will be apparent from the description.

Drawings

The embodiments herein are described in detail below with reference to the attached drawing figures, wherein:

FIG. 1 shows a flow chart of an Electronic Control Unit (ECU) calibration method according to an embodiment of the present invention;

FIG. 2 shows a flowchart of the substeps of obtaining calibration parameters for the target ECU, according to an embodiment of the present invention;

FIG. 3 shows a flowchart of substeps of setting calibration parameters for the target ECU, in accordance with an embodiment of the present invention;

FIG. 4 shows a schematic diagram of a system according to an embodiment of the invention;

fig. 5 shows a schematic view of an electronic device according to an embodiment of the invention.

In the drawings, the same or similar reference numerals will be used to refer to the same or similar features.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the following detailed description and accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.

Definition of

In this context, automobiles have the conventional meaning in the art. The present disclosure is not intended to limit the types of vehicles, driving types, applications, etc. to which embodiments of the present disclosure may be applied, such as passenger cars, commercial vehicles, fuel-powered vehicles, electric vehicles, autonomous vehicles, etc. Herein, an automobile and a vehicle may be used interchangeably.

In this context, an Electronic Control Unit (ECU), or Electronic Control Unit, has the conventional meaning known in the art. According to the Open systems architecture (AUTomotive architecture), an ECU means a microcontroller and peripheral along with responsive software for control of a vehicle or its components. For automobiles, there may be a large number of ECUs operating within the vehicle, including but not limited to ABS (anti-lock braking system), ACC (adaptive cruise control), BMS (battery management system), EMS (engine management system), autonomous driving controller, VCU (vehicle control unit), and the like. The specific type of ECU to which embodiments of the present invention are applicable is not intended to be limited herein.

Herein, a Controller Area Network (CAN) has a conventional meaning known in the art, and is an ISO internationally standardized serial communication protocol.

Herein, ccp (CAN Calibration protocol) has a conventional meaning known in the art, and proposes a CAN-based ECU Calibration protocol for the automation and measurement system standards association (ASAM).

In this context, xcp (universal Measurement and Calibration protocol) has a conventional meaning known in the art, and proposes a CAN-based ECU Calibration protocol for the automation and Measurement system standards association (ASAM). The XCP protocol CAN further run on various transport layers (CAN, Ethernet, FlexRay, SCI, SPI, USB) based on CCP. In this context, all embodiments described for the CCP protocol may be adapted within the scope of the present invention to obtain new embodiments for the XCP protocol, unless otherwise specified; and vice versa.

The CANoe, which may also be referred to herein as CAN environment, has the conventional meaning known in the art, and is a bus development environment software tool from Vector, germany, for modeling, simulating, developing, and analyzing the integrity of individual ECUs or the entire ECU network. CANoe supports the entire process from planning to testing at the system level.

The A2L file is herein a descriptive format of internal ECU variables for measurement and calibration purposes defined by the ASAM MCD-2 MC standard and has conventional meaning known in the art.

In an embodiment of the present invention, to address the deficiencies in the prior art, a method is provided for controlling, and more particularly calibrating, an ECU based on a bus analysis tool, such as the CCP or XCP protocol of CANoe.

In one embodiment, as shown in FIG. 1, an Electronic Control Unit (ECU) calibration method based on the CCP or XCP protocol is provided. In a specific embodiment, the above described scheme is implemented in a proprietary or retrofit software platform or application tool. According to a preferred embodiment, the Electronic Control Unit (ECU) calibration method can be implemented in various conventionally used bus development tools, such as in CANoe. In some embodiments, this may be accomplished by modifying or invoking a CANoe or other bus development tool.

As shown in fig. 1, the method comprises the steps of:

s101: a Diagnostic Engineering Tool (Diagnostic Engineering Tool) is invoked to unlock the target ECU.

S102: CAN communication between a host and a target unit based on CCP or XCP protocols is activated and maintained by sending a diagnostic message.

S103: and analyzing the calibration parameter file to acquire the information of the calibration parameters of the ECU.

S104: and acquiring and/or setting the value of the calibration parameter of the target ECU based on the acquired information of the calibration parameter.

According to one embodiment, the calibration parameter file is an A2L file.

In one embodiment, parsing the A2L file includes reading at least some of the physical memory addresses, lengths, physical units, and conversion formulas of the calibration parameters within the A2L file and storing in the form of a structure.

In some embodiments, parsing the A2L file includes reading the contents of each line of the A2L file through a script, and identifying the type of the contents of the line by querying a specific string, obtaining the address of the specific string, locating the relevant parameter contents including but not limited to physical memory address, length, physical unit, conversion formula, etc., and structuring the parameter contents for storage. In some embodiments, parsing the A2L file includes extracting all of the target parameters in the file and creating a structure for each target parameter.

In the embodiment shown with reference to fig. 2, obtaining the calibration parameters of the target ECU comprises:

and S201, responding to the received calibration parameters, inquiring the structural body to obtain the physical memory address and the conversion formula of the received calibration parameters.

S202: and loading the physical address of the received calibration parameter in a diagnosis message to inquire the value of the calibration parameter to a target ECU.

S203: and extracting and analyzing the communication message content replied by the target ECU, obtaining the actual value of the received calibration parameter and updating the value of the received calibration parameter.

In the embodiment shown with reference to fig. 3, setting the calibration parameters of the target ECU includes:

s301: in response to the received calibration parameters and predetermined values for the calibration parameters, the structure is queried to determine whether the received calibration parameters are settable.

S302: and if the calibration parameter can be set, loading the physical address of the received calibration parameter and the preset value of the calibration parameter in a diagnostic message to send to the target ECU.

S303: and setting the value of the corresponding calibration parameter of the target ECU to be the preset value.

In some embodiments, obtaining and/or setting values for calibration parameters of the target ECU may be performed manually or automatically.

In some embodiments, which are manually obtained and/or set, the received calibration parameters and/or predetermined values are input by a user, for example, in an operation interface. More specifically, the obtaining of the calibration parameters of the target ECU includes: a target parameter query structure body input by a user in an operation interface to obtain a physical address and a conversion formula of a target parameter; loading the physical address in a communication message and inquiring the target unit; and extracting and analyzing the content of the communication message replied by the target unit, obtaining the actual value of the target parameter, and updating the (actual) value of the calibration parameter in the operation interface in real time.

In some embodiments, which are manually obtained and/or set, the search for the parameters can be achieved by searching for all the parameters containing the keywords through the keywords input by the user. In some embodiments, the operation interface supports the functions of reading or inputting multiple, for example, 20 calibration parameter data and setting calibration parameters at the same time in real time. In some embodiments, a user-desired queue of target parameters can be imported and exported as a configuration file. The problems of poor operability, low integration level and low safety are solved.

According to one embodiment, the method is arranged to be carried out in an automated manner, comprising: invoking an automated test script to perform the unlocking, activating and maintaining, parsing, obtaining, and/or setting steps. This fulfills the requirement of highly automated testing.

In some embodiments, the received calibration parameters and/or predetermined values are automatically read by invoking an automated test script.

The invention can also provide a function interface for reading and setting the target parameters, and solves the defect that the CANoe-based automatic script cannot read and set the target parameters.

In an embodiment of automatically setting target calibration parameters, the calibration method includes the following specific steps:

the Diagnostic engineering tool (Diagnostic engineering tool) is invoked to activate and initiate CCP communications by calling an activation function, such as Active _ CCP (char DiagnodeName [ ], char DETPath [ ]).

The A2L file is parsed by calling a parse A2L file function, such as A2l _ Read (char A2LPAth [ ]).

A target calibration parameter, such as the Data of CCP _ name1, is obtained by calling a Read calibration parameter function, such as Read _ CCP _ Data (char _ CCP _ name [ ]).

The settable attribute of the target calibration parameter, such as ccp _ name1, is determined by calling a Set determination function, such as Set _ ccp _ Switch (char _ ccp _ name [ ], int ext _ control).

A target calibration parameter, such as the value of ccp _ name1 or data, is Set to data by calling a calibration parameter setting function, such as Set _ ccp _ data (char _ ccp _ name [ ], float data).

Optionally, the method may be implemented based on an automated test platform developed by CAPL.

Referring to FIG. 4, an embodiment of an ECU calibration system 400 based on the CCP or XCP protocol is shown and includes: a host 410; at least one target ECU420 (also sometimes referred to as a slave), 3 as shown, each target ECU420 including a respective CAN communication module 422 having a CCP or XCP protocol; and a CAN bus analysis tool 430 connecting the host and the CAN communication module, wherein the host is installed with a CANoe and a Diagnostic engineering tool (Diagnostic engineering tool). The ECU may be those described above, or various ECUs in the vehicle, such as an ECU for controlling a door lock, etc., and the present invention is not limited to the kind of ECU.

In the system of this embodiment, by using the ECU calibration system 400 of CANeo, a highly integrated platform can be provided, and the calibration parameters of the terminal ECU can be acquired or set (changed) while modeling, simulation, development and analysis are realized by a common bus development environment software tool.

In some embodiments, the host comprises a PC. In some embodiments, a host 410, such as a PC, is connected to a CAN bus analysis tool 430, which is connected to a target ECU420 using a wiring harness 450, via a cable 440, such as a USB cable.

In some embodiments, the CAN communication module 422 may operate from a dc power supply voltage.

According to one embodiment, the host further comprises an automated test script reading interface integrated in or communicatively connected to the CANoe, the automated test script reading interface configured to read an automated test script to automatically unlock the CAN communication module, activate and maintain the communication, obtain and/or set calibration parameters. In some embodiments, a function interface for automatic test script calls, such as those described above, may be integrated in the CANoe software tool.

As shown in fig. 5, an embodiment of an electronic device 500 is provided, including a processor (processor) 510 and memory 530, and may also include a communication interface 520 and bus 540. The processor 510, the communication interface 520, and the memory 530 may communicate with each other via a bus 540. Communication interface 520 may be used for information transfer. Processor 510 may invoke logic instructions in memory 530. The memory stores instructions executable by the processor, and the processor is configured to execute the instructions in the memory to implement the method according to embodiments of the invention.

Furthermore, the logic instructions in the memory 530 may be implemented in the form of software functional units and stored in a computer readable storage medium when the software functional units are sold or used as independent products.

The memory 530 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal device, and the like. Further, memory 530 may include high speed random access memory, and may also include non-volatile memory.

The computer-readable storage medium described above may be a transitory computer-readable storage medium or a non-transitory computer-readable storage medium.

The technical solution of the embodiments of the present disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes one or more instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method of the embodiments of the present disclosure. And the aforementioned storage medium may be a non-transitory storage medium comprising: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes, and may also be a transient storage medium.

The above description and drawings sufficiently illustrate embodiments of the disclosure to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. The examples merely typify possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and features of some embodiments may be included in or substituted for those of others. The scope of the disclosed embodiments includes the full ambit of the claims, as well as all available equivalents of the claims. As used in this application, although the terms "first," "second," etc. may be used in this application to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, unless the meaning of the description changes, so long as all occurrences of the "first element" are renamed consistently and all occurrences of the "second element" are renamed consistently. The first and second elements are both elements, but may not be the same element. Furthermore, the words used in the specification are words of description only and are not intended to limit the claims. As used in the description of the embodiments and the claims, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Similarly, the term "and/or" as used in this application is meant to encompass any and all possible combinations of one or more of the associated listed. Furthermore, the terms "comprises," "comprising," or any other variation thereof, when used in this application, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Without further limitation, an element defined by the phrase "comprising an …" does not exclude the presence of other like elements in a process, method or apparatus that comprises the element. In this document, each embodiment may be described with emphasis on differences from other embodiments, and the same and similar parts between the respective embodiments may be referred to each other. For methods, products, etc. of the embodiment disclosures, reference may be made to the description of the method section for relevance if it corresponds to the method section of the embodiment disclosure.

Those of skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software may depend upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments. It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments disclosed herein, the disclosed methods, products (including but not limited to devices, apparatuses, etc.) may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit may be merely a division of a logical function, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form. Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to implement the present embodiment. In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. In the description corresponding to the flowcharts and block diagrams in the figures, operations or steps corresponding to different blocks may also occur in different orders than disclosed in the description, and sometimes there is no specific order between the different operations or steps. For example, two sequential operations or steps may in fact be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. Each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Claims

1. An Electronic Control Unit (ECU) calibration method based on CCP or XCP protocol, comprising:

invoking a diagnostic engineering tool to unlock the target ECU;

2. The calibration method according to claim 1, wherein parsing the calibration parameter file into a parsed A2L file comprises reading at least some of physical memory addresses, lengths, physical units and conversion formulas of the calibration parameters in the A2L file and storing the same in the form of a structure.

3. The calibration method according to claim 2, wherein the obtaining calibration parameters of the target ECU comprises:

4. The calibration method according to claim 2 or 3, wherein the setting of calibration parameters of the target ECU comprises:

5. A calibration method according to any one of claims 1 to 4, wherein the method is arranged to be carried out in an automated manner, comprising:

invoking an automated test script to perform the unlocking, activating and maintaining, parsing, obtaining, and/or setting steps.

6. An ECU calibration system based on CCP or XCP protocol, comprising: a host; at least one target ECU, wherein each target ECU comprises a respective CAN communication module with CCP or XCP protocol; the CAN bus analysis tool is connected with the host and the CAN communication module, wherein the host is provided with a CANoe and a diagnosis engineering tool;

wherein the host is configured to invoke the diagnostic engineering tool to unlock the CAN communication module;

wherein the host is configured to send a diagnostic message by means of the diagnostic engineering tool to activate and maintain communication between the host and the CAN communication module via the CAN bus analysis tool;

the host is configured to analyze at least one calibration parameter file by means of CANoe to acquire information of calibration parameters of at least one target ECU;

wherein the host is configured to obtain and/or set a value of a calibration parameter of the at least one target ECU by means of the CANoe based on the obtained information of the calibration parameter.

7. The ECU calibration system according to claim 6, wherein the host further comprises an operation interface integrated in or communicatively connected with the CANoe, the operation interface being configured to receive user input of calibration parameters and predetermined values thereof and/or display calibration parameters and actual values thereof read from the at least one target ECU.

8. The ECU calibration system according to claim 6 or 7, wherein the host further comprises an automated test script reading interface integrated in or communicatively connected to a CANoe, the automated test script reading interface configured to read an automated test script to automatically unlock the CAN communication module, activate and maintain the communication, obtain and/or set calibration parameters.

9. An electronic device comprising a processor and a memory communicatively coupled to the processor, the memory storing instructions executable by the processor, the processor configured to execute the instructions in the memory to perform the method of any of claims 1 to 5.

10. A computer-readable storage medium having stored thereon computer-executable instructions configured, when executed, to implement the method of any one of claims 1 to 5.