A diagnostic data management method and apparatus for an electronic control unit

Abstract

The application discloses a kind of electronic control unit's diagnosis data management method, device, the electronic control unit's diagnosis data management method includes: diagnosis data is positioned to preset calibration area by data locator, defined as calibration quantity;Configuration lower computer and the communication connection of upper computer calibration tool;Calibration quantity is calibrated, and calibration quantity format file is obtained;According to the calibration quantity format file, the HEX file of the lower computer is updated and saved.The application can be in the process of vehicle type function development iteration, diagnosis data is positioned to calibration area by data locator, diagnosis data is defined as non-volatile data, and then the parameter variation of diagnosis data can be managed in development process.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle electronic control, in particular to a diagnosis data management method of an electronic control unit and a diagnosis data management device of an electronic control unit. BACKGROUND

[0002] In recent years, with the rapid development of intelligent and networked vehicles, the number of electronic control units (ECUs), the core of vehicle electronic control systems in a vehicle, has increased exponentially. In the actual system development process, the complexity of the control algorithms and parameters inside the ECU has also increased, and hundreds of parameters and signal quantities need to be effectively controlled and adjusted during ECU operation. The diagnosis system is becoming increasingly complex. Once the vehicle is assembled, it is not easy to know the various information hidden in the vehicle body. The diagnosis system, as the name implies, diagnoses the faults of the sensors and actuators of the control system. The fault reason can be read from the air conditioning ECU using a diagnostic instrument, so that maintenance personnel can accurately solve the fault. The application of diagnosis includes: reading ECU fault codes in after-sales service, accurately positioning faults, and saving maintenance time; before the vehicle is delivered, encoding, rewriting parameters, and terminal element detection are performed on different configurations of vehicle models; and ECU software is updated during the development stage.

[0003] Under the new architecture of current intelligent vehicles, the development and iteration of the diagnosis related module in the version function are gradually developed from the initial bottom software implementation basic module, the independent controller stage of the application developer completing the application software function, to the last mule test stage of the completed vehicle function development. During this process, the diagnosis function is gradually developed with version iteration, and some diagnosis functions are not perfect during the development process, such as the communication of the diagnosis function, the positioning, storage, and copying of the diagnosis data, and the like. Professional developers also need to use the diagnosis module in the iteration process of vehicle function development to verify the stability of their functions, which is a pain point of the current prior art. SUMMARY

[0004] The purpose of the present application is to provide a diagnosis data management method of an electronic control unit and a diagnosis data management device of an electronic control unit to solve at least one of the above technical problems.

[0005] The present application provides the following solutions:

[0006] A diagnosis data management method of an electronic control unit, comprising:

[0007] Positioning the diagnosis data to a preset calibration area through a data locator, defined as a calibration quantity;

[0008] Configuring a communication connection between the lower computer and the upper computer calibration tool;

[0009] The calibration quantity is calibrated to obtain a calibration quantity format file;

[0010] The HEX file of the lower computer is updated according to the calibration quantity format file and saved.

[0011] Optionally, the communication connection between the lower computer and the upper computer calibration tool comprises:

[0012] The source code file of the lower computer is compiled to obtain an executable file of the lower computer;

[0013] The executable file is burned into the lower computer;

[0014] The lower computer is connected with a power supply of a power supply;

[0015] The calibration tool is connected with the lower computer through a calibration CAN route bundle, wherein,

[0016] The calibration tool is configured with a connection channel connected with the lower computer.

[0017] Optionally, the communication connection between the lower computer and the upper computer calibration tool further comprises:

[0018] The communication connection between the calibration tool and the lower computer is tested through the connection channel.

[0019] Optionally, before the calibration quantity is calibrated to obtain a calibration quantity format file, the method further comprises:

[0020] An ELF file of the lower computer is obtained;

[0021] The ELF file of the lower computer is added to a calibration tool database.

[0022] Optionally, the calibration quantity is calibrated to obtain a calibration quantity format file, comprising:

[0023] Calibration quantity and calibration quantity address information are obtained from the calibration tool database;

