A method, apparatus, and non-transitory computer-readable storage medium for configuring a vehicle ECU.
By parsing PDX data packets to obtain ECU information and selection feature codes, and calculating and sending ECU configuration codes, the problems of information omissions and selection errors in vehicle configuration systems are solved, and efficient and reliable personalized configuration data exchange is achieved.
Patent Information
- Application Number
- CN202311107625.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-30
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-08-30
AI Technical Summary
Existing vehicle configuration systems are prone to information omissions and selection errors when personalized options are required, leading to maintenance difficulties, reduced efficiency, and increased costs.
By parsing PDX data packets to obtain ECU information and optional feature codes, the actual ECU configuration code is calculated and sent to the target vehicle. Standardized vehicle configuration data is then parsed using ODX and configuration files.
It improves the efficiency and quality of configuration data exchange, ensures the integrity and reliability of configuration data, and meets personalized configuration requirements.
Smart Images

Figure CN117130306B_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of intelligent connected vehicle technology, specifically relating to a vehicle ECU configuration method, device, and non-transitory computer-readable storage medium. Background Technology
[0002] To enhance market competitiveness and align with business strategies and marketing needs, various automakers have introduced personalized vehicle configuration options. Consequently, vehicle production lines and after-sales diagnostic equipment need to be equipped with these options. However, existing vehicle configuration systems require engineers to interactively input configuration details based on these requirements, which can easily lead to information omissions and selection errors, resulting in maintenance difficulties, reduced efficiency, and increased costs. Summary of the Invention
[0003] The technical problem to be solved by the embodiments of the present invention is to provide a vehicle ECU configuration method, device and non-transitory computer-readable storage medium to improve the efficiency and quality of configuration data exchange and ensure the integrity and reliability of configuration data.
[0004] To solve the above-mentioned technical problems, the present invention provides a vehicle ECU configuration method, comprising:
[0005] Obtain the PDX data package and configuration file of the target vehicle model to be configured;
[0006] Parse the PDX data packet to obtain the ECU information definition information of the vehicle model, the definition information including vehicle configuration data definition information;
[0007] Based on the ECU information, a diagnostic request is sent to the corresponding ECU of the target vehicle to obtain the optional feature code;
[0008] Based on the configuration file, the vehicle configuration data definition information, and the optional feature code, the actual ECU configuration code is calculated and sent to the target vehicle.
[0009] Preferably, parsing the PDX data packet specifically includes:
[0010] Read the PDX data packet, extract the directory file of the PDX data packet, and obtain the ODX-E file through the contents of the directory file;
[0011] Read the ODX-E file to obtain the ECU-CONFIG node that defines the target ECU;
[0012] Parse the ECU-CONFIG node information to obtain the CONFIG-DATA node;
[0013] Parse the CONFIG-DATA node information to obtain the VALID-BASE-VARIANT node that defines ECU information and the CONFIG-RECORD node that defines configuration data;
[0014] Parse the VALID-BASE-VARIANT node information to obtain the ECU-VARIANT-SNREF node;
[0015] Parse the ECU-VARIANT-SNREF node information to obtain the corresponding ECU diagnostic address information;
[0016] Parse the CONFIG-RECORD node information to obtain the DIAG-COMM-DATA-CONNECTOR node that defines the communication data;
[0017] Parse the DIAG-COMM-DATA-CONNECTOR node information to obtain the WRITE-DIAG-COMM-CONNECTOR node;
[0018] Parse the WRITE-DIAG-COMM-CONNECTOR node information to obtain the WRITE-DIAG-COMM-SNREF node that defines the vehicle configuration service and the WRITE-DATA-SNREF node that defines the vehicle configuration data;
[0019] Parse the WRITE-DIAG-COMM-SNREF node information to obtain the corresponding vehicle configuration service SID and DID;
[0020] Parse the WRITE-DATA-SNREF node information to obtain the corresponding vehicle configuration data definition information.
[0021] Preferably, the definition information further includes optional feature code definition information, which is obtained by parsing the PDX data packet; the step of sending a diagnostic request to the corresponding ECU of the target vehicle based on the ECU information to obtain the optional feature code specifically includes:
[0022] Obtain the hexadecimal value of the selected feature code;
[0023] Based on the obtained optional feature code definition information, the hexadecimal value of the optional feature code is parsed into an optional feature code.
[0024] Preferably, the step of calculating the actual ECU configuration code based on the configuration file, the vehicle configuration data definition information, and the optional feature code specifically includes:
[0025] Read the ECU basic configuration code of the target vehicle model from the configuration file;
[0026] Read the configuration code calculation rules in the configuration file. The configuration code calculation rules define the configuration service corresponding to a certain function configuration, as well as the values that need to be changed in the configuration data.
[0027] The actual configuration code of the ECU is calculated based on the ECU's basic configuration code, optional feature code, and configuration code calculation rules.
[0028] Preferably, after sending the actual ECU configuration code to the target vehicle, the method further includes: obtaining the response from the target vehicle and storing the configuration result in a configuration database.
[0029] The present invention also provides a vehicle ECU configuration device, comprising:
[0030] The first acquisition module is used to acquire the PDX data package and configuration file of the model of the target vehicle to be configured;
[0031] The parsing module is used to parse the PDX data packet to obtain the ECU information definition information of the vehicle model, the definition information including vehicle configuration data definition information;
[0032] The second acquisition module is used to send a diagnostic request to the corresponding ECU of the target vehicle based on the ECU information to obtain the optional feature code;
[0033] The configuration module is used to calculate the actual ECU configuration code based on the configuration file, the vehicle configuration data definition information and the optional feature code, and send the actual ECU configuration code to the target vehicle.
[0034] Preferably, the parsing module is specifically used for:
[0035] Read the PDX data packet, extract the directory file of the PDX data packet, and obtain the ODX-E file through the contents of the directory file;
[0036] Read the ODX-E file to obtain the ECU-CONFIG node that defines the target ECU;
[0037] Parse the ECU-CONFIG node information to obtain the CONFIG-DATA node;
[0038] Parse the CONFIG-DATA node information to obtain the VALID-BASE-VARIANT node that defines ECU information and the CONFIG-RECORD node that defines configuration data;
[0039] Parse the VALID-BASE-VARIANT node information to obtain the ECU-VARIANT-SNREF node;
[0040] Parse the ECU-VARIANT-SNREF node information to obtain the corresponding ECU diagnostic address information;
[0041] Parse the CONFIG-RECORD node information to obtain the DIAG-COMM-DATA-CONNECTOR node that defines the communication data;
[0042] Parse the DIAG-COMM-DATA-CONNECTOR node information to obtain the WRITE-DIAG-COMM-CONNECTOR node;
[0043] Parse the WRITE-DIAG-COMM-CONNECTOR node information to obtain the WRITE-DIAG-COMM-SNREF node that defines the vehicle configuration service and the WRITE-DATA-SNREF node that defines the vehicle configuration data;
[0044] Parse the WRITE-DIAG-COMM-SNREF node information to obtain the corresponding vehicle configuration service SID and DID;
[0045] Parse the WRITE-DATA-SNREF node information to obtain the corresponding vehicle configuration data definition information.
[0046] Preferably, the definition information further includes optional feature code definition information, and the parsing module is further used to parse the PDX data packet to obtain the optional feature code definition information; the second acquisition module is specifically used for:
[0047] Obtain the hexadecimal value of the selected feature code;
[0048] Based on the obtained optional feature code definition information, the hexadecimal value of the optional feature code is parsed into an optional feature code.
[0049] Preferably, the configuration module is specifically used for:
[0050] Read the ECU basic configuration code of the target vehicle model from the configuration file;
[0051] Read the configuration code calculation rules in the configuration file. The configuration code calculation rules define the configuration service corresponding to a certain function configuration, as well as the values that need to be changed in the configuration data.
[0052] The actual configuration code of the ECU is calculated based on the ECU's basic configuration code, optional feature code, and configuration code calculation rules.
[0053] Preferably, the vehicle ECU configuration device further includes a third acquisition module, used to acquire the response of the target vehicle after the actual ECU configuration code is sent to the target vehicle, and store the configuration result in the configuration database.
[0054] The present invention also provides a vehicle ECU configuration device, including a processor and a memory, wherein the processor is configured to execute a computer program stored in the memory to implement the vehicle ECU configuration method.
[0055] The present invention also provides a non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium including a stored computer program; wherein, when the computer program is executed, it controls the device where the non-transitory computer-readable storage medium is located to execute the vehicle ECU configuration method.
[0056] Implementing this invention has the following beneficial effects: by using a vehicle configuration data parsing scheme that combines ODX and configuration files, while meeting personalized configuration requirements, the configuration information definition is standardized, which facilitates platform-based management, helps improve the efficiency and quality of data exchange, and ensures the integrity and reliability of configuration data. Attached Figure Description
[0057] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0058] Figure 1 This is a flowchart illustrating a vehicle ECU configuration method according to an embodiment of the present invention.
[0059] Figure 2 This is a schematic diagram of the process of parsing PDX data packets in an embodiment of the present invention.
[0060] Figure 3 This is a schematic diagram of the functional modules of a vehicle ECU configuration device according to Embodiment 2 of the present invention.
[0061] Figure 4 This is a schematic diagram of a vehicle ECU configuration device according to Embodiment 3 of the present invention. Detailed Implementation
[0062] The following description of the embodiments is taken with reference to the accompanying drawings, which illustrate specific embodiments in which the invention can be implemented.
[0063] Please refer to Figure 1As shown, Embodiment 1 of the present invention provides a vehicle ECU configuration method, including:
[0064] Obtain the PDX data package and configuration file of the target vehicle model to be configured;
[0065] Parse the PDX data packet to obtain the ECU information definition information of the vehicle model, the definition information including vehicle configuration data definition information;
[0066] Based on the ECU information, a diagnostic request is sent to the corresponding ECU of the target vehicle to obtain the optional feature code;
[0067] Based on the configuration file, the vehicle configuration data definition information, and the optional feature code, the actual ECU configuration code is calculated and sent to the target vehicle.
[0068] As can be seen from the above, the embodiments of the present invention, by formulating a vehicle configuration data parsing scheme, standardize the definition of configuration information, facilitate platform-based management, help improve the efficiency and quality of data exchange, and ensure the integrity and reliability of configuration data.
[0069] The PDX data packet and configuration file of the target vehicle model to be configured are stored on the server. Obtaining the PDX data packet and configuration file of the target vehicle model to be configured means obtaining them from the server.
[0070] Specifically, a PDX package is a file container for exchanging ODX (Open Diagnostic Data Exchange) files; all ODX files can be packaged into a single PDX package. ODX is an open diagnostic data exchange protocol for vehicles, a data file used by the MVCI (Modular Vehicle Communication Interface) of standard diagnostic tools defined by ASAM, facilitating data exchange between different suppliers, between suppliers and vehicle manufacturers, and between development and after-sales diagnostics. ODX 2.2.0 (ISO-22901) classifies ODX files into the following types:
[0071] ODX-C / -CS: Communication parameters, such as session layer, transport layer time parameters, and logical address, etc.
[0072] ODX-D: ECU Diagnostic Layer Specification (includes all diagnostic services for ECUs and the data used for diagnostics);
[0073] ODX-V: Vehicle Information (-V files can contain the topology of all controllers in the vehicle, and the diagnostic tool can select the ECU to be diagnosed through logic link);
[0074] ODX-E: ECU configuration (production line ECU configuration information, including enabling / disabling optional functions and setting characteristic curves according to specific vehicle environment and location);
[0075] ODX-F: ECU programming data (ECU flashing related data, such as checksum and signature information, etc.);
[0076] ODX-FD: Function Dictionary (Vehicle function information database, such as the central locking function which includes function information for all four doors);
[0077] ODX-M: Multi-ECU Functional Specification (defines methods for communicating with multiple ECUs simultaneously).
[0078] This embodiment of the invention processes the aforementioned ODX-E file. First, it retrieves the PDX data package and configuration file of the target vehicle to be configured from the server. Then, it extracts the ODX-E file from the PDX data package and parses it to obtain ECU information and definition information. In this embodiment, the definition information includes vehicle configuration data definition information and optional feature code definition information. It can be understood that vehicle configuration data definition information is the definition information about specific configuration data of the vehicle during the production or customization process; for example, a vehicle may have multiple different configuration options, such as a sunroof, navigation system, different types of tires, etc. Each configuration option needs an associated data definition so that the ECU can correctly control and coordinate various functions of the vehicle based on this data. These configuration data definitions are identified during the parsing of the PDX data package and used for further ECU configuration. Optional feature code definition information is the definition information of codes—optional feature codes—for certain optional configurations or features of the vehicle. For example, a vehicle may have different interior colors, audio systems, etc., and each option has a specific code or identifier called an "optional feature code"; the definition of these codes, i.e., the optional feature code definition information, describes how to parse and use these codes. During ECU configuration, based on the optional feature code definition information, the ECU can understand which optional features the vehicle possesses and perform corresponding control and adjustments accordingly. Both the optional feature code definition information and the vehicle configuration data definition information are parsed and extracted from the PDX data packet. Thus, during ECU configuration, the system can use this definition information to parse and obtain the optional feature codes and vehicle configuration data, and generate the corresponding configuration code for the ECU accordingly. The ODX-E file is a text file, and its contents can be parsed using UTF-8 format. Then, the data contained within each node can be retrieved by searching and identifying the node name. Please refer to [reference needed]. Figure 2 As shown, the specific process for parsing PDX data packets is as follows:
[0079] (1) Read the PDX data packet, extract the index.xml file (the directory file of the PDX data packet), and obtain the ODX-E file through the content of the index.xml file;
[0080] (2) Read the ODX-E file and obtain the ECU-CONFIG node that defines the target ECU. Generally speaking, one ECU-CONFIG node defines one ECU, and the ECU information corresponding to the ECU is defined in the VALID-BASE-VARIANT node under the ECU-CONFIG node. ECU-CONFIG is the top-level node of the ODX-E file and is a characteristic that distinguishes it from other types of ODX files.
[0081] (3) Parse the ECU-CONFIG node information to obtain the CONFIG-DATA node; the CONFIG-DATA node aggregates data representing ECU information and ECU configuration;
[0082] (4) Parse the CONFIG-DATA node information to obtain the VALID-BASE-VARIANT node that defines ECU information and the CONFIG-RECORD node that defines configuration data; where the VALID-BASE-VARIANT node represents the specific location of a valid ECU, and each ECU has only one BASE-VARIANT file in each vehicle model.
[0083] (5) Parse the VALID-BASE-VARIANT node information to obtain the ECU-VARIANT-SNREF node;
[0084] (6) Parse the ECU-VARIANT-SNREF node information to obtain the corresponding ECU diagnostic address information;
[0085] (7) Parse the CONFIG-RECORD node information and obtain the DIAG-COMM-DATA-CONNECTOR node that defines the communication data;
[0086] (8) Parse the DIAG-COMM-DATA-CONNECTOR node information and obtain the WRITE-DIAG-COMM-CONNECTOR node;
[0087] (9) Parse the WRITE-DIAG-COMM-CONNECTOR node information to obtain the WRITE-DIAG-COMM-SNREF node that defines the vehicle configuration service and the WRITE-DATA-SNREF node that defines the vehicle configuration data;
[0088] (10) Parse the WRITE-DIAG-COMM-SNREF node information to obtain the corresponding vehicle configuration service SID and DID, as well as the optional feature code DID;
[0089] (11) Parse the WRITE-DATA-SNREF node information to obtain the corresponding vehicle configuration data definition and optional feature code definition.
[0090] It should be noted that the ECU information includes the ECU diagnostic address information mentioned in step (6) above; the vehicle configuration data definition information includes the vehicle configuration service SID and DID mentioned in step (10) above, and the vehicle configuration data definition information mentioned in step (11); the optional feature code definition information includes the optional feature code DID mentioned in step (10) above, and the optional feature code definition information mentioned in step (11).
[0091] After obtaining the ECU information of the vehicle model, a diagnostic request is sent to the corresponding ECU of the target vehicle to obtain the hexadecimal value of the optional feature code. Then, based on the optional feature code definition information obtained in the previous steps, the hexadecimal value of the optional feature code is parsed into an optional feature code. It can be understood that the optional feature code is specifically represented in the form of a string.
[0092] Based on the configuration file, the vehicle configuration data definition information, and the optional feature code, the actual ECU configuration code is calculated, specifically including:
[0093] (1) Read the ECU basic configuration code of the target vehicle model from the configuration file;
[0094] (2) Read the configuration code calculation rules in the configuration file;
[0095] The configuration code calculation rules define the configuration service corresponding to a certain function configuration, as well as the values that need to be changed in the configuration data. For example, if the automatic locking function of BCM needs to be enabled, the configuration service corresponding to this function configuration will be defined in the configuration file as "WriteDataByIdentifier", the corresponding configuration service data will be "BCM_FunctionConfiguration", the corresponding configuration data bit will be "AutoLocked", and the value of this data bit should be "Enable".
[0096] (3) Calculate the actual configuration code of the ECU based on the ECU basic configuration code, optional feature code and configuration code calculation rules;
[0097] Taking the automatic locking function of BCM as an example, according to the configuration code calculation rules defined in the configuration file, the configuration service SID corresponding to "WriteDataByIdentifier" is obtained as 22, the configuration service DID corresponding to "BCM_FunctionConfiguration" is obtained as F124, the configuration service data bit corresponding to "AutoLocked" is obtained as the 3rd bit of the 5th byte, and the data bit value corresponding to "Enable" is obtained as 1. These are then combined with the obtained optional feature code and basic configuration code to obtain the actual configuration code.
[0098] After obtaining the actual ECU configuration code, based on the ECU information and the vehicle configuration SID and DID, the actual ECU configuration code is sent to the corresponding ECU of the target vehicle, thus completing the vehicle ECU configuration. Then, the response from the target vehicle is obtained, and the configuration result is stored in the configuration database.
[0099] Please refer to again Figure 3 As shown, corresponding to the vehicle ECU configuration method described in Embodiment 1 of the present invention, Embodiment 2 of the present invention provides a vehicle ECU configuration device, comprising:
[0100] The first acquisition module is used to acquire the PDX data package and configuration file of the model of the target vehicle to be configured;
[0101] The parsing module is used to parse the PDX data packet to obtain the ECU information and definition information of the vehicle model, wherein the definition information includes vehicle configuration data definition information;
[0102] The second acquisition module is used to send a diagnostic request to the corresponding ECU of the target vehicle based on the ECU information to obtain the optional feature code;
[0103] The configuration module is used to calculate the actual ECU configuration code based on the configuration file, the vehicle configuration data definition information and the optional feature code, and send the actual ECU configuration code to the target vehicle.
[0104] Preferably, the parsing module is specifically used for:
[0105] Read the PDX data packet, extract the directory file of the PDX data packet, and obtain the ODX-E file through the contents of the directory file;
[0106] Read the ODX-E file to obtain the ECU-CONFIG node that defines the target ECU;
[0107] Parse the ECU-CONFIG node information to obtain the CONFIG-DATA node;
[0108] Parse the CONFIG-DATA node information to obtain the VALID-BASE-VARIANT node that defines ECU information and the CONFIG-RECORD node that defines configuration data;
[0109] Parse the VALID-BASE-VARIANT node information to obtain the ECU-VARIANT-SNREF node;
[0110] Parse the ECU-VARIANT-SNREF node information to obtain the corresponding ECU diagnostic address information;
[0111] Parse the CONFIG-RECORD node information to obtain the DIAG-COMM-DATA-CONNECTOR node that defines the communication data;
[0112] Parse the DIAG-COMM-DATA-CONNECTOR node information to obtain the WRITE-DIAG-COMM-CONNECTOR node;
[0113] Parse the WRITE-DIAG-COMM-CONNECTOR node information to obtain the WRITE-DIAG-COMM-SNREF node that defines the vehicle configuration service and the WRITE-DATA-SNREF node that defines the vehicle configuration data;
[0114] Parse the WRITE-DIAG-COMM-SNREF node information to obtain the corresponding vehicle configuration service SID and DID;
[0115] Parse the WRITE-DATA-SNREF node information to obtain the corresponding vehicle configuration data definition information.
[0116] Preferably, the definition information further includes optional feature code definition information, and the parsing module is further used to parse the PDX data packet to obtain the optional feature code definition information; that is, to parse the WRITE-DIAG-COMM-SNREF node information to obtain the corresponding optional feature code DID; and to parse the WRITE-DATA-SNREF node information to obtain the corresponding optional feature code definition information; the second acquisition module is specifically used for:
[0117] Obtain the hexadecimal value of the selected feature code;
[0118] Based on the obtained optional feature code definition information, the hexadecimal value of the optional feature code is parsed into an optional feature code.
[0119] Preferably, the configuration module is specifically used for:
[0120] Read the ECU basic configuration code of the target vehicle model from the configuration file;
[0121] Read the configuration code calculation rules in the configuration file. The configuration code calculation rules define the configuration service corresponding to a certain function configuration, as well as the values that need to be changed in the configuration data.
[0122] The actual configuration code of the ECU is calculated based on the ECU's basic configuration code, optional feature code, and configuration code calculation rules.
[0123] Preferably, the vehicle ECU configuration device further includes a third acquisition module, used to acquire the response of the target vehicle after the actual ECU configuration code is sent to the target vehicle, and store the configuration result in the configuration database.
[0124] Please refer to again Figure 4 As shown, corresponding to the vehicle ECU configuration method described in Embodiment 1 of the present invention, Embodiment 3 of the present invention also provides a vehicle ECU configuration device, including a processor and a memory, wherein the processor is configured to execute a computer program stored in the memory to implement the vehicle ECU configuration method as described in Embodiment 1 of the present invention.
[0125] The processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor, or the processor can be any conventional processor. The processor is the control center of the device and connects the various parts of the device using various interfaces and lines.
[0126] The memory mainly includes a program storage area and a data storage area. The program storage area can store the operating system, applications required for at least one function, etc., while the data storage area can store related data, etc. Furthermore, the memory can be a high-speed random access memory, or a non-volatile memory, such as a plug-in hard drive, a SmartMedia Card (SMC), a Secure Digital (SD) card, and a Flash Card, or other volatile solid-state storage devices.
[0127] Corresponding to the vehicle ECU configuration method described in Embodiment 1 of the present invention, Embodiment 4 of the present invention also provides a non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium including a stored computer program; wherein, when the computer program is running, it controls the device where the non-transitory computer-readable storage medium is located to execute the vehicle ECU configuration method as described in Embodiment 1 of the present invention.
[0128] Preferably, the computer program can be divided into one or more modules / units (such as computer program 1, computer program 2, ...), and the one or more modules / units are stored in the memory and executed by the processor to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of performing a specific function, and the instruction segments are used to describe the execution process of the computer program in the device.
[0129] For the working principle and process of the above embodiments, please refer to the description of Embodiment 1 of the present invention, which will not be repeated here.
[0130] As can be seen from the above description, compared with the prior art, the beneficial effects of the present invention are as follows: by using a vehicle configuration data parsing scheme that combines ODX and configuration files, the configuration information definition is standardized while meeting the requirements of personalized configuration, which facilitates platform management, helps to improve the efficiency and quality of data exchange, and ensures the integrity and reliability of configuration data.
[0131] The above description is merely a preferred embodiment of the present invention and should not be construed as limiting the scope of the invention. Therefore, any equivalent variations made in accordance with the claims of the present invention are still within the scope of the present invention.
Claims
1. A vehicle ECU configuration method characterized by, include: Obtain the PDX data package and configuration file of the target vehicle model to be configured; Parse the PDX data packet to obtain the ECU information and definition information of the vehicle model, wherein the definition information includes vehicle configuration data definition information; Based on the ECU information, a diagnostic request is sent to the corresponding ECU of the target vehicle to obtain the optional feature code; Based on the configuration file, the vehicle configuration data definition information, and the optional feature code, the actual ECU configuration code is calculated, and the actual ECU configuration code is sent to the target vehicle. The parsing of the PDX data packet specifically includes: Read the PDX data packet, extract the directory file of the PDX data packet, and obtain the odx-e file through the contents of the directory file; Read the odx-e file to obtain the ECU-CONFIG node that defines the target ECU; Parse the ECU-CONFIG node information to obtain the CONFIG-DATA node; Parse the CONFIG-DATA node information to obtain the VALID-BASE-VARIANT node that defines ECU information and the CONFIG-RECORD node that defines configuration data; Parse the VALID-BASE-VARIANT node information to obtain the ECU-VARIANT-SNREF node; Parse the ECU-VARIANT-SNREF node information to obtain the corresponding ECU diagnostic address information; Parse the CONFIG-RECORD node information to obtain the DIAG-COMM-DATA-CONNECTOR node that defines the communication data; Parse the DIAG-COMM-DATA-CONNECTOR node information to obtain the WRITE-DIAG-COMM-CONNECTOR node; Parse the WRITE-DIAG-COMM-CONNECTOR node information to obtain the WRITE-DIAG-COMM-SNREF node that defines the vehicle configuration service and the WRITE-DATA-SNREF node that defines the vehicle configuration data; Parse the WRITE-DIAG-COMM-SNREF node information to obtain the corresponding vehicle configuration service SID and DID; Parse the WRITE-DATA-SNREF node information to obtain the corresponding vehicle configuration data definition information.
2. The vehicle ECU configuration method according to claim 1, characterized by, The definition information also includes optional feature code definition information, which is obtained by parsing the PDX data packet; the step of sending a diagnostic request to the corresponding ECU of the target vehicle based on the ECU information to obtain the optional feature code specifically includes: Obtain the hexadecimal value of the selected feature code; Based on the obtained optional feature code definition information, the hexadecimal value of the optional feature code is parsed into an optional feature code.
3. The vehicle ECU configuration method according to claim 1, characterized in that, The step of calculating the actual ECU configuration code based on the configuration file, the vehicle configuration data definition information, and the optional feature code specifically includes: Read the ECU basic configuration code of the target vehicle model from the configuration file; Read the configuration code calculation rules in the configuration file. The configuration code calculation rules define the configuration service corresponding to a certain function configuration, as well as the values that need to be changed in the configuration data. The actual configuration code of the ECU is calculated based on the ECU's basic configuration code, optional feature code, and configuration code calculation rules.
4. The vehicle ECU configuration method according to claim 1, characterized in that, After sending the actual ECU configuration code to the target vehicle, the process further includes: obtaining the response from the target vehicle and storing the configuration result in the configuration database.
5. A vehicle ECU configuration device, characterized in that, include: The first acquisition module is used to acquire the PDX data package and configuration file of the model of the target vehicle to be configured; The parsing module is used to parse the PDX data packet to obtain the ECU information and definition information of the vehicle model, wherein the definition information includes vehicle configuration data definition information; The second acquisition module is used to send a diagnostic request to the corresponding ECU of the target vehicle based on the ECU information to obtain the optional feature code; The configuration module is used to calculate the actual ECU configuration code based on the configuration file, the vehicle configuration data definition information and the optional feature code, and send the actual ECU configuration code to the target vehicle. The parsing module is specifically used for: Read the PDX data packet, extract the directory file of the PDX data packet, and obtain the odx-e file through the contents of the directory file; Read the odx-e file to obtain the ECU-CONFIG node that defines the target ECU; Parse the ECU-CONFIG node information to obtain the CONFIG-DATA node; Parse the CONFIG-DATA node information to obtain the VALID-BASE-VARIANT node that defines ECU information and the CONFIG-RECORD node that defines configuration data; Parse the VALID-BASE-VARIANT node information to obtain the ECU-VARIANT-SNREF node; Parse the ECU-VARIANT-SNREF node information to obtain the corresponding ECU diagnostic address information; Parse the CONFIG-RECORD node information to obtain the DIAG-COMM-DATA-CONNECTOR node that defines the communication data; Parse the DIAG-COMM-DATA-CONNECTOR node information to obtain the WRITE-DIAG-COMM-CONNECTOR node; Parse the WRITE-DIAG-COMM-CONNECTOR node information to obtain the WRITE-DIAG-COMM-SNREF node that defines the vehicle configuration service and the WRITE-DATA-SNREF node that defines the vehicle configuration data; Parse the WRITE-DIAG-COMM-SNREF node information to obtain the corresponding vehicle configuration service SID and DID; Parse the WRITE-DATA-SNREF node information to obtain the corresponding vehicle configuration data definition information.
6. The vehicle ECU configuration device according to claim 5, characterized in that, The definition information also includes optional feature code definition information; the parsing module is further used to parse the PDX data packet to obtain the optional feature code definition information; the second acquisition module is specifically used for: Obtain the hexadecimal value of the selected feature code; Based on the obtained optional feature code definition information, the hexadecimal value of the optional feature code is parsed into an optional feature code.
7. The vehicle ECU configuration device according to claim 5, characterized in that, The configuration module is specifically used for: Read the ECU basic configuration code of the target vehicle model from the configuration file; Read the configuration code calculation rules in the configuration file. The configuration code calculation rules define the configuration service corresponding to a certain function configuration, as well as the values that need to be changed in the configuration data. The actual configuration code of the ECU is calculated based on the ECU's basic configuration code, optional feature code, and configuration code calculation rules.
8. The vehicle ECU configuration device according to claim 5, characterized in that, It also includes a third acquisition module, which is used to acquire the response of the target vehicle after the actual ECU configuration code is sent to the target vehicle, and store the configuration result in the configuration database.
9. A vehicle ECU configuration device, characterized in that, It includes a processor and a memory, the processor being configured to execute a computer program stored in the memory to implement the vehicle ECU configuration method as described in any one of claims 1 to 4.
10. A non-transitory computer-readable storage medium, characterized in that, The non-transitory computer-readable storage medium includes a stored computer program; wherein, when the computer program is executed, it controls the device where the non-transitory computer-readable storage medium is located to perform the vehicle ECU configuration method as described in any one of claims 1 to 4.
Citation Information
Patent Citations
ECU configuration code automatic generation method and device
CN112445160A
ECU software refreshing method and system based on ODX
CN114756258A
