ECU measurement calibration method, device, electronic device and storage medium

Abstract

The present disclosure proposes a measurement and calibration method, device, electronic device and storage medium of an ECU, which relates to the field of measurement and calibration technology. The method comprises: sending a first CAN message to an electronic control unit ECU, wherein the first CAN message is a CAN message that can be filtered by the ECU; in response to receiving a response message returned by the ECU for the first CAN message, determining the historical state of the ECU; and measuring or calibrating the ECU based on the historical state. Thus, the ECU can be measured or calibrated in time after the ECU resumes connection, and the data of the ECU can be obtained in time within a short time after the ECU resumes connection, with a lower probability of error and better stability.

Description

Technical Field

[0001] The present disclosure relates to the field of measurement and calibration technology, and in particular to a measurement and calibration method, device, electronic device and storage medium for an ECU. Background Art

[0002] After being awakened, the Electronic Control Unit (ECU) sometimes needs to execute some functions immediately, such as the welcome light function, which starts running about 1 second after the ECU is awakened.

[0003] In the related art, when CANoe measurement and calibration software is usually used to measure the ECU, after the ECU is awakened, the CANoe measurement and calibration software will resend the messages that were not received during the ECU's sleep period. The ECU needs to process them, which may make it impossible to establish data collection for the ECU for a long time. Summary of the invention

[0004] The present application proposes an ECU measurement and calibration method, device, electronic device and storage medium, aiming to solve one of the technical problems in the related art at least to a certain extent.

[0005] The first embodiment of the present application provides a measurement and calibration method for an ECU, including:

[0006] Sending a first CAN message to an electronic control unit ECU, wherein the first CAN message is a CAN message that can be filtered by the ECU;

[0007] In response to receiving a response message returned by the ECU in response to the first CAN message, determining a historical state of the ECU;

[0008] Based on the historical status, the ECU is measured or calibrated.

[0009] The second aspect of the present application provides a measurement and calibration device for an ECU, including:

[0010] A sending module, used for sending a first CAN message to an electronic control unit ECU, wherein the first CAN message is a CAN message that can be filtered by the ECU;

[0011] a determination module, configured to determine a historical state of the ECU in response to receiving a response message returned by the ECU in response to the first CAN message;

[0012] A measurement and calibration module is used to measure or calibrate the ECU based on the historical state.

[0013] The third aspect embodiment of the present application proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the measurement and calibration method of the ECU of the embodiment of the present application.

[0014] The fourth aspect embodiment of the present application proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to execute the measurement and calibration method of the ECU disclosed in the embodiment of the present application.

[0015] In the disclosed embodiment, a first CAN message is first sent to an electronic control unit ECU, wherein the first CAN message is a CAN message that can be filtered by the ECU, and then in response to receiving a response message returned by the ECU for the first CAN message, the historical state of the ECU is finally determined; based on the historical state, the ECU is measured or calibrated. Thus, the ECU can be measured or calibrated in time after the ECU is restored to connection, and the data of the ECU can be obtained in time within a short time after the ECU is restored to connection, with a lower probability of error and better stability.

[0016] Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description or learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and / or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0018] Figure 1 It is a flowchart of a measurement and calibration method of an ECU provided according to the first embodiment of the present disclosure;

[0019] Figure 2 is a flow chart of a measurement and calibration method of an ECU provided according to a second embodiment of the present disclosure;

[0020] Figure 3 is a schematic diagram of a measurement and calibration device for an ECU according to an embodiment of the present disclosure;

[0021] Figure 4 It is a block diagram of an electronic device used to implement the measurement and calibration method of the ECU according to the embodiment of the present disclosure. DETAILED DESCRIPTION

[0022] Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present disclosure, and are not to be construed as limitations of the present disclosure. On the contrary, the embodiments of the present disclosure include all changes, modifications, and equivalents that fall within the spirit and connotation of the appended claims.

[0023] Related technology: When using INCA (Integrated Calibration and Application Tool) to measure ECU, when the ECU under test enters sleep mode, INCA will send a connection message to the ECU every 1 second. After the ECU replies to the connection message, INCA will first verify and download the message before starting the measurement. During the verification, the user will be asked to click whether to switch the work page. This click operation cannot be set to not execute, and the verification operation cannot be set to cancel. Since the user still needs a certain amount of time to perform the click operation, ICNA cannot immediately obtain the ECU data after the ECU wakes up from sleep mode.