[0024] The calibration quantity and calibration quantity address information are added to an A2L file of the calibration tool;

[0025] The calibration quantity is calibrated by using the calibration tool to obtain a calibration quantity format file.

[0026] Optionally, the calibration quantity is calibrated by using the calibration tool to obtain a calibration quantity format file, comprising:

[0027] The calibration quantity is calibrated to obtain a current calibration quantity value;

[0028] acquiring address information of the calibration quantity from the A2L file;

[0029] sending a message to the lower machine, the message including the address information of the calibration quantity;

[0030] sending a current calibration quantity value to the lower machine;

[0031] deriving a calibration quantity format file according to the current calibration quantity value.

[0032] Optionally, the updating and saving of the HEX file of the lower machine according to the calibration quantity format file comprises:

[0033] acquiring calibration quantity address of the calibration quantity in the A2L file according to the calibration quantity in the calibration quantity format file derived according to the final calibration operation;

[0034] acquiring the corresponding calibration quantity and calibration quantity value in the HEX file of the lower machine according to the calibration quantity address of the calibration quantity in the A2L file;

[0035] comparing the calibration quantity and calibration quantity value in the calibration quantity format file derived according to the final calibration operation with the corresponding calibration quantity and calibration quantity value in the HEX file of the lower machine, and if the comparison is inconsistent,

[0036] updating the calibration quantity value of the corresponding calibration quantity in the HEX file of the lower machine by using the calibration quantity value of the calibration quantity in the calibration quantity format file derived according to the final calibration operation;

[0037] saving the updated HEX file of the lower machine in the lower machine.

[0038] The application further provides an electronic control unit diagnosis data management device, comprising:

[0039] a diagnosis data positioning module, configured to position diagnosis data to a preset calibration area through a data locator, and define the calibration area as a calibration quantity;

[0040] a communication connection configuration module, configured to configure communication connection of the lower machine and the upper machine calibration tool;

[0041] a calibration quantity format file acquisition module, configured to perform calibration processing on the calibration quantity, and obtain a calibration quantity format file;

[0042] a HEX file processing module, configured to update and save the HEX file of the lower machine according to the calibration quantity format file.

[0043] The application further provides an electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the method.

[0044] The application further provides a computer readable storage medium storing a computer program executable by an electronic device, and when the computer program is run on the electronic device, the electronic device executes the steps of the method.

[0045] Compared with the prior art, the application has the following advantages:

[0046] The electronic control unit diagnosis data management method of the application can position the diagnosis data required by the application professional to the calibration area through the data locator during the version function development and iteration process of the diagnosis related module, and regards the diagnosis data as calibration quantity, i.e. non-volatile quantity. After the engineering code is compiled, the positioning, storage and copying functions of the diagnosis data are consistent with the calibration quantity. If the application professional developer wants to save the diagnosis data, the developer in this scenario can use the calibration tool to export the calibration quantity (i.e. diagnosis data) to a calibration format file after the lower machine is powered on, integrate the calibration format file to the HEX file of the lower machine in the calibration tool, and save the diagnosis data. The application can provide a transition method in the case that the diagnosis module related function is not perfect in the initial stage of the vehicle controller software development, so that the diagnosis data can be stored in the lower machine, and the diagnosis data is not lost after power off. BRIEF DESCRIPTION OF DRAWINGS

[0047] In order to more clearly illustrate the specific embodiments of the application or the technical solutions in the prior art, the following will briefly introduce the drawings needed to be used in the specific embodiments or the prior art description. Obviously, the drawings in the following description are some embodiments of the application, and other drawings can also be obtained by those skilled in the art without creative labor.

[0048] Figure 1 The flowchart of the electronic control unit diagnosis data management method of an embodiment of the application;

[0049] Figure 2 The structural diagram of the electronic control unit diagnosis data management device of an embodiment of the application;

[0050] Figure 3 The electronic device structural diagram of the electronic control unit diagnosis data management method of the application. DETAILED DESCRIPTION

