Vehicle ECU parameter configuration method and related equipment

Abstract

The embodiment of the invention discloses a vehicle ECU parameter configuration method and related equipment. The vehicle ECU parameter configuration method and the related equipment are used for flexibly and safely modifying vehicle ECU parameters under the condition that ECU firmware does not need to be recompiled or flashed. The method provided by the embodiment of the invention comprises the following steps: establishing communication connection between the terminal equipment and the vehicle, so that the terminal equipment accesses a parameter configuration interface built in the vehicle through the communication connection; receiving a parameter configuration operation for a target parameter in the target ECU through the parameter configuration interface; and based on the parameter configuration operation, generating a parameter configuration instruction and sending the parameter configuration instruction to the target ECU so as to update a target parameter of the target ECU according to the parameter configuration instruction.

Description

Technical Field

[0001] This application relates to the field of automotive electronic control technology, and in particular to vehicle ECU parameter configuration methods and related equipment. Background Technology

[0002] With the rapid development of automotive electronics technology, modern vehicles increasingly rely on electronic control units (ECUs) to manage and regulate various functions. ECUs store a large number of calibration parameters used to control fuel injection quantity, ignition timing, boost pressure, idle speed, throttle pedal response, and more. Therefore, adjusting ECU operating parameters to achieve vehicle control during vehicle development, verification, and after-sales diagnostics is a common practice in the industry.

[0003] In existing technologies, if it is necessary to modify the operating parameters inside the ECU, the configuration change is usually made by firmware flashing. After the R&D personnel adjust the target parameters in the calibration or development environment, they need to regenerate the ECU firmware containing the new parameter configuration, and then write the firmware into the ECU through the vehicle diagnostic interface, flashing device or remote upgrade (OTA, Over-The-Air) method, so that the ECU runs according to the new parameters after restarting.

[0004] However, in scenarios such as vehicle testing, debugging, and fault diagnosis where parameters need to be frequently adjusted, the operation process is relatively complex and time-consuming because each parameter change requires firmware generation and flashing. This limits the response speed and flexibility of parameter adjustment, making it difficult to meet the actual needs of rapid verification and dynamic debugging. Summary of the Invention

[0005] Based on the above problems, this application provides a method and related equipment for configuring vehicle ECU parameters. The purpose is to enable visualized remote configuration of vehicle ECU operating parameters without regenerating and flashing the ECU firmware, thereby improving the efficiency and flexibility of parameter adjustment in vehicle testing, debugging and fault diagnosis scenarios.

[0006] In a first aspect, embodiments of this application provide a method for configuring vehicle ECU parameters, including:

[0007] Establish a communication connection between the terminal device and the vehicle, so that the terminal device can access the parameter configuration interface built into the vehicle through the communication connection;

[0008] The parameter configuration interface receives parameter configuration operations for the target parameters in the target ECU.

[0009] Based on the parameter configuration operation, a parameter configuration instruction is generated and sent to the target ECU to update the target parameters of the target ECU according to the parameter configuration instruction.

[0010] In one embodiment, establishing a communication connection between the terminal device and the vehicle, so that the terminal device can access the vehicle's built-in parameter configuration interface through the communication connection, includes:

[0011] Enable the vehicle's wireless access point, and set a service set identifier and network access credentials to identify the vehicle, so that the terminal device can access the vehicle's internal network and access the vehicle's built-in parameter configuration interface after entering the correct access authentication credentials through the communication connection.

[0012] In one embodiment, the method further includes:

[0013] The network server program runs on the pre-installed operating system.

[0014] The network server program responds to the access request from the terminal device, loads the interface resource file stored in the preset path, and returns the interface resource file to the terminal device to render and display the parameter configuration interface on the terminal device.

[0015] In one embodiment, before receiving the parameter configuration operation for the target parameter in the target ECU through the parameter configuration interface, the method further includes:

[0016] The parameter configuration interface receives the user's account identifier and authentication password.

[0017] The account identifier and authentication password are compared with the pre-stored legitimate account information. If the comparison is successful, the terminal device is allowed to access the parameter configuration interface; if the comparison fails, the terminal device is denied access to the parameter configuration interface.

[0018] In one embodiment, after establishing a communication connection between the terminal device and the vehicle, enabling the terminal device to access the vehicle's built-in parameter configuration interface through the communication connection, the method further includes:

[0019] Read the pre-stored vehicle ECU configuration table; wherein the vehicle ECU configuration table records the identification information of each ECU in the vehicle and the configurable parameter information corresponding to each ECU;

[0020] Based on the records in the vehicle ECU configuration table, a target ECU list and configurable parameter items corresponding to each target ECU are generated, and the target ECU list and the configurable parameter items are returned to the parameter configuration interface for display.

[0021] In one embodiment, receiving parameter configuration operations for target parameters in the target ECU through the parameter configuration interface includes:

[0022] The parameter configuration interface receives a selection operation for selecting a target ECU and target parameters, thereby determining the target ECU and target parameters, and sending a parameter read request to the target ECU.

[0023] Obtain the current value of the target parameter returned by the target ECU, and display the current value of the target parameter in the parameter configuration interface;

[0024] The parameter configuration interface receives the target parameter value and parameter configuration type identifier for the target parameter settings.

[0025] In one embodiment, the parameter configuration instruction includes at least a target parameter value and a parameter configuration type identifier; updating the target parameter of the target ECU according to the parameter configuration instruction includes:

[0026] If the parameter configuration type identifier indicates a first configuration type, the target parameter value is updated in the volatile memory corresponding to the target ECU so that the target ECU can operate according to the target parameter value in the current operating cycle; wherein, after the target ECU is reset, the target parameter is restored to the original parameter value stored in the non-volatile memory;