[0024] When using CANoe (control area network development and testing tool) to measure ECU, when ECU is dormant, the software can be configured to send a packet of messages to ECU every 1 second to try to reconnect to ECU. The physical transmission layer of the message is CAN, and CAN messages have delays. When ECU is dormant, CAN messages sent to ECU are not received by ECU. After ECU wakes up, these messages will be automatically resent to ECU, and ECU will reply to these messages one by one. As a result, CANoe will suddenly receive a lot of messages, the timing of CANoe internal program will be disordered, and data collection cannot be established for a long time.

[0025] It should be noted that the executor of the ECU measurement and calibration method of this embodiment may be a measurement and calibration device of the ECU, which may be implemented by software and / or hardware, and which may be configured in any electronic device, such as a mobile phone, a car computer, a computer, etc., and is not limited here.

[0026] In the disclosed embodiment, the ECU measurement and calibration method will be described by taking the "ECU measurement and calibration device" as the execution subject, and no limitation is made here. The ECU measurement and calibration software is installed in the ECU measurement and calibration device.

[0027] Figure 1 FIG. 1 is a flow chart of a method for measuring and calibrating an ECU according to the first embodiment of the present disclosure. Figure 1 As shown, the method includes:

[0028] S101: Sending a first CAN message to an electronic control unit ECU, wherein the first CAN message is a CAN message that can be filtered by the ECU.

[0029] Among them, ECU (Electronic Control Unit) is an electronic control unit used to monitor, control and manage various electronic systems and functions of the vehicle. Different systems have corresponding ECUs to process the sensor data and actuator control signals related to them, such as the Engine Control Unit (ECU) and the Transmission Control Unit (TCU), which are not limited here.

[0030] The first CAN message is a CAN message that can be filtered by the ECU.

[0031] In the embodiment of the present disclosure, a filterable first CAN message may be sent to the ECU during the process of the ECU being disconnected.

[0032] Optionally, a set of filtering rules can be pre-configured in the ECU to receive specific CAN messages from the bus that are relevant to the ECU's functions, while ignoring irrelevant messages. For example, the ECU can perform identifier (ID) filtering, and configure filtering rules in the CAN controller in the ECU to only receive CAN messages with specific IDs.

[0033] It should be noted that, since the first CAN message is a CAN message that can be filtered by the ECU, it can prevent the ECU from being accidentally awakened during sleep, that is, it can prevent the ECU from further processing the message after waking up, thereby preventing the problem of being unable to establish data collection for a long time.

[0034] As a possible implementation method, the device can send a first CAN message to the ECU according to a specified period when detecting that the ECU is disconnected.

[0035] The specified period may be a time period of a certain length, such as 100ms, 10ms, or 20ms, and may be set based on actual experience and is not limited here.

[0036] The ECU may be disconnected due to a sleep state or an abnormal disconnection, which is not limited here.

[0037] Optionally, when detecting whether the ECU is disconnected, there may be multiple implementations. For example, data stream detection may be performed using a CAN bus analyzer to capture and parse messages transmitted on the CAN bus in real time. When the ECU is disconnected, its corresponding CAN message disappears from the bus. The CAN message here may be any type of message, which may be a CAN message used for measurement and calibration, or a CAN message not used for measurement and calibration.

[0038] Alternatively, an on-board diagnostic system (OBD-II) or vehicle diagnostic system may be used to monitor the communication status of each ECU and the vehicle bus system in real time. If the ECU does not send or receive messages as expected, it may be disconnected. There are many ways to detect whether the ECU is disconnected, which will not be described here.

[0039] As a possible implementation manner, a first CAN message of a non-embedded communication protocol XCP may be sent to the ECU.

[0040] Among them, the CAN message of XCP is used for XCP measurement or XCP calibration.

[0041] XCP measurement refers to reading the sensor data and controller status of the ECU in real time through the XCP protocol, and displaying or recording it in the data acquisition software for analysis and diagnosis. XCP measurement can help engineers understand the real-time operation and performance of the ECU, identify problems, and perform debugging and optimization.

[0042] Among them, XCP calibration refers to changing the parameters of the ECU, such as fuel injection amount, ignition timing, etc., through the XCP protocol to optimize engine performance and save energy and reduce consumption.