[0051] The technical solutions of the present application will be described clearly and completely in conjunction with the drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0052] Figure 1 A flowchart of a diagnostic data management method of an electronic control unit according to an embodiment of the present application;

[0053] As shown in Figure 1 A diagnostic data management method of an electronic control unit, comprising:

[0054] Step 1: Positioning the diagnostic data to a preset calibration area through a data locator, defined as calibration quantity;

[0055] Step 2: Configuring the communication connection between the lower computer and the calibration tool of the upper computer;

[0056] Step 3: Calibrating the calibration quantity to obtain a calibration quantity format file;

[0057] Step 4: Updating and saving the HEX file of the lower computer according to the calibration quantity format file.

[0058] The diagnostic data management method of the electronic control unit can position the diagnostic data required by the application professional to the calibration area through the data locator during the version function development and iteration process of the diagnostic related module. The diagnostic data is regarded as the calibration quantity, i.e. non-volatile quantity. After the engineering code is compiled, the positioning, storage and copying functions of the diagnostic data are consistent with the calibration quantity. If the application professional developer wants to save the diagnostic data, the developer in this scenario can export the calibration quantity (i.e. diagnostic data) to a calibration format file using the calibration tool after powering on the lower computer. The calibration format file is integrated into the HEX file of the lower computer in the calibration tool, and the download and storage of the diagnostic data are completed. The present application can provide a transition method in the case that the diagnostic module related functions are not perfect in the early stage of vehicle controller software development, so that the diagnostic data can be stored in the lower computer, and the diagnostic data is not lost after power off.

[0059] In the embodiment, the underlying developer needs to develop the underlying basic module before positioning the diagnostic data to the preset calibration area. Specifically, based on the XCP protocol, the underlying professional developer configures and perfects the XCP module in the underlying configuration project, so that the calibration function can be normally used. After the development is completed, the application developer releases it to the application developer, and then the application developer develops the modeling of the related modules based on the underlying software.

[0060] In the embodiment, the diagnostic data is located to the preset calibration area through the data locator, specifically, the application developer locates the diagnostic data to the calibration area through the data locator (fixes the address of the data at the compiling time to the preset memory address area) to regard the calibration as the calibration quantity, wherein the diagnostic data can be a custom memory segment of a link file.

[0061] In the embodiment, the communication connection between the lower computer and the upper computer calibration tool includes:

[0062] The source code file of the lower computer is compiled to obtain an executable file of the lower computer, a compiler is selected for the chip architecture type of the current vehicle controller to compile the source code C language file of the current vehicle controller into an ELF executable file and a HEX file, the lower computer in the embodiment can be one of an ECU, a development board or an MCU chip; the upper computer calibration tool is CANAPE.

[0063] In the embodiment, the executable file is burned into the lower computer, which means that the ELF file or the HEX file of the current vehicle compiled by the compiler is burned into the current lower computer.

[0064] In the embodiment, the lower computer is connected with the power supply;

[0065] The calibration tool is connected with the lower computer through a calibration CAN route bundle, wherein,

[0066] The calibration tool is configured with a connection channel of the lower computer.

[0067] Specifically, the connection between the lower computer and the calibration tool includes the connection of the power line and the connection of the calibration CAN route bundle, the connection of the power line is the connection between the lower computer development board and the DC power supply (power supply equipment), and the connection of the calibration CAN route bundle is the connection between the lower computer development board and the upper computer calibration tool.

[0068] In the embodiment, the communication connection between the lower computer and the upper computer calibration tool further includes:

[0069] The communication connection between the calibration tool and the lower computer is tested through the connection channel.

[0070] In one embodiment, the connection of the power line is to connect the development board KL30 and KL15 with the power supply, so that the development board can be in a constant power and high voltage state; the connection of the calibration CAN route bundle is to connect the calibration tool CANAPE and the ECU, and the channel is configured in the CANAPE software, after the ECU is powered on, the calibration tool and the lower computer are tested through the preset channel to see if they can normally handshake to keep the link in normal communication.

[0071] In this embodiment, before calibrating the calibration quantification and obtaining the calibration quantification format file, the method further includes:

[0072] Obtain the ELF file from the lower-level device;

[0073] Add the lower-level machine's ELF file to the calibration tool database so that the calibration tool database updates all variable and address information.

[0074] In this embodiment, the lower-level machine's ELF file needs to be added to the calibration tool CANAPE to update the calibration tool's database, that is, to update all variables and address information in the database.

[0075] In this embodiment, the calibration process for the calibration quantity to obtain the calibration quantity format file includes:

[0076] Retrieve calibration data and calibration data address information from the calibration tool database;

[0077] Add the calibration quantification and calibration quantification address information to the A2L file of the calibration tool;

[0078] Use a calibration tool to calibrate the calibration quantity and obtain the calibration quantity format file.

[0079] Specifically, when operating the calibration tool, it is necessary to first obtain the calibration quantity and calibration quantity address information from the calibration tool database (CANAPE's internal file format), then add the calibration quantity (diagnostic data) to the A2L file of the calibration tool CANAPE for configuration, and then add the calibration quantity (diagnostic data) to the main window of the calibration tool to prepare for calibration.

[0080] In this embodiment, a calibration tool is used to calibrate the calibration quantity, and the resulting calibration quantity format file includes:

[0081] Perform calibration on the calibration quantity to obtain the current calibration quantity value;

[0082] Obtain the address information of the calibration quantity from the A2L file;

[0083] Send a message to the lower-level computer, the message including the address information of the calibrated quantity;

[0084] Send the current calibration value to the lower-level computer;

[0085] Export the standardization format file based on the current standardization value.

[0086] In the embodiment, when the calibration tool calibrates the calibration quantity, the calibration tool searches the address information corresponding to the calibration quantity in the A2L file according to the name of the calibration quantity, so that when the calibration tool sends the message data segment to the lower machine, the message data segment includes the address information of the calibration quantity, and the calibration tool sends the current calibration quantity value of the calibration quantity after the calibration operation to the lower machine. The lower machine performs read-write change operation according to the address information and the current calibration quantity value, and feeds back to the upper machine after the operation. The specific interaction process includes the following steps:

[0087] (1) The calibration tool sends the address information of the calibration quantity to be operated to the lower machine;

[0088] (2) The lower machine replies with a positive response;

[0089] (3) The calibration tool transmits the current calibration quantity value to the lower machine;

[0090] (4) The lower machine replies with a positive response;

[0091] (5) After uploading the calibrated data, confirm that the calibration data is successful, or confirm that the calibration data is successful;

[0092] (6) The lower machine replies with a positive response.

[0093] After completing the calibration, the current calibration quantity is saved, specifically, a calibration quantity format file (DCM file) is derived according to the value of the current calibration quantity. This process is also completed by the calibration tool CANAPE. The DCM file includes the name of each calibration quantity and the value of the calibration quantity.

[0094] In the embodiment, the HEX file of the lower machine is updated and saved according to the calibration quantity format file, including:

[0095] According to the calibration quantity in the calibration quantity format file derived by the final calibration operation, the calibration quantity address of the corresponding calibration quantity in the A2L file is obtained;

[0096] According to the calibration quantity address of the calibration quantity in the A2L file, the corresponding calibration quantity and the calibration quantity value in the HEX file of the lower machine are obtained;

[0097] The calibration quantity and the calibration quantity value in the calibration quantity format file derived by the final calibration operation are compared with the corresponding calibration quantity and the calibration quantity value in the HEX file of the lower machine. If the comparison is inconsistent,

[0098] The calibration quantity value of the calibration quantity in the calibration quantity format file derived by the final calibration operation is used to update the calibration quantity value of the corresponding calibration quantity in the HEX file of the lower machine;

[0099] The updated HEX file of the lower machine is saved in the lower machine.

[0100] In the embodiment, the Display in vCDMstudio tool interface (offline storage mode) in the CANAPE software tool is used to integrate and save the DCM file and the current version of the HEX file of the lower computer.

[0101] First, the original HEX file is selected in the Display in vCDMstudio interface, and then the A2L file corresponding to the current calibration project is selected. The A2L file contains calibration quantities and address information of the calibration quantities. The HEX file contains address information and value information corresponding to the address information. After the A2L file is imported, the calibration quantities and the value information corresponding to the calibration quantities can be displayed. Then, the DCM file exported by the final calibration operation is imported. The DCM file contains calibration quantities and value information corresponding to the calibration quantities. The Differences in the parameter interface is selected in the compare tool bar to display the difference items of the calibration values. The difference values in the DCM file are transplanted to cover the corresponding calibration values in the HEX file. Then, the HEX file is saved, and the version development of the vehicle controller software iteration in this stage is completed.

[0102] Figure 2 FIG. 1 is a structural schematic diagram of a diagnostic data management device of an electronic control unit according to an embodiment of the present application;

[0103] As shown in Figure 2 The present application also provides a diagnostic data management device of an electronic control unit, which comprises a diagnostic data positioning module, a communication connection configuration module, a calibration quantity format file acquisition module and a HEX file processing module.

[0104] The diagnostic data positioning module is used to position the diagnostic data to a preset calibration area through a data positioning symbol, and define the calibration area as a calibration quantity.

[0105] The communication connection configuration module is used to configure the communication connection between the lower computer and the calibration tool of the upper computer.

[0106] The calibration quantity format file acquisition module is used to perform calibration processing on the calibration quantity, and obtain a calibration quantity format file.

[0107] The HEX file processing module is used to update and save the HEX file of the lower computer according to the calibration quantity format file.

[0108] It is worth noting that, although the system only discloses the basic function modules such as the diagnostic data positioning module, the communication connection configuration module, the calibration quantity format file acquisition module and the HEX file processing module, but does not mean that the device is limited to the above basic function modules, relatively, the meaning of the present application is that on the basis of the above basic function modules, the person skilled in the art can add one or more function modules according to the prior art to form infinite embodiments or technical solutions, that is, the system is open rather than closed, and the protection scope of the present application cannot be limited to the above disclosed basic function modules because the present embodiment only discloses individual basic function modules.

[0109] Figure 3 An electronic device structure diagram of the electronic control unit diagnostic data management method.

[0110] As shown in Figure 3 The electronic device includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus; the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the electronic control unit diagnostic data management method.

[0111] The present application also provides a computer readable storage medium which stores a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the electronic control unit diagnostic data management method.

[0112] The above processor can be a general processor, including a central processing unit (CPU), a network processor (NP) and the like; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0113] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus can be divided into an address bus, a data bus, a control bus, and the like. For the convenience of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or only one type of bus.