[0027] If the parameter configuration type identifier indicates a second configuration type, the target parameter value is written into the non-volatile memory of the target ECU so that the target ECU can operate according to the target parameter value during the current operating cycle and after the target ECU is reset.

[0028] Secondly, embodiments of this application also provide a vehicle ECU parameter configuration device, including:

[0029] A communication connection establishment unit is used to establish a communication connection between a terminal device and a vehicle, so that the terminal device can access the parameter configuration interface built into the vehicle through the communication connection.

[0030] An operation receiving unit is used to receive parameter configuration operations for target parameters in the target ECU through the parameter configuration interface;

[0031] The instruction receiving unit is configured to generate a parameter configuration instruction based on the parameter configuration operation and send the parameter configuration instruction to the target ECU to update the target parameters of the target ECU according to the parameter configuration instruction.

[0032] Thirdly, embodiments of this application also provide a computer device, including:

[0033] Central processing unit, memory, input / output interfaces;

[0034] The memory is either a short-term storage memory or a persistent storage memory;

[0035] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the vehicle ECU parameter configuration method described in the first aspect of the embodiments of this application or any specific implementation thereof.

[0036] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, is used to implement the vehicle ECU parameter configuration method described in the first aspect or any specific implementation of the first aspect of the embodiments of this application.

[0037] Fifthly, embodiments of this application also provide a computer program product storing a computer program / instruction thereon, which, when executed by a processor, is used to implement the vehicle ECU parameter configuration method described in the first aspect or any specific implementation of the first aspect of the embodiments of this application.

[0038] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0039] This application embodiment establishes a communication connection between the terminal device and the vehicle, enabling the terminal device to directly access the vehicle's built-in parameter configuration interface. Within this interface, the terminal device configures the target parameters in the target ECU. The vehicle then generates parameter configuration instructions based on these instructions and sends them to the target ECU for parameter updates. This eliminates the complex process of recompiling the ECU firmware, generating a complete firmware image, and flashing the firmware, as is common in traditional solutions. Therefore, when ECU operating parameters need to be changed, only parameter-level data exchange packets can replace the entire firmware flashing process. This allows for rapid parameter modification and verification in scenarios requiring frequent parameter adjustments, such as vehicle testing, debugging, and fault diagnosis, improving the response speed and efficiency of parameter adjustments. Attached Figure Description

[0040] 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 embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0041] Figure 1 This is a schematic flowchart of a vehicle ECU parameter configuration method provided in an embodiment of this application;

[0042] Figure 2 This is a schematic diagram of a vehicle ECU parameter configuration device provided in an embodiment of this application;

[0043] Figure 3 This is a schematic diagram of a computer device structure provided in an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] In this embodiment, the application environment of the vehicle ECU parameter configuration method includes at least the vehicle itself and terminal devices that interact with the vehicle. Multiple Electronic Control Units (ECUs) are installed inside the vehicle, each ECU performing different vehicle functions such as engine control, transmission control, chassis control, and body control. The ECUs can interact with each other via an in-vehicle communication network, which can be a controller area network, an Ethernet-based in-vehicle network, or a combination of both. Inside the vehicle, one or more of an in-vehicle gateway controller, domain controller, or centralized in-vehicle computing platform can also be installed to implement protocol conversion, data forwarding, diagnostics, and management functions between different in-vehicle communication networks.

[0046] In this embodiment, to enable external terminal devices to configure the ECU parameters inside the vehicle, a communication unit is provided in the vehicle for establishing a data communication connection with the terminal device. This communication unit can be a wireless communication module, a wired communication interface, or a combination thereof. The wireless communication module can support wireless local area networks, cellular mobile communication, or short-range wireless communication. The vehicle's onboard gateway controller or domain controller can be configured with an operating system and network service programs running on it. These network service programs provide a parameter configuration interface based on pre-set page resources, which is rendered and displayed in the terminal device's browser or client application, allowing users to select and configure the target ECU and its parameters through a graphical interface. The vehicle can also include an authentication module and a permission management module for the parameter configuration interface, used to verify the identity and control access of terminal devices and users accessing the parameter configuration interface, ensuring the security and controllability of ECU parameter configuration operations.

[0047] The terminal device can be a smartphone, tablet, laptop, or other electronic device with network access capabilities. The terminal device connects to the vehicle's communication network via the aforementioned communication unit and accesses the vehicle's built-in parameter configuration interface using a browser or dedicated application. In the parameter configuration interface, the terminal device can obtain a list of ECUs currently supported for configuration by the vehicle, as well as the configurable parameter information corresponding to each ECU. Through interface interaction, it transmits the user's intended settings for the target parameters to the vehicle's onboard gateway controller, domain controller, or onboard computing platform, thereby generating and issuing parameter configuration commands.

[0048] The various embodiments of this application will now be described in further detail with reference to the accompanying drawings.

[0049] This application provides a method for configuring vehicle ECU parameters, such as... Figure 1 As shown, the method includes steps S110-S130.

[0050] S110: Establish a communication connection between the terminal device and the vehicle, so that the terminal device can access the parameter configuration interface built into the vehicle through the communication connection;