[0043] It should be noted that if the device sends XCP CAN messages, it will take a lot of time to process these messages after the ECU restores the connection. In addition, after the ECU restores the connection and sends a message to the device, it is difficult for the device to determine whether the message replied by the ECU is a CAN message sent before the connection is restored or a CAN message sent after the connection is restored.

[0044] It is understandable that sending messages on the XCP CAN path is prone to accidentally waking up the ECU. Since non-XCP CAN messages can be sent on the non-XCP CAN path, the probability of accidentally waking up the ECU can be reduced.

[0045] S102: In response to receiving a response message returned by the ECU in response to the first CAN message, determining a historical state of the ECU.

[0046] It should be noted that the filtering mechanism in the ECU does not change the basic communication mode. In the request-response mode, the sender (the device) sends a message, and the receiver (ECU) sends a response message (ack message) as confirmation after receiving it. Although the first CAN message is a message filtered by the ECU, the ECU can respond to the first CAN message in the connected state, that is, reply with a response message (ack message).

[0047] Since the ECU can respond to the message only when it is in the connected state, if the device receives the response message, it means that the ECU has restored the connection. The device can further determine the state of the ECU before the connection is restored.

[0048] The historical state may be the state of the ECU before the connection is restored, such as a measurement state or a calibration state, which is not limited here.

[0049] S103: Measure or calibrate the ECU based on the historical status.

[0050] Optionally, when the historical state is a calibration state, the calibration action on the ECU is restored.

[0051] It should be noted that when it is detected that the ECU is restored to connection, if the calibration modification is performed before the ECU is disconnected, the calibration modification is performed first, that is, the calibration action before the disconnection is restored.

[0052] Optionally, the ECU may be measured after the ECU calibration is completed.

[0053] Optionally, when the historical state is a measurement state, data of the ECU is collected for measurement.

[0054] It should be noted that after detecting that the ECU has restored the connection, if measurement was in progress before the ECU was disconnected, the measurement configuration can be executed to start collecting ECU data and analyzing the problem.

[0055] In the disclosed embodiment, a first CAN message is first sent to an electronic control unit ECU, wherein the first CAN message is a CAN message that can be filtered by the ECU, and in response to receiving a response message returned by the ECU for the first CAN message, the historical state of the ECU is determined, and the ECU is measured or calibrated based on the historical state. Thus, the ECU can be measured or calibrated in time after the ECU is restored to a connection, and the data of the ECU can be obtained in time within a short time after the ECU is restored to a connection, with a lower probability of error and better stability.

[0056] Figure 2 FIG. 1 is a flow chart of a measurement and calibration method of an ECU according to a second embodiment of the present disclosure. Figure 2 As shown, the method includes:

[0057] S201: When the connection with the ECU is established for the first time, the ECU is verified to obtain a verification result.

[0058] The verification result may be verification passed or verification failed, or verification aborted, verification abnormal, etc., which are not limited here.

[0059] Specifically, a connection with the ECU can be established through a corresponding communication protocol (such as XCP) to ensure that data can be sent and received. After that, the standard page and reference page information supported by the ECU can be obtained, and a list of standard pages and reference pages supported by the ECU can be obtained by sending a query command or instruction.

[0060] Furthermore, automatic verification can be performed, that is, verification can be performed automatically according to the acquired standard page and reference page information. The communication can be verified to be normal by sending corresponding verification commands or instructions, and the return value of the ECU can be ensured to be consistent with the expectation, which is not limited here.

[0061] It should be noted that the specific implementation method of verifying the ECU may vary depending on the type of ECU, communication protocol and hardware device. In the actual development process, appropriate adjustments and modifications need to be made according to specific circumstances, which are not limited in the embodiments of the present disclosure.

[0062] S202: If the verification result is passed, the standard page and the reference page are automatically switched.

[0063] Among them, the standard page can be a data page stored in the ECU, which contains various parameters and calibration values. These parameters and calibration values ​​are used to control the behavior of the ECU, such as engine fuel injection amount, ignition timing, sensor thresholds, etc. The standard page can be the official data page of the ECU for practical application.

[0064] The reference page can be a backup data page stored in the ECU for calibration and debugging operations. The reference page is a copy of the standard page and can be modified and edited for parameter adjustment and calibration. By modifying the values ​​in the reference page, the working mode and performance of the ECU can be changed, such as adjusting the combustion efficiency of the engine or improving the response speed of the sensor.