[0114] The electronic device includes a hardware layer, an operating system layer running above the hardware layer, and an application layer running on the operating system. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory. The operating system can be any one or more computer operating systems that implement control of the electronic device through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. In embodiments of the present application, the electronic device can be a handheld device such as a smartphone or a tablet computer, or an electronic device such as a desktop computer or a portable computer, and is not particularly limited in embodiments of the present application.

[0115] The execution subject of the electronic device control in embodiments of the present application can be the electronic device, or a functional module capable of calling and executing a program in the electronic device. The electronic device can obtain a firmware corresponding to the storage medium, and the firmware corresponding to the storage medium is provided by a vendor. The firmware corresponding to different storage media can be the same or different, and is not limited herein. After the electronic device obtains the firmware corresponding to the storage medium, the electronic device can write the firmware corresponding to the storage medium into the storage medium, specifically, burn the firmware corresponding to the storage medium into the storage medium. The process of burning the firmware into the storage medium can be implemented by using existing technology, and is not described in detail in embodiments of the present application.

[0116] The electronic device can also obtain a reset command corresponding to the storage medium, and the reset command corresponding to the storage medium is provided by a vendor. The reset command corresponding to different storage media can be the same or different, and is not limited herein.

[0117] At this time, the storage medium of the electronic device is a storage medium into which the corresponding firmware is written, and the electronic device can respond to the reset command corresponding to the storage medium in the storage medium into which the corresponding firmware is written, so that the electronic device resets the storage medium into which the corresponding firmware is written according to the reset command corresponding to the storage medium. The process of resetting the storage medium according to the reset command can be implemented by using existing technology, and is not described in detail in embodiments of the present application.