[0051] The vehicle can establish a logical communication link with the terminal device via a wireless access point, wired network interface, or other communication methods. After the communication link is established, the terminal device can act as a client node in the vehicle network, initiating access requests to service nodes inside the vehicle. These service nodes can be ECUs with network service capabilities, such as vehicle gateways, domain controllers, or vehicle computing platforms. This allows the terminal device to load and display the vehicle's built-in parameter configuration interface. The parameter configuration interface can be understood as a human-machine interface provided by an application running inside the vehicle, used to display the various ECUs in the vehicle and their configurable parameters, and to receive configuration operations from the terminal device user. This transforms the ECU parameter access operation, which originally required dedicated flashing equipment or diagnostic tools, into an interactive access method based on a general-purpose terminal device.

[0052] S120: Receive parameter configuration operations for target parameters in the target ECU through the parameter configuration interface;

[0053] In this embodiment, the target ECU refers to the ECU selected for parameter adjustment in the current parameter configuration operation; the target parameter refers to the modifiable operating or calibration parameters within the target ECU, such as parameters used to control fuel injection quantity, ignition timing, boost pressure, idle speed, or throttle pedal response. The parameter configuration operation includes at least selecting the target ECU, selecting target parameter items, and setting target parameter values. It may also include selecting a parameter configuration type, which indicates the activation method and activation period of the set target parameter value within the ECU. After receiving the above parameter configuration operation, the parameter configuration interface can organize the operation events input and selected by the user at the interface layer into an internally unified configuration data structure, thereby generating parameter configuration instructions.

[0054] S130: Based on the parameter configuration operation, generate a parameter configuration instruction and send the parameter configuration instruction to the target ECU to update the target parameters of the target ECU according to the parameter configuration instruction.

[0055] Parameter configuration instructions can be understood as control messages encapsulated in a predetermined format within the vehicle. These messages carry information such as the target ECU identifier, target parameter identifier, target parameter value, and parameter configuration type identifier. The specific message format or communication protocol used can be adapted to existing in-vehicle communication networks, and this application does not limit this. After receiving configuration data from the parameter configuration interface, the vehicle assembles it into parameter configuration instructions according to preset conversion rules and sends them to the corresponding target ECU via the in-vehicle communication network. Upon receiving the parameter configuration instructions, the target ECU parses out the target parameter identifier and target parameter value, and determines whether to write the target parameter value to volatile or non-volatile storage space based on the parameter configuration type identifier. This completes the update of the target parameters, allowing subsequent control operations of the ECU to be performed based on the updated parameter values. This step decouples the interface-level parameter configuration from the ECU's internal parameter storage, enabling the generation, management, and distribution of parameters to be completed without regenerating the firmware.

[0056] This application embodiment achieves a complete chain by providing a built-in parameter configuration interface on the vehicle side and remotely accessing this interface via a terminal device. This chain retrieves parameter configuration intent from the human-machine interface layer, generates standardized parameter configuration instructions through the vehicle's internal conversion logic, and finally sends them to the target ECU to update internal parameters. This chain replaces the traditional parameter change path, which relies on firmware compilation and flashing, with a parameter update path based on runtime instructions. This shifts parameter adjustment from firmware-level operations to runtime-level configuration operations, reducing reliance on firmware generation and flashing processes, simplifying the technical process of ECU parameter adjustment, and improving the visibility and operational flexibility of the parameter configuration process. This facilitates rapid parameter adjustment and verification in scenarios requiring frequent parameter modifications, such as vehicle development, testing, debugging, and fault diagnosis, thereby improving the efficiency and practicality of vehicle ECU parameter configuration.

[0057] To enable terminal devices to quickly configure the operating parameters of the ECU in a vehicle, in one embodiment, step S110 of this application establishes a communication connection between the terminal device and the vehicle, so that the terminal device can access the parameter configuration interface built into the vehicle through the communication connection. This includes: enabling the vehicle's wireless access point, setting a service set identifier and network access credentials to identify the vehicle, so that the terminal device can access the vehicle's internal network and access the vehicle's built-in parameter configuration interface after inputting the correct access authentication credentials through the communication connection.

[0058] This application embodiment employs a method of enabling a Wireless Access Point (WAP) on the vehicle side to construct a vehicle local area network, thereby achieving direct communication between the terminal device and the vehicle without relying on an external network environment. Specifically, the vehicle's wireless access point is a control node deployed inside the vehicle, equipped with a wireless communication module and network management functions, such as an in-vehicle gateway, a communication control unit, or a vehicle controller with network service capabilities. During the activation of the wireless access point, the vehicle sets a set of network access parameters, including a Service Set Identifier (SSID) for identifying the vehicle and network access credentials for access permission control. The aforementioned Service Set Identifier can be understood as the network name broadcast by the vehicle; essentially, it is a network name composed of characters, displayed to the user in the wireless network scanning list of the terminal device. For example, this identifier can be set to a string containing specific information such as the vehicle model and vehicle identification number, so that technicians can accurately identify the target vehicle in a multi-vehicle environment. The network access credentials correspond to the authentication password used to verify the access permission of the terminal device, such as a Wi-Fi connection password or other credentials based on authentication protocols.

[0059] When a terminal device (such as a laptop, tablet, or smartphone) enters the communication range near the vehicle, the Service Set Identifier (SSID) broadcast by the vehicle can be found in the list of wireless networks. The user selects the corresponding SSID on the terminal device and enters the correct network access credentials. An authentication process then occurs between the terminal device and the vehicle's wireless access point. Upon successful authentication, the terminal device connects to the local area network (LAN) created by the vehicle's wireless access point. At this point, the vehicle's control node (i.e., gateway or domain controller) assigns an Internet Protocol address (IP address) within the LAN to the successfully connected terminal device using methods such as Dynamic Host Configuration Protocol (DHCP), ensuring that the terminal device, the vehicle's control node, and other network entities are on the same logical network segment.