[0065] During the calibration process, the values ​​in the reference page can be adjusted to the expected values ​​first, and then the values ​​in the reference page can be loaded into the standard page to change the actual working parameters of the ECU. In this way, the original standard page can be kept unchanged during the calibration process to avoid problems caused by accidental modifications. At the same time, the modification of the reference page can also be undone at any time to recalibrate or restore to the original state.

[0066] S203: Sending a first CAN message to the ECU via a first CAN line connected to the ECU.

[0067] The data bus communication configuration table of the first CAN line does not include the identifier of the first CAN message.

[0068] It should be noted that there may be many CAN paths connected to the ECU, and the first CAN path may be any CAN path configured with a data bus communication configuration table.

[0069] The Data Bus Communication (DBC) configuration table is a file format used to describe and configure the CAN network, which defines the structure of CAN messages, signal properties, and other information related to CAN signals. The DBC configuration table is a configuration file created based on the DBC file format, which contains the definitions of all CAN messages, signals, and nodes used in the CAN network. These configuration tables can be used in various applications, such as automotive electronic system development, diagnostic tool development, and CAN communication network analysis.

[0070] It should be noted that for each system that uses CAN bus communication, there can be a corresponding DBC configuration table. Since the messages and signals on each CAN bus may be different, it is necessary to write a corresponding DBC configuration table for each CAN bus to ensure the correct parsing and processing of messages and signals. In addition, different devices may also need to use different versions of DBC configuration tables. When developing and debugging a CAN communication network, multiple DBC configuration tables can be written and managed according to actual conditions.

[0071] In the disclosed embodiment, the data bus communication configuration table in the first CAN path does not contain the identifier of the target CAN message, so the ECU application layer can directly filter the CAN message and does not process the CAN message, thereby avoiding affecting the normal business logic of the ECU and avoiding accidental wake-up of the ECU.

[0072] S204: In response to receiving a response message returned by the ECU in response to the first CAN message, determine a historical state of the ECU.

[0073] S205: Measure or calibrate the ECU based on the historical status.

[0074] It should be noted that the specific implementation of steps S204 and S205 can refer to the above embodiment and will not be described in detail here.

[0075] In the disclosed embodiment, first, when the connection with the ECU is established for the first time, the ECU is verified to obtain the verification result. If the verification result is that the verification is passed, the standard page and the reference page are automatically switched, and the first CAN message is sent to the ECU through the first CAN line connected to the ECU. Then, in response to receiving the response message returned by the ECU for the first CAN message, the historical state of the ECU is determined, and finally, based on the historical state, the ECU is measured or calibrated. In this way, after detecting that the ECU is awake, the verification link can be skipped to avoid time consumption due to verification. It is only necessary to verify when the connection with the ECU is established for the first time, and the ECU can be measured or calibrated in time after the ECU resumes the connection. The data of the ECU can be obtained in time within a short time after the ECU resumes the connection, and the error probability is low and the stability is better.

[0076] Figure 3 FIG. 1 is a schematic diagram of a measurement and calibration device for an ECU according to another embodiment of the present disclosure. Figure 3 As shown, the measurement and calibration device 300 of the ECU includes:

[0077] The sending module 310 is used to send a first CAN message to an electronic control unit ECU, wherein the first CAN message is a CAN message that can be filtered by the ECU;

[0078] A determination module 320, configured to determine a historical state of the ECU in response to receiving a response message returned by the ECU in response to the first CAN message;

[0079] The measurement and calibration module 330 is used to measure or calibrate the ECU based on the historical state.

[0080] Optionally, the sending module 310 is specifically configured to:

[0081] In response to detecting that the ECU is disconnected, a first CAN message is sent to the ECU according to a specified period.

[0082] Optionally, the sending module 310 is specifically configured to:

[0083] A first CAN message of a non-embedded communication protocol XCP is sent to the ECU.

[0084] Optionally, the sending module 310 is specifically configured to:

[0085] sending a first CAN message to the ECU via a first CAN line connected to the ECU,

[0086] The data bus communication configuration table of the first CAN path does not include the identifier of the first CAN message.

[0087] Optionally, the sending module 310 is further configured to:

[0088] When establishing a connection with the ECU for the first time, verifying the ECU to obtain a verification result;

[0089] If the verification result is that the verification is passed, the standard page and the reference page are automatically switched.

