Method for Restoring the Factory Settings of a Vehicle Controller

Through the diagnostic instrument, the factory configuration file is parsed, and the factory settings of the vehicle controller are identified and restored, the problem of difficulty in upgrading the on-board controller after replacement in the after-sales market is solved, and a controllable upgrade process is realized, which improves customer satisfaction.

CN114859860BActive Publication Date: 2025-07-29CHERY AUTOMOBILE CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202210454356.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-04-27
Publication Date
2025-07-29
Estimated Expiration
2042-04-27

AI Technical Summary

Technical Problem

The existing technology cannot effectively solve the difficulty of software upgrade after the replacement of in-vehicle controllers in the after-sales market.

Method used

Connect the vehicle through the diagnostic instrument, analyze the factory configuration file, identify the assembly information and software version number of each controller of the vehicle, judge the consistency, and automatically restore the controller's factory settings based on the factory configuration file to build a reasonable upgrade process.

Benefits of technology

It realizes automatic factory reset of on-board controllers in the after-sales market, ensuring that the upgrade process is controllable and improving customer satisfaction.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114859860B_ABST
    Figure CN114859860B_ABST
Patent Text Reader

Abstract

The object of the present invention is to provide a method for restoring the factory settings of a vehicle controller. Based on the assembly part number, application / calibration software part number, and application / calibration software version number, a complete and reasonable method for identifying and restoring the factory settings of the controller software is proposed according to the subordinate relationship between the controller part number and the version number. The implementation process is based on the factory configuration file to ensure that the diagnostic instrument can automatically complete the restoration of the factory settings after replacing the in-vehicle controller in the aftermarket, and a reasonable upgrade process is constructed to meet the needs of end users and ensure that the process is controllable.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of automotive electronics, and more specifically, to a method for restoring the vehicle controller to its factory settings. Background Art

[0002] With the continuous advancement of the new four modernizations of automobiles, the number of in-vehicle control units has shown an explosive growth, and the functions integrated in the system have become increasingly complex. At the same time, due to software-related problems, large-scale recalls by vehicle manufacturers in the after-sales market occur frequently. In order to improve customer satisfaction in the after-sales market, vehicle manufacturers usually take corresponding measures to ensure the controlled software upgrade of the controller. Especially when the controller is replaced, how to accurately and reliably restore the vehicle to its factory state is crucial for the implementation of the remote flashing function.

[0003] The patent with the title "Method for Remote Upgrade of Vehicle Terminal and Internet of Vehicles System" (CN103312786A) first queries the version number of the vehicle terminal and determines whether the current software version of the vehicle terminal needs to be upgraded. If an upgrade is required, an upgrade request is sent to the vehicle terminal. After receiving the response message from the vehicle terminal indicating permission to receive the upgrade data packet, the upgrade data packet is sent to the vehicle terminal through the mobile communication network. Since there may be differences in the current software versions of vehicle terminals, a large number of versions of upgrade data packets are required, which may seriously lead to incorrect sending of upgrade data packets and inability to upgrade.

[0004] The patent with the title "Method, Device, Computer Equipment and Storage Medium for Online Upgrade of Vehicle Controller" (CN112804698A) obtains an upgrade data file for the vehicle controller with a specific data structure. In addition to global configuration information and upgrade data, the upgrade data file for the vehicle controller also contains data configuration information set before the upgrade data. The data configuration information includes the configuration information of the upgrade data in the upgrade file for the vehicle controller. After obtaining the upgrade data file for the vehicle controller with this specific data structure, the data configuration information can be parsed first, and after parsing the data configuration information, a judgment can be made on the upgrade data in advance, so as to parse the upgrade data faster. Subsequently, the vehicle controller can be upgraded online according to the global configuration information and the upgrade data. It can be seen that this solution first parses the data configuration information and makes a judgment on the upgrade data in advance after parsing, so as to parse the upgrade data faster, and then the vehicle controller can be upgraded online. It can be seen that the online upgrade package for the vehicle controller also has diverse contents.

[0005] The name is "An OTA Upgrade Method and Upgrade Device" (CN 113805920 A). If it is determined that the upgrade mode is the OTA mode based on the wake-up information, the first vehicle is controlled to power on, and the version information of the in-vehicle terminal of the first vehicle is queried; if it is determined that the version information of the in-vehicle terminal meets the upgrade requirements, the upgrade data packet required for the current upgrade task sent by the TSP platform is received, and the current upgrade task corresponds to the first in-vehicle terminal in the first vehicle; the relevant parameters of the first vehicle are obtained; based on the upgrade data packet required for the current upgrade task and the relevant parameters, the first in-vehicle terminal is