[0118] Those of skill in the art will understand that the herein disclosed aspects are to be considered in a descriptive sense only and not for purposes of limitation. Descriptions and examples of the aspects are intended to be illustrative of aspects of the present application, and are not intended to be limiting. It is contemplated that the aspects presented herein cover any and all modifications within the scope of the underlying principles of the aspects. It is intended that the aspects presented herein can be used in virtually any number of particular environments and / or applications.

[0119] It is to be understood that the terminology used herein is for the purpose of describing particular aspects only and is not intended to be limiting. It will be apparent to those of ordinary skill in the art that other layouts, designs, and materials can be employed.

[0120] The technical features of the above embodiments can be combined in any manner. In order to make the description simple, each technical feature in the above embodiments is not described in all possible combinations, however, as long as the combination of technical features does not exist contradictory, it should be considered within the scope of the present disclosure.

[0121] In addition, those skilled in the art will appreciate that, although some of the embodiments described herein comprise certain features that are not included in other embodiments, combinations of the features of the different embodiments are to be construed within the scope of the present disclosure and form different embodiments. For example, any one of the embodiments claimed in the claims can be used in any combination of the embodiments of the present disclosure.

[0122] In the description of the present disclosure, the description referring to the terms "one embodiment", "an example", "a specific example" and the like means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present disclosure. In the present disclosure, the illustrative description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0123] In addition, the technical solutions of the various embodiments of the present disclosure can be combined with each other, but it must be based on the realization of the ordinary skilled in the art, when the combination of technical solutions appears contradictory or unachievable, it should be considered that the combination of technical solutions does not exist, also not within the scope of the present disclosure claimed.

[0124] In addition, each functional module in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0125] All features disclosed in this specification, and / or all steps of any methods or processes disclosed in this specification, can be combined in any combination, except combinations where at least some of such features and / or steps are mutually exclusive. Any of the features disclosed in this specification, unless explicitly stated to the contrary, are intended to be alternatives that are applicable to and useful in most embodiments in which that feature is present. In other words, any of the features disclosed in this specification can be applied to or combined with any of the other features disclosed in this specification, unless the features are mutually exclusive. Throughout this specification, the same reference numerals or reference designations refer to the same or similar items in the figures.

[0126] As will be appreciated by one skilled in the art, aspects of the embodiments can be embodied as a system, method or computer program product. Computer program products can include computer readable storage media having computer readable program instructions stored therewith. The computer readable program instructions, when executed by a computer, cause the computer to implement aspects of the embodiments. The computer readable storage media can be tangible or in transitory media such as transmission media, signals, and the like. As noted above, any of the features disclosed in this specification can be applied to or combined with any of the other features disclosed in this specification, unless the features are mutually exclusive. In addition, each feature disclosed in this specification, unless specifically stated to the contrary, can be replaced by alternative features that serve the same, equivalent or a similar purpose, unless the context excludes it. Throughout this specification, the same reference numerals or reference designations refer to the same or similar items.

[0127] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0128] Those skilled in the art can understand that the embodiments of the present application can be provided as a method, device, or computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage, etc.) containing computer-usable program code.

[0129] In addition, each functional unit in each embodiment of the present application can be integrated in one processing module, or each unit can be physically present separately, or two or more units can be integrated in one module. The integrated module can be realized in the form of hardware or in the form of a software functional module. When the integrated module is realized 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.