[0090] Optionally, the measurement calibration module 330 includes:

[0091] A recovery unit, used for recovering the calibration action of the ECU when the historical state is a calibration state;

[0092] After the ECU calibration is completed, the ECU is measured.

[0093] Optionally, the measurement calibration module 330 is specifically used for:

[0094] When the historical state is a measurement state, data of the ECU is collected for measurement.

[0095] In the disclosed embodiment, a first CAN message is first sent to an electronic control unit ECU, wherein the first CAN message is a CAN message that can be filtered by the ECU, and in response to receiving a response message returned by the ECU for the first CAN message, the historical state of the ECU is determined, and the ECU is measured or calibrated based on the historical state. Thus, the ECU can be measured or calibrated in time after the ECU is restored to a connection, and the data of the ECU can be obtained in time within a short time after the ECU is restored to a connection, with a lower probability of error and better stability.

[0096] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

[0097] Figure 4 A block diagram of an exemplary computer device suitable for implementing embodiments of the present application is shown. Figure 4 The computer device 12 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0098] like Figure 4 As shown, the computer device 12 is in the form of a general-purpose computing device. The components of the computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that connects various system components (including the system memory 28 and the processing unit 16).

[0099] The bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnection (PCI) bus.

[0100] The computer device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the computer device 12, including volatile and non-volatile media, removable and non-removable media.

[0101] The memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The computer device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 4 Not shown, often called a "hard drive").

[0102] although Figure 4 Not shown, a disk drive for reading and writing a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk (e.g., a compact disc read only memory (CD-ROM), a digital versatile disc read only memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present application.

[0103] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0104] The computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the computer device 12, and / or any device that enables the computer device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed via an input / output (I / O) interface 22. In addition, the computer device 12 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 20. As shown, the network adapter 20 communicates with other modules of the computer device 12 via a bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the computer device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0105] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing the measurement and calibration method of the ECU mentioned in the above embodiment.

[0106] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the application disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0107] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

[0108] It should be noted that, in the description of this application, the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of this application, unless otherwise specified, the meaning of "plurality" is two or more.

[0109] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0110] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0111] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0112] In addition, each functional unit in each embodiment of the present application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The above-mentioned storage medium can be a read-only memory, a disk or an optical disk, etc.

[0113] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0114] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A measurement and calibration method for an ECU, characterized in that: include: During the process of disconnecting the ECU, a first CAN message is sent to an electronic control unit ECU, wherein the first CAN message is a non-embedded communication protocol XCP message that can be filtered by the ECU; In response to receiving a response message returned by the ECU in response to the first CAN message, determining that the ECU has restored the connection, and determining a historical state of the ECU; Based on the historical status, the ECU is measured or calibrated.

2. The method according to claim 1, characterized in that The sending of a first CAN message to an electronic control unit ECU comprises: In response to detecting that the ECU is disconnected, a first CAN message is sent to the ECU according to a specified period.

3. The method according to claim 1, characterized in that The sending of a first CAN message to an electronic control unit ECU comprises: sending a first CAN message to the ECU via a first CAN line connected to the ECU, The data bus communication configuration table of the first CAN path does not include the identifier of the first CAN message.

4. The method according to claim 2, characterized in that: Before the response to detecting that the ECU is disconnected, the method further includes: When establishing a connection with the ECU for the first time, verifying the ECU to obtain a verification result; If the verification result is that the verification is passed, the standard page and the reference page are automatically switched.

5. The method according to claim 1, characterized in that The measuring or calibrating the ECU based on the historical state includes: When the historical state is a calibration state, resuming the calibration action on the ECU; After the ECU calibration is completed, the ECU is measured.

6. The method according to claim 1, characterized in that The measuring or calibrating the ECU based on the historical state includes: When the historical state is a measurement state, data of the ECU is collected for measurement.

7. A measurement and calibration device for an ECU, characterized in that: include: A sending module, used for sending a first CAN message to an electronic control unit ECU during the process of disconnecting the ECU, wherein the first CAN message is a non-embedded communication protocol XCP message that can be filtered by the ECU; a determination module, configured to determine that the ECU has restored the connection in response to receiving a response message returned by the ECU in response to the first CAN message, and to determine a historical state of the ECU; A measurement and calibration module is used to measure or calibrate the ECU based on the historical state.

8. An electronic device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 6.

9. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-6.

Images