[0006] OTA upgraded. This solution also upgrades the vehicle based on the upgrade data packet required for the current upgrade task determined by the in-vehicle terminal version information.

[0007] None of the above-mentioned prior arts can solve the problem of difficult upgrade after replacing parts of the in-vehicle controller in the aftermarket. Summary of the Invention

[0008] The object of the present invention is to provide a method for restoring the factory settings of a vehicle controller.

[0009] The technical solution adopted is: the diagnostic instrument OBD connector is connected to the vehicle. After the diagnostic instrument is connected to the network, the diagnostic instrument serial number authentication information is uploaded to the remote flashing background for legality verification. After the background verification is passed, the following steps are carried out:

[0010] (1) Analyze the vehicle factory configuration file: After the diagnostic instrument is verified to be legal, the vehicle factory configuration file is obtained from the remote flashing background. The factory configuration file corresponds one-to-one with the vehicle VIN code, and the file contains the assembly information, software configuration information, controller part number, software / hardware version number of each controller of the specified vehicle, and the configuration information associated with the vehicle at the time of factory shipment of the flashing file type;

[0011] After the diagnostic instrument analyzes the vehicle factory configuration and obtains the relevant information of each controller of the vehicle, it scans each controller of the vehicle to determine whether the controller software settings need to be restored to the factory settings state online; [[ID=२१]] [[ID=२२]]

[0012] [[ID=२३]](2) Read controller information: The diagnostic instrument identifies the assembly information of each controller of the vehicle according to the factory configuration file, and sequentially reads the part number and version information of each controller of the actual vehicle. The part number and version information include the assembly part number, application software part number, calibration software part number, application software version number, and calibration software version number; [[ID=२४]] [[ID=२५]]

[0013] [[ID=२६]](3) Start judging the factory reset task: According to the assembly situation of each controller of the vehicle, sequentially judge the consistency between the actual part number and version of each controller and the part number and version in the factory configuration file; [[ID=२७]] [[ID=२८]]

[0014] (4)Assembly Part Number Judgment: Determine whether the actual assembly part number of the controller is consistent with the assembly part number in the factory configuration file. If they are consistent, continue to start the judgment process for the part number and version number of the application software and the part number and version number of the calibration software. If they are inconsistent, end the judgment process of the current controller and enter the judgment process of the next controller.

[0015] Based on the assembly part number, application / calibration software part number, and application / calibration software version number, the above technical solution proposes a complete and reasonable method for identifying and restoring the factory settings of the controller software according to the subordinate relationship of the controller part number and version number. The implementation process is based on the factory configuration file to ensure that the in-vehicle controller can automatically restore the factory settings using a diagnostic instrument after replacing parts in the aftermarket, and constructs a reasonable upgrade process to meet the needs of end users and ensure that the process is controllable. Brief Description of the Drawings

[0016] Figure 1 It is the logic diagram of the present invention. Detailed Embodiment

[0017] Connect the diagnostic instrument OBD connector to the vehicle. After the diagnostic instrument is connected to the network, upload the diagnostic instrument serial number authentication information to the remote flashing background for verification of legality. Only after the background verification is passed can the controller software be restored to the factory settings online. The specific identification process is as follows:

[0018] (1)Analyze the vehicle factory configuration file: After the diagnostic instrument is verified to be legal, obtain the vehicle factory configuration file from the remote flashing background. The factory configuration file corresponds one-to-one with the vehicle VIN code, and the file contains the assembly information, software configuration information, controller part number, software / hardware version number, flashing file, and other configuration information related to the vehicle when it leaves the factory. After the diagnostic instrument analyzes the vehicle factory configuration and obtains the relevant information of each controller of the vehicle, scan each controller of the vehicle according to the preset logic to determine whether the controller software needs to be restored to the factory settings online.

[0019] (2)Read controller information: The diagnostic instrument identifies the assembly information of each controller of the vehicle according to the factory configuration file, and sequentially reads the part number and version information of each controller of the actual vehicle, including: assembly part number, application software part number, calibration software part number, application software version number, and calibration software version number, to prepare for the subsequent comparison of part numbers and version numbers.

[0020] (3)Start the judgment of the factory reset task: According to the assembly situation of each controller of the vehicle, sequentially judge the consistency between the actual part number and version of each controller and the part number and version in the factory configuration file.

[0021] (4)Assembly part number judgment: Judge whether the actual assembly part number of the controller is consistent with the assembly part number in the factory configuration file. If they are consistent, continue to judge the consistency of the application software part number. If they are inconsistent, end the judgment process of the current controller and enter the judgment process of the next controller.