[0060] Once the vehicle's wireless access point is activated, the internal parameter configuration service will operate as a server, listening for HTTP or HTTPS requests from terminal devices to provide access to the parameter configuration interface. Terminal devices can access the vehicle's designated local IP address or domain name via a browser or dedicated client, for example, by entering a specific internet protocol address and port number, such as 192.168.1.1\index.html, to retrieve the parameter configuration interface resource files deployed by the vehicle, including web page structure files, style files, and script files. 192.168.1.1 is the default IP address of the gateway or domain controller. The parameter configuration interface is typically presented as an embedded webpage, which directly utilizes the vehicle's existing network hardware and software resources, thus enabling reliable direct communication between terminal devices and the vehicle in closed or offline environments without relying on external internet infrastructure.

[0061] To enable the terminal device to visualize the configuration of vehicle ECU parameters, in one embodiment, the method of this application further includes: running a network server program based on a preset operating system; the network server program responding to the access request from the terminal device, loading an interface resource file stored in a preset path, and returning the interface resource file to the terminal device to render and display the parameter configuration interface on the terminal device.

[0062] In this embodiment, the vehicle's onboard gateway or domain controller (which can also be understood as the vehicle's control node) is equipped with electronic hardware possessing certain computing and storage capabilities, and an operating system is pre-installed on it. The pre-installed operating system refers to general-purpose or embedded operating system software integrated at the factory or subsequently installable on the hardware platform, such as embedded Linux, Android, or other operating systems suitable for the vehicle environment. Based on this operating system environment, when the vehicle starts up or enters a specific service mode, a network server program is pre-configured and runs. This network server program refers to software capable of listening to network ports and processing application layer protocol requests such as Hypertext Transfer Protocol (HTTP). It can be implemented based on existing mature server frameworks, such as Apache, Nginx, Lighttpd, and Tomcat. These network server programs are configured to run continuously in the background as system services or daemons, listening to specific network ports (such as port 80 or 8080) and responding to access requests from the network. For example, the interface resource files related to each parameter configuration may include HyperText Markup Language (HTML) files for defining the page structure and content, Cascading Style Sheets (CSS) files for controlling the page's visual appearance, and JavaScript script files and images for implementing the page's dynamic interaction logic. These interface resource files are pre-stored in a storage path specified in the gateway or domain controller's file system. After receiving an access request from a terminal device, the web server retrieves the corresponding interface resource files from this preset path based on the path information in the access request, loads them, and returns the encapsulated response data from the web server to the terminal device. The browser on the terminal device then parses and renders the data, ultimately presenting the parameter configuration interface on the terminal device.