[0130] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A diagnostic data management method of an electronic control unit, characterized by, The method comprises the following steps: locating diagnostic data to a preset calibration area through a data locator, and defining the diagnostic data as calibration quantities; configuring a communication connection between the lower computer and the upper computer calibration tool; calibrating the calibration quantities to obtain a calibration quantity format file; updating and saving the HEX file of the lower computer according to the calibration quantity format file; the updating and saving of the HEX file of the lower computer according to the calibration quantity format file comprises: obtaining the calibration quantity address of the corresponding calibration quantity in the A2L file according to the calibration quantity in the calibration quantity format file derived from the final calibration operation; obtaining the corresponding calibration quantity and calibration quantity value in the HEX file of the lower computer according to the calibration quantity address of the calibration quantity in the A2L file; comparing the calibration quantity and calibration quantity value in the calibration quantity format file derived from the final calibration operation with the corresponding calibration quantity and calibration quantity value in the HEX file of the lower computer, and if the comparison is inconsistent, updating the calibration quantity value of the corresponding calibration quantity in the HEX file of the lower computer with the calibration quantity value of the calibration quantity in the calibration quantity format file derived from the final calibration operation; saving the updated HEX file of the lower computer in the lower computer.

2. The diagnostic data management method of an electronic control unit according to claim 1, characterized by, the configuration of the communication connection between the lower computer and the upper computer calibration tool comprises: compiling the source code file of the lower computer to obtain an executable file that can be compiled by the lower computer; burning the executable file into the lower computer; connecting the lower computer with the power supply of the power supply; connecting the calibration tool with the lower computer through the calibration CAN route bundle, wherein, the calibration tool is configured with a connection channel with the lower computer.

3. The diagnostic data management method of an electronic control unit according to claim 2, wherein the configuration of the communication connection between the lower computer and the upper computer calibration tool further comprises: communicating test of the communication connection between the calibration tool and the lower computer through the connection channel.

4. The diagnostic data management method of an electronic control unit according to claim 1, characterized by, Before the calibration of the calibration quantities to obtain the calibration quantity format file, the method further comprises: obtaining the ELF file of the lower computer; adding the ELF file of the lower computer to the calibration tool database.

5. The diagnostic data management method of an electronic control unit according to claim 1, characterized by, the calibration of the calibration quantities to obtain the calibration quantity format file comprises: obtaining calibration quantity and calibration quantity address information from the calibration tool database; adding the calibration quantity and calibration quantity address information to the A2L file of the calibration tool; calibrating the calibration quantities using the calibration tool to obtain the calibration quantity format file.

6. The diagnostic data management method of an electronic control unit according to claim 5, wherein, the calibration of the calibration quantities using the calibration tool to obtain the calibration quantity format file comprises: carrying out a calibration operation on the calibration quantities to obtain the current calibration quantity value; obtaining the address information of the calibration quantity from the A2L file; sending a message to the lower computer, wherein the message comprises the address information of the calibration quantity; sending the current calibration quantity value to the lower computer; deriving the calibration quantity format file according to the current calibration quantity value.

7. An electronic control unit diagnostic data management apparatus characterized by comprising: The method comprises the following steps: a diagnostic data locating module for locating diagnostic data to a preset calibration area through a data locator, and defining the diagnostic data as calibration quantities; a communication connection configuration module for configuring a communication connection between the lower computer and the upper computer calibration tool; The calibration quantity format file acquisition module is configured to calibrate the calibration quantity and obtain a calibration quantity format file; The HEX file processing module is configured to update and save the HEX file of the lower machine according to the calibration quantity format file; The updating and saving of the HEX file of the lower machine according to the calibration quantity format file comprises: obtaining the calibration quantity address of the corresponding calibration quantity in the A2L file according to the calibration quantity in the calibration quantity format file derived by the final calibration operation; obtaining the corresponding calibration quantity and calibration quantity value in the HEX file of the lower machine according to the calibration quantity address of the calibration quantity in the A2L file; comparing the calibration quantity and calibration quantity value in the calibration quantity format file derived by the final calibration operation with the corresponding calibration quantity and calibration quantity value in the HEX file of the lower machine, and if the comparison is inconsistent, updating the calibration quantity value of the corresponding calibration quantity in the HEX file of the lower machine by using the calibration quantity value of the calibration quantity in the calibration quantity format file derived by the final calibration operation; saving the updated HEX file of the lower machine in the lower machine.

8. An electronic device, comprising: The device comprises: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the method of any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The device stores a computer program executable by the electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the method of any one of claims 1-6.

Images