[0022] (5)Readability judgment of application software part number: Considering that the controller may not be able to read the application software part number (for example, the controller software is abnormal and cannot be read, the controller does not develop the application software part number, etc.), to ensure the consistency of the identification process, it is necessary to judge the readability of the application software part number. If it can be read, then judge its consistency. Otherwise, enter the judgment process of the application software version number.

[0023] (6)Application software part number judgment: Judge whether the actual application software part number of the controller is consistent with the application software part number in the factory configuration file. If they are consistent, continue to judge the application software version number. If they are inconsistent, end the judgment process of the current controller and enter the judgment process of the next controller.

[0024] (7)Readability judgment of application software version number: Similar to step (5), it is necessary to judge the readability of the application software version number. If it can be read, then judge its consistency. Otherwise, enter the judgment process of the application software refresh file.

[0025] (8)Application software version number judgment: Judge whether the actual application software version number of the controller is consistent with the application software version number in the factory configuration file. If they are consistent, it is considered that the controller does not need to upgrade the application software, and continue to judge the calibration software. If they are inconsistent, enter the judgment process of the application software refresh file.

[0026] (9)Application software refresh file judgment: The diagnostic instrument searches for the corresponding application software refresh file in the vehicle factory configuration file. If the corresponding file can be found, continue to judge the calibration software refresh file. If the corresponding file cannot be found, end the judgment process of the current controller and enter the judgment process of the next controller.

[0027] (10)Calibration software refresh file judgment: The diagnostic instrument searches for the corresponding calibration software refresh file in the vehicle factory configuration file. If the corresponding file can be found, execute step (11). If the corresponding file cannot be found, execute step (12).

[0028] (11)Refresh the "application + calibration" software.

[0029] (12)Refresh the "application" software.

[0030] (13)Readability judgment of calibration software part number: Similar to step (5), it is necessary to judge the readability of the calibration software part number. If it can be read, then judge its consistency. Otherwise, enter the judgment process of the calibration software version number.

[0031] (14)Judgment of calibration software part number: Judge whether the actual calibration software part number of the controller is consistent with the calibration software part number in the factory configuration file. If they are consistent, continue to judge the calibration software version number. If they are inconsistent, end the judgment process of the current controller and enter the judgment process of the next controller.

[0032] (15)Readability judgment of calibration software version number: Similar to step (5), it is necessary to judge the readability of the calibration software version number. If it can be read, then judge its consistency. Otherwise, enter the judgment process of the calibration software refresh file.

[0033] (16)Judgment of calibration software version number: Judge whether the actual calibration software version number of the controller is consistent with the calibration software version number in the factory configuration file. If they are consistent, it is considered that the controller does not need to upgrade any software, end the judgment process of the current controller, and enter the judgment process of the next controller. If they are inconsistent, refresh the "calibration" software of the controller.

[0034] (17)Judgment of calibration software refresh file with the same version: After the calibration software version number cannot be read, the diagnostic instrument searches for the corresponding calibration software refresh file in the vehicle factory configuration file. If the corresponding file can be found, then refresh the "calibration" software. If the corresponding file cannot be found, end the judgment process of the current controller and enter the judgment process of the next controller.

[0035] (18)The controller meets the software factory reset condition, and refresh the "calibration" software.

[0036] (19)End the judgment process of the current controller.

[0037] (20)Enter the judgment process of the next controller.

Claims

1. A method for restoring the factory settings of a vehicle controller, characterized in that: The diagnostic instrument's OBD connector is connected to the vehicle. After the diagnostic instrument is connected to the network, it uploads the authentication information of the diagnostic instrument's serial number to the remote flashing background for legality verification. After the background verification passes, the following steps are carried out: (1) Analyze the vehicle's factory configuration file: After the diagnostic instrument is verified to be legal, it obtains the vehicle's factory configuration file from the remote flashing background. The factory configuration file corresponds one-to-one with the vehicle's VIN code. The file contains the assembly information, software configuration information, controller part numbers, software / hardware version numbers of each controller of the specified vehicle, and the configuration information associated with the vehicle at the time of factory production for the flashing file type; After the diagnostic instrument analyzes the vehicle's factory configuration and obtains the relevant information of each controller of the vehicle, it scans each controller of the vehicle to determine whether the controller software settings need to be restored to the factory settings state online; (2) Read controller information: The diagnostic instrument identifies the assembly information of each controller of the vehicle according to the factory configuration file, and sequentially reads the part number and version information of each controller in the actual vehicle. The part number and version information include the assembly part number, application software part number, calibration software part number, application software version number, and calibration software version number; (3) Start the judgment of the factory reset task: According to the assembly situation of each controller of the vehicle, sequentially judge the consistency between the actual part number and version of each controller and the part number and version in the factory configuration file; (4) Assembly part number judgment: Judge whether the actual assembly part number of the controller is consistent with the assembly part number in the factory configuration file. If they are consistent, continue to start the judgment program for the application software part number and version number, and the part number and version number of the calibration software. If they are inconsistent, end the judgment process of the current controller and enter the judgment process of the next controller.