[0063] For example, when a terminal device initiates an access request through a browser (e.g., a user enters a specified IP address in the browser's address bar), the access request reaches the vehicle gateway via an established communication connection. The running web server program intercepts and parses this access request, and locates the corresponding interface resource file under the preset path according to the resource path specified in the access request. For example, when requesting the root path, the server typically returns an HTML file named index.html by default. The server program reads this HTML file from the storage medium and, according to the corresponding protocol specifications, returns the HTML file as the response body, along with necessary response headers (such as content type and content length), to the requesting terminal device.

[0064] After receiving a response from the vehicle's network server program, the browser on the terminal device begins parsing and rendering. First, it parses the HTML file, which serves as the entry point, and builds a Document Object Model (DOM) tree. Then, it loads and parses the referenced CSS file, builds a CSS Object Model (CSS) tree, and applies the styles to the DOM to determine the page's visual layout. Simultaneously, it executes the referenced JavaScript files, which contain code defining the interactive logic in the parameter configuration interface. This includes actions such as requesting a list of configurable ECUs from the vehicle's backend service, processing user selections and inputs, and sending parameter read or write commands.

[0065] It should be noted that the interface resource files are not limited to the combination of HTML files, CSS files, and JavaScript script files mentioned above. In other embodiments, they may also include template files for page layout or component reuse, various image files for displaying icons or backgrounds, multimedia resource files such as audio and video, internationalization resource files for multilingual switching, or packaged resource files generated by a front-end framework. For example, in the scenario of implementing a single-page application using a front-end framework, the interface resource files can be static resource files packaged by build tools such as Vue framework or React framework, including packaged script files, style files, and related runtime resources; in the scenario of implementing the parameter configuration interface in a non-web page form, the interface resource files can also be descriptive configuration files or interface definition files used by the terminal device to present the graphical interface. As long as the relevant interface resource files can be loaded by the web server program and parsed by the terminal device for rendering and displaying the interactive interface for ECU parameter configuration on the terminal device, they all fall within the scope of the interface resource files described in this application, and this application does not limit them.

[0066] To ensure the security and controllability of vehicle ECU parameter configuration operations, in one embodiment, before receiving the parameter configuration operation for the target parameter in the target ECU through the parameter configuration interface as described in step S120 of this application, the method of this application embodiment further includes: receiving an account identifier and authentication password input by the user in the parameter configuration interface; comparing the account identifier and authentication password with pre-stored legitimate account information; if the comparison is successful, allowing the terminal device to access the parameter configuration interface; if the comparison fails, denying the terminal device access to the parameter configuration interface.

[0067] In this embodiment, when the terminal device accesses the vehicle's built-in parameter configuration interface via a communication connection, the parameter configuration interface first presents an authentication interaction interface, such as a form interface including an account input box, a password input box, and a submit button, i.e., a login interface, used to receive user-inputted authentication information. In this login interface, the user needs to input an account identifier and an authentication password. The account identifier can be identification information used to distinguish different user identities, such as a username, employee ID, email address, or other unique or distinguishable identifier fields. The authentication password can be a password information that corresponds one-to-one with the account identifier, or it can be an encrypted or encoded authentication credential. After the user completes the input and triggers the submit operation, the client script (such as JavaScript) running in the interface collects this input data and sends the account identifier and authentication password to the vehicle's onboard gateway or domain controller via a network connection. The onboard gateway or domain controller then compares the account identifier and authentication password with pre-stored legitimate account information.

[0068] Pre-stored legitimate account information can be stored in the storage area corresponding to the gateway controller, domain controller, or other in-vehicle computing platform. Legitimate account information typically includes account identifiers for multiple trusted users and corresponding authentication passwords for each account identifier. In specific implementations, to enhance security, the pre-stored authentication passwords can be stored using a hash algorithm or other encryption methods. When the vehicle compares the user-input authentication password, it can transform it according to the same rules before matching it with the pre-stored data, thereby preventing the plaintext password from being directly exposed during the interaction process. This application does not limit the specific encryption algorithm and storage structure; the specific implementation method can be selected according to data security requirements.

[0069] After the comparison is completed, if the user's entered account identifier and authentication password match a record in the pre-stored list of legitimate accounts, the comparison is considered successful, and the user corresponding to the current terminal device is deemed to have legitimate access rights. In this case, the terminal device is allowed to further access the complete parameter configuration interface, where the user can then browse the list of configurable ECU parameters, view the current values ​​of each parameter, and initiate parameter configuration operations. Conversely, if the comparison result shows that the user's entered account identifier does not match the authentication password, or if the account identifier does not exist in the pre-stored list of legitimate accounts, the user is deemed to lack access rights, and the terminal device is denied access to the parameter configuration interface. Feedback can be provided by returning to the login failure message or remaining on the login screen, thus preventing unauthorized users from viewing and modifying the vehicle's ECU parameters. In this way, even if the terminal device connects to the vehicle's internal network via a wireless access point, only legitimate users verified with the account identifier and authentication password are allowed to access the parameter configuration interface to perform parameter modification or viewing operations, avoiding the data security risk of arbitrary modification of ECU parameters simply by successfully connecting to the vehicle network. On the other hand, by pre-storing information about different accounts and their corresponding permissions, it is possible to expand to multi-level user permission control without changing the overall architecture. For example, it can distinguish between read-only users and users with write permissions, or distinguish the permissions of different roles such as testers and maintenance personnel, making the ECU parameter configuration process safer and more flexible.

[0070] To achieve visualized configuration and rapid management of vehicle ECU parameters, in one embodiment, after establishing a communication connection between the terminal device and the vehicle as described in step S110 of this application embodiment, so that the terminal device can access the parameter configuration interface built into the vehicle through the communication connection, the method of this application embodiment further includes: reading a pre-stored vehicle ECU configuration table; wherein, the vehicle ECU configuration table records the identification information of each ECU in the vehicle and the configurable parameter information corresponding to each ECU; generating a target ECU list and configurable parameter items corresponding to each target ECU based on the records in the vehicle ECU configuration table, and returning the target ECU list and the configurable parameter items to the parameter configuration interface for display.

[0071] After the terminal device successfully establishes a communication connection with the vehicle and accesses the parameter configuration interface, and before receiving specific parameter configuration operations, this embodiment of the application will first display the ECU information and configurable parameter items of the ECUs that can be configured in the current vehicle ECU configuration table. The ECU information stored in the vehicle ECU configuration table may include the unique identifier of each ECU, the name of the control function (e.g., engine controller, transmission controller, body controller, etc.), and the communication network it is on (e.g., CAN bus, LIN bus, etc.). In addition, the configurable parameter information corresponding to the ECU includes the unique identifier of each configurable parameter within the ECU (which may be a parameter number or memory address offset), the name of each parameter item (e.g., idle speed, fuel injection quantity), data type (e.g., integer, floating-point number), value range, default value, and other attribute fields.

[0072] Once a user is authenticated and granted access, the parameter configuration interface or its backend network server logic triggers a read operation on the vehicle ECU configuration table. This involves accessing the storage area and reading the complete or filtered vehicle ECU configuration table content based on the user's account permissions. Subsequently, the identification information of all ECUs is extracted from the read table and organized into an ordered list—the target ECU list. Simultaneously, for each ECU in the target ECU list, all configurable parameter information is extracted and organized, forming a tree-like list or grouped set of configurable parameter items associated with each ECU. For example, the target ECU list can be used to populate a dropdown selection box or a navigation tree, allowing the user to select an ECU as the target ECU. When a user selects an ECU, the parameter configuration interface generates corresponding parameter input areas based on the configurable parameter item data bound to that ECU. These controls include input boxes, sliders, and dropdown menus, each with input restrictions set according to parameter metadata (such as value range and data type). Therefore, it can be understood that before generating the parameter configuration command, the vehicle gateway or domain controller needs to perform a validity check on the target parameter value. The parameter configuration command is only generated and sent when the target parameter value input by the user meets the preset value range and data type requirements; and when the target parameter value input by the user does not meet the preset requirements, a parameter configuration error message is output in the parameter configuration interface.

[0073] In one embodiment, step S120 of this application embodiment, which describes receiving a parameter configuration operation for a target parameter in a target ECU through the parameter configuration interface, includes: receiving a selection operation for selecting a target ECU and a target parameter through the parameter configuration interface to determine the target ECU and the target parameter, and sending a parameter read request to the target ECU; obtaining the current value of the target parameter returned by the target ECU, and displaying the current value of the target parameter on the parameter configuration interface; and receiving the target parameter value and parameter configuration type identifier set for the target parameter through the parameter configuration interface.

[0074] Specifically, the interface first displays a list of target ECUs. A specific ECU is selected as the target ECU for this operation only upon receiving user click, touch, or keyboard operation events. For example, the item identified as the engine ECU can be selected from the displayed list of target ECUs. Next, the parameter configuration interface will display the configurable parameter items corresponding to the selected target ECU. From this, the user can further select one or more specific parameters as target parameters, such as selecting the injection time, thereby determining the object of this parameter configuration action.

[0075] After identifying the target ECU and target parameters, the vehicle constructs a parameter read request based on the parameter configuration action transmitted from the parameter configuration interface and sends this request to the target ECU via the vehicle communication network. The vehicle communication network can be a controller area network, Ethernet, or other vehicle bus type; this embodiment does not limit this. The parameter read request carries at least the identification information of the target ECU and the target parameter, enabling the target ECU to identify which parameter's current value needs to be returned. Upon receiving the parameter read request, the target ECU reads the current value of the target parameter from its corresponding operating storage space or configuration storage area based on the parameter identifier in the request, and returns this current value to the front-end parameter configuration interface via the vehicle communication network. The latter then transmits the current value to the parameter configuration interface for display. Taking the engine ECU as an example, when a technician selects the engine system and injection timing parameters in the interface, the gateway or domain controller sends a request to the engine ECU to read the injection timing. The engine ECU returns the current injection timing value, and the parameter configuration interface then displays this current value on the terminal device, allowing technicians to refer to the current parameter value and determine the adjustment range.

[0076] After obtaining and displaying the current value of the target parameter, the parameter configuration interface is further used to receive the new target parameter value set by the technician, i.e., receiving the target parameter value and the parameter configuration type identifier. The parameter configuration type identifier indicates the effective method and duration of the target parameter value within the ECU, distinguishing whether the parameter modification is temporary or permanent.

[0077] Specifically, in one embodiment, the parameter configuration instruction includes at least a target parameter value and a parameter configuration type identifier; step S130 of this application embodiment, which describes updating the target parameter of the target ECU according to the parameter configuration instruction, includes: if the parameter configuration type identifier indicates a first configuration type, then updating the target parameter value in the volatile memory corresponding to the target ECU, so that the target ECU can operate according to the target parameter value in the current operating cycle; wherein, after the target ECU is reset, the target parameter is restored to the original parameter value stored in the non-volatile memory; if the parameter configuration type identifier indicates a second configuration type, then writing the target parameter value into the non-volatile memory of the target ECU, so that the target ECU can operate according to the target parameter value in the current operating cycle and after the target ECU is reset.

[0078] Parameter configuration commands are control commands generated by the vehicle and sent to the target ECU after the terminal device selects the target parameter value and parameter configuration type through the parameter configuration interface. After receiving the parameter configuration command from the gateway or domain controller through the vehicle's internal network, the target ECU's embedded firmware program first parses the parameter configuration command to extract the payload contained in the parameter configuration command, which includes at least: the specific parameter value to be modified, i.e., the target parameter value, and the parameter configuration type identifier corresponding to the target parameter value.

[0079] If the parsed parameter configuration type identifier indicates the first configuration type (i.e., corresponding to a temporary configuration), the ECU will write the received new parameter value (target parameter value) into a specific memory area in the volatile memory corresponding to the ECU, which is reserved or dynamically allocated for temporary parameter management. Here, volatile memory, such as static random access memory or dynamic random access memory, has the advantage of fast access speed, but all data stored in the volatile memory will be lost after the ECU loses power or performs a hardware or software reset. Therefore, after writing the target parameter value into the volatile memory, the software module in the ECU responsible for implementing the related control functions of that parameter (e.g., the function for calculating the fuel injection quantity) will have its parameter reading logic redirected to the specified address in the volatile memory to obtain the parameter value during the current power-on cycle, instead of reading from the default non-volatile memory. However, the effect of this target parameter value in the volatile memory is temporary. When the ECU is reset for any reason (such as vehicle power-on / off, receiving a set reset / restart command, or system failure restart), all contents in the volatile memory are automatically cleared by hardware. When the ECU's control logic is reinitialized, it will load the specific values ​​of each parameter from the non-volatile memory again, thereby automatically and error-free restoring the configuration state before the modification, without any additional operation, which is convenient for technicians to debug and test.

[0080] If the parsed parameter configuration type identifier indicates the second configuration type (i.e., corresponding to persistent configuration), the ECU's control logic will perform a non-volatile write operation. In this case, the ECU will directly write the received new parameter value (target parameter value) to a fixed storage address pre-allocated for that parameter item in its non-volatile memory. Non-volatile memory, such as flash memory or electrically erasable programmable read-only memory, has the advantage of retaining data for a long time after power loss. Therefore, the parameter write operation under the second configuration type physically changes the charge state of the storage cell, thereby overwriting the parameter value previously stored at that address. After a successful write, the ECU's control logic will read and use this new value from the non-volatile memory address within the current operating cycle. Furthermore, until a new parameter configuration instruction for that parameter item is received, regardless of how many times the ECU undergoes resets, power outages, and power-on cycles, the parameter value loaded from the non-volatile memory during ECU operation will always be the newly written value from this parameter configuration operation.

[0081] By introducing a parameter configuration type identifier into the parameter configuration command and distinguishing between volatile and non-volatile memory areas within the target ECU, this embodiment allows technicians to select a first configuration type for calibration parameters requiring short-term verification during actual debugging, without altering the ECU firmware structure. This automatically restores the original configuration after ECU reset, preventing long-term residual debugging parameters from affecting normal vehicle operation. Alternatively, a second configuration type can be selected for verified calibration results requiring persistence, ensuring the adjusted parameters are saved non-volatilely and remain effective in subsequent ECU operation. Therefore, this embodiment avoids the cumbersome process of recompiling and flashing firmware for each parameter adjustment, significantly improving the flexibility and efficiency of ECU parameter adjustment during vehicle testing, calibration, and fault diagnosis.

[0082] To implement the vehicle ECU parameter configuration method of this application embodiment, this application embodiment also provides a vehicle ECU parameter configuration device, such as... Figure 2 As shown, the device includes:

[0083] The communication connection establishment unit 201 is used to establish a communication connection between the terminal device and the vehicle, so that the terminal device can access the parameter configuration interface built into the vehicle through the communication connection;

[0084] The operation receiving unit 202 is used to receive parameter configuration operations for target parameters in the target ECU through the parameter configuration interface;

[0085] The instruction receiving unit 203 is used to generate a parameter configuration instruction based on the parameter configuration operation and send the parameter configuration instruction to the target ECU to update the target parameters of the target ECU according to the parameter configuration instruction.

[0086] In one embodiment, the communication connection establishment unit 201 is specifically used to: enable the vehicle's wireless access point, set a service set identifier and network access credentials to identify the vehicle, so that the terminal device can access the vehicle's internal network and access the vehicle's built-in parameter configuration interface after inputting the correct access authentication credentials through the communication connection.

[0087] In one embodiment, the device further includes: an interface rendering unit; the interface rendering unit is specifically used to: run a network server program based on a preset operating system; the network server program responds to access requests from the terminal device, loads interface resource files stored in a preset path, and returns the interface resource files to the terminal device to render and display the parameter configuration interface on the terminal device.

[0088] In one embodiment, the operation receiving unit 202 is specifically used to: receive the account identifier and authentication password input by the user in the parameter configuration interface; compare the account identifier and authentication password with the pre-stored legitimate account information; if the comparison is successful, allow the terminal device to access the parameter configuration interface; if the comparison fails, deny the terminal device access to the parameter configuration interface.

[0089] In one embodiment, the operation receiving unit 202 is specifically used to: read a pre-stored vehicle ECU configuration table; wherein the vehicle ECU configuration table records the identification information of each ECU in the vehicle and the configurable parameter information corresponding to each ECU; generate a target ECU list and configurable parameter items corresponding to each target ECU based on the records in the vehicle ECU configuration table, and return the target ECU list and the configurable parameter items to the parameter configuration interface for display.

[0090] In one embodiment, the operation receiving unit 202 is specifically configured to: receive a selection operation for selecting a target ECU and target parameters through the parameter configuration interface, thereby determining the target ECU and the target parameters, and sending a parameter reading request to the target ECU; obtain the current value of the target parameters returned by the target ECU, and display the current value of the target parameters on the parameter configuration interface; and receive the target parameter value and parameter configuration type identifier set for the target parameters through the parameter configuration interface.

[0091] In one embodiment, the instruction receiving unit 203 is specifically configured to: if the parameter configuration type identifier indicates a first configuration type, update the target parameter value in the volatile memory corresponding to the target ECU, so that the target ECU can operate according to the target parameter value in the current operating cycle; wherein, after the target ECU is reset, the target parameter is restored to the original parameter value stored in the non-volatile memory; if the parameter configuration type identifier indicates a second configuration type, write the target parameter value into the non-volatile memory of the target ECU, so that the target ECU can operate according to the target parameter value in the current operating cycle and after the target ECU is reset.

[0092] It should be noted that the vehicle ECU parameter configuration device provided in the above embodiments is only illustrated by the division of the above-described program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. Furthermore, the vehicle ECU parameter configuration device and the vehicle ECU parameter configuration method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process is detailed in the method embodiments, which will not be repeated here.

[0093] Based on the hardware implementation of the above program modules, and in order to implement the vehicle ECU parameter configuration method provided in this application embodiment, this application embodiment also provides a computer device, such as... Figure 3 As shown, computer device 300 includes:

[0094] Central processing unit 301, memory 302, and input / output interface 303;

[0095] The memory 302 is a short-term storage memory or a persistent storage memory;

[0096] The central processing unit 301 is configured to communicate with the memory 302 and execute the instructions in the memory 302 to perform any of the above-described vehicle ECU parameter configuration methods.

[0097] Of course, in practical applications, the various components in the computer device 300 are coupled together through a bus system 304. It is understood that the bus system 304 is used to realize communication between these components. In addition to a data bus, the bus system 304 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 3 The general designated all buses as Bus System 304.

[0098] The memory 302 in this embodiment is used to store various types of data to support the operation of the computer device 300. Examples of such data include any computer program used to operate on the computer device 300.

[0099] It is understood that when the processor in the computer device described above executes the computer program, it can also realize the functions of each unit in the corresponding device embodiments described above, which will not be repeated here. Exemplarily, the computer program can be divided into one or more modules / units, one or more modules / units are stored in memory and executed by the processor to complete the various embodiments of this application. One or more modules / units can be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the computer device. For example, the computer program can be divided into units in the aforementioned computer device, and each unit can implement the specific functions described in the corresponding computer device above.

[0100] Computer equipment can be desktop computers, laptops, handheld computers, and cloud servers, among other computing devices. Computer equipment may include, but is not limited to, processors and memory. Those skilled in the art will understand that processors and memory are merely examples of computer equipment and do not constitute a limitation on the computer equipment. It may include more or fewer components, or combinations of certain components, or different components. For example, computer equipment may also include input / output devices, network access devices, buses, etc.

[0101] A 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. A general-purpose processor can be a microprocessor or any conventional processor. The processor is the control center of a computer device, connecting all parts of the computer device through various interfaces and lines.

[0102] Memory can be used to store computer programs and / or modules. The processor performs various functions of the computer device by running or executing the computer programs and / or modules stored in the memory, and by accessing data stored in the memory. Memory can primarily include a program storage area and a data storage area. The program storage area can store the operating system, at least one application program required for a function, etc.; the data storage area can store data created based on terminal usage, etc. Furthermore, memory can include high-speed random access memory, and can also include non-volatile memory, such as hard disks, RAM, plug-in hard disks, smart media cards (SMC), secure digital cards (SD), flash cards, at least one disk storage device, flash memory device, or other volatile solid-state storage devices.

[0103] This application also provides a computer-readable storage medium storing a computer program thereon. When the computer program is executed by a processor, it performs the vehicle ECU parameter configuration method described in the first aspect or any specific implementation of the first aspect of this application.

[0104] This application also provides a computer program product storing a computer program / instruction, which, when executed by a processor, is used to implement the vehicle ECU parameter configuration method described in the first aspect or any specific implementation of the first aspect of this application.

[0105] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0106] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0107] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0108] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0109] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for configuring vehicle ECU parameters, characterized in that, include: Establish a communication connection between the terminal device and the vehicle, so that the terminal device can access the parameter configuration interface built into the vehicle through the communication connection; The parameter configuration interface receives parameter configuration operations for target parameters in the target electronic controller (ECU). Based on the parameter configuration operation, a parameter configuration instruction is generated and sent to the target ECU to update the target parameters of the target ECU according to the parameter configuration instruction.

2. The method according to claim 1, characterized in that, The step of establishing a communication connection between the terminal device and the vehicle, enabling the terminal device to access the vehicle's built-in parameter configuration interface through the communication connection, includes: Enable the vehicle's wireless access point, and set a service set identifier and network access credentials to identify the vehicle, so that the terminal device can access the vehicle's internal network and access the vehicle's built-in parameter configuration interface after entering the correct access authentication credentials through the communication connection.

3. The method according to claim 1, characterized in that, The method further includes: The network server program runs on the pre-installed operating system. The network server program responds to the access request from the terminal device, loads the interface resource file stored in the preset path, and returns the interface resource file to the terminal device to render and display the parameter configuration interface on the terminal device.

4. The method according to claim 1, characterized in that, Before receiving parameter configuration operations for target parameters in the target ECU through the parameter configuration interface, the method further includes: The parameter configuration interface receives the user's account identifier and authentication password. The account identifier and authentication password are compared with the pre-stored legitimate account information. If the comparison is successful, the terminal device is allowed to access the parameter configuration interface; if the comparison fails, the terminal device is denied access to the parameter configuration interface.

5. The method according to claim 1, characterized in that, After establishing a communication connection between the terminal device and the vehicle, enabling the terminal device to access the vehicle's built-in parameter configuration interface via the communication connection, the method further includes: Read the pre-stored vehicle ECU configuration table; wherein the vehicle ECU configuration table records the identification information of each ECU in the vehicle and the configurable parameter information corresponding to each ECU; Based on the records in the vehicle ECU configuration table, a target ECU list and configurable parameter items corresponding to each target ECU are generated, and the target ECU list and the configurable parameter items are returned to the parameter configuration interface for display.