2. The method for restoring the factory settings of a vehicle controller according to claim 1, wherein: (5) Readability judgment of the application software part number: Judge the readability of the application software part number. If it can be read, then judge its consistency. Otherwise, enter the judgment process of the application software version number; (6) Application software part number judgment: Judge whether the actual application software part number of the controller is consistent with the application software part number in the factory configuration file. If they are consistent, continue to judge the application software version number. If they are inconsistent, end the judgment process of the current controller and enter the judgment process of the next controller.

3. The method for restoring the factory settings of a vehicle controller according to claim 2, wherein: (7) Readability judgment of the application software version number: Judge the readability of the application software version number. If it can be read, then judge its consistency. Otherwise, enter the judgment process of the application software refresh file; (8) Application software version number judgment: Judge whether the actual application software version number of the controller is consistent with the application software version number in the factory configuration file. If they are consistent, it is considered that the controller does not need to upgrade the application software, and continue to judge the calibration software. If they are inconsistent, enter the judgment process of the application software refresh file.

4. The method for restoring the factory settings of a vehicle controller according to claim 3, wherein: (9)Judgment of application software refresh file: The diagnostic instrument searches for the corresponding application software refresh file in the vehicle factory configuration file. If the corresponding file can be found, continue to judge the calibration software refresh file. If the corresponding file cannot be found, end the judgment process of the current controller and enter the judgment process of the next controller; (10)Judgment of calibration software refresh file: The diagnostic instrument searches for the corresponding calibration software refresh file in the vehicle factory configuration file. If the corresponding file can be found, execute step (11). If the corresponding file cannot be found, execute step (12); (11)Refresh the "application + calibration" software; (12)Refresh the "application" software.

5. The method for restoring the vehicle controller to the factory settings according to claim 4, characterized in that: (13)Readability judgment of calibration software part number: It is necessary to judge the readability of the calibration software part number. If it can be read, then judge its consistency. Otherwise, enter the judgment process of the calibration software version number.

6. The method for restoring the vehicle controller to the factory settings according to claim 5, characterized in that: (14)Calibration software part number judgment: Judge whether the actual calibration software part number of the controller is consistent with the calibration software part number in the factory configuration file. If they are consistent, continue to judge the calibration software version number. If they are inconsistent, end the judgment process of the current controller and enter the judgment process of the next controller.

7. The method for restoring the vehicle controller to the factory settings according to claim 6, characterized in that: (15)Readability judgment of calibration software version number: Similar to step (5), it is necessary to judge the readability of the calibration software version number. If it can be read, then judge its consistency. Otherwise, enter the judgment process of the calibration software refresh file; (16)Calibration software version number judgment: Judge whether the actual calibration software version number of the controller is consistent with the calibration software version number in the factory configuration file. If they are consistent, it is considered that the controller does not need to upgrade any software, end the judgment process of the current controller, and enter the judgment process of the next controller. If they are inconsistent, refresh the "calibration" software of the controller.

8. The method for restoring the vehicle controller to the factory settings according to claim 7, characterized in that: (17)Judgment of calibration software refresh file with the same version: After the calibration software version number cannot be read, the diagnostic instrument searches for the corresponding calibration software refresh file in the vehicle factory configuration file. If the corresponding file can be found, refresh the "calibration" software. If the corresponding file cannot be found, end the judgment process of the current controller and enter the judgment process of the next controller.

9. The method for restoring the vehicle controller to the factory settings according to claim 8, characterized in that: (18)When the controller meets the software restoration to factory conditions, refresh the "calibration" software; (19)End the judgment process of the current controller.

Citation Information

Patent Citations

  • Vehicle-mounted terminal remote upgrading method and car networking system

    CN103312786A

  • On-line upgrading method and device for vehicle-mounted controller, computer equipment and storage medium

    CN112804698A

  • OTA upgrading method and upgrading device

    CN113805920A

  • Vehicle diagnostic device calibration software configuration administrative system and method

    CN101266492A

  • Remote after-service on-line ECU refresh method and diagnosis apparatus

    CN105094901A