6. The method according to claim 1, characterized in that, The step of receiving parameter configuration operations for target parameters in the target ECU through the parameter configuration interface includes: The parameter configuration interface receives a selection operation for selecting a target ECU and target parameters, thereby determining the target ECU and target parameters, and sending a parameter read request to the target ECU. Obtain the current value of the target parameter returned by the target ECU, and display the current value of the target parameter in the parameter configuration interface; The parameter configuration interface receives the target parameter value and parameter configuration type identifier for the target parameter settings.

7. The method according to any one of claims 1 or 6, characterized in that, The parameter configuration instruction includes at least a target parameter value and a parameter configuration type identifier; updating the target parameter of the target ECU according to the parameter configuration instruction includes: If the parameter configuration type identifier indicates a first configuration type, the target parameter value is updated in the volatile memory corresponding to the target ECU so that the target ECU can operate according to the target parameter value in the current operating cycle; wherein, after the target ECU is reset, the target parameter is restored to the original parameter value stored in the non-volatile memory; If the parameter configuration type identifier indicates a second configuration type, the target parameter value is written into the non-volatile memory of the target ECU so that the target ECU can operate according to the target parameter value during the current operating cycle and after the target ECU is reset.

8. A vehicle ECU parameter configuration device, characterized in that, include: A communication connection establishment unit is used to establish a communication connection between a terminal device and a vehicle, so that the terminal device can access the parameter configuration interface built into the vehicle through the communication connection. An operation receiving unit is used to receive parameter configuration operations for target parameters in the target ECU through the parameter configuration interface; The instruction receiving unit is configured to generate a parameter configuration instruction based on the parameter configuration operation and send the parameter configuration instruction to the target ECU to update the target parameters of the target ECU according to the parameter configuration instruction.

9. A computer device, characterized in that, include: Central processing unit, memory, and input / output interfaces; The memory is either a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it is used to implement the method as described in any one of claims 1 to 7.

Images