Instrument mileage backup synchronization method and system and vehicle

Abstract

The invention provides an instrument mileage backup synchronization method and system and a vehicle, and belongs to the field of vehicle instruments. The method comprises the following steps: an external detector sends a backup request to an instrument and each backup controller; the instrument and each backup controller upload the recorded mileage value to a vehicle network matrix, and the mileage value is read by an external detector; the external detector sends the read mileage values of the backup controllers to the instrument, and the instrument judges whether the backup controllers meet backup requirements or not by combining the mileage values stored in the instrument; and for the backup controller meeting the backup requirement, the external detector writes the instrument mileage value into the corresponding backup controller so as to rewrite the original mileage value stored in the backup controller. According to the invention, the external equipment is used as a bridge for triggering the backup request and information transmission, so that the situation that mileage values need to be compared every time the instrument is powered on is avoided, the calculation resources of the instrument are saved, and the situation that the mileage is mistakenly rewritten is reduced.

Description

Technical Field

[0001] The present invention belongs to the field of vehicle instruments, and in particular, relates to an instrument mileage backup synchronization method, system and vehicle. Background Art

[0002] Currently, vehicles need to replace instruments to solve problems such as failures, accidents, and upgrades, which causes the ODO (mileage) display on the instrument to be reset to zero, causing inconvenience to users and others, and making it impossible to simply and clearly identify the vehicle's specific mileage.

[0003] The existing instrument backup synchronization method has certain drawbacks and limitations, with the coverage rate of scenarios being less than 80% and causing misidentification.

[0004] In the existing technology, the backup controller usually directly transmits the mileage value stored in its own backup to the meter, and then the meter compares it. This will result in: every time the meter is powered on, it needs to compare the value, which will occupy the startup calculation time at this time, resulting in the risk of BUG. However, the value of the vehicle will only change within two times during the period from scrapping to scrapping, and in most cases, the value of the vehicle will not change; so there is no need to add unnecessary calculations and risks to each vehicle. At the same time, when the backup controller is troubleshooting, the mileage may be mistakenly rewritten, resulting in user complaints and commercial vehicles cannot be sold. Summary of the invention

[0005] The present invention aims to overcome the shortcomings of the prior art and proposes an instrument mileage backup synchronization method, system and vehicle to achieve the following purposes: using an external device as a bridge to trigger backup requests and information transmission, avoiding the need to compare mileage values ​​every time the instrument is powered on, saving the instrument's computing resources, and reducing the occurrence of mileage being accidentally rewritten.

[0006] In order to achieve the above object, the technical solution adopted by the present invention is:

[0007] A method for synchronizing instrument mileage backup, the method comprising:

[0008] Step S1, the external detector sends a backup request to the meter and each backup controller to start mileage backup;

[0009] Step S2, the meter and each backup controller upload the recorded mileage value to the vehicle network matrix and read it through an external detector;

[0010] Step S3, the external detector sends the mileage values ​​of each backup controller read to the meter, and the meter then determines whether the backup controller meets the backup requirements in combination with the mileage values ​​stored in the meter;

[0011] Step S4: For the backup controller that meets the backup requirements, the meter mileage value is written into the corresponding backup controller through an external detector to overwrite the original mileage value stored in the backup controller.

[0012] Preferably, the method further comprises:

[0013] Step S5: The external detector reads back the backup controller that has completed the backup to verify whether the backup is successful.

[0014] Preferably, the backup controller includes a body controller, an engine controller, a motor controller, and an ignition controller.

[0015] Preferably, the backup requirements in step S2 include:

[0016] (1) If the current meter mileage value is the same as the mileage value stored in all backup controllers, and the mileage values ​​stored in all backup controllers are also the same, it is considered that the backup requirements are not met and the backup controller is not rewritten;

[0017] (2) If the current meter mileage value is greater than the mileage value stored in all backup controllers, and the mileage values ​​stored in all backup controllers are the same, it is considered that the backup requirements are not met and the backup controller is not rewritten;

[0018] (3) If the current meter mileage value is less than the mileage values ​​stored in all backup controllers, and the difference between them is less than a preset coefficient, it is deemed that the backup requirement is not met and the backup controller is not rewritten. The mileage values ​​stored in all backup controllers are the same.

[0019] (4) If the current meter mileage value is less than the mileage values ​​stored in all backup controllers, but the difference between them is greater than or equal to the preset coefficient, it is considered that the backup requirements are met and all backup controllers are rewritten, wherein the mileage values ​​stored in all backup controllers are the same;

[0020] (5) If the current meter mileage value is the same as the mileage value stored in one backup controller, but the mileage values ​​stored in the other backup controllers are the same, and the current meter mileage value is greater than the mileage values ​​stored in the other backup controllers, it is considered that the backup requirements are not met and the backup controller is not rewritten;

[0021] (6) If the current meter mileage value is the same as the mileage value stored in one backup controller, but the mileage values ​​stored in the other backup controllers are the same, and the current meter mileage value is less than the mileage values ​​stored in the other backup controllers, it is deemed that the backup requirements are not met and the backup controller is not rewritten;

[0022] (7) If the current meter mileage value is less than the mileage value stored in all backup controllers, and there is at least one mileage value of the current meter mileage value and the mileage value stored in the backup controller whose difference is greater than or equal to the preset coefficient, it is considered that the backup requirements are met and all backup controllers are rewritten.

[0023] Preferably, the preset coefficient is determined by the maximum value of the mileage that can be reset to zero before the car leaves the factory.

[0024] Preferably, the instrument feeds back the judgment result of the corresponding backup requirement to the external detector to inform the user, and the user further decides whether to execute the backup rewrite of all backup controllers through the external detector.

[0025] At the same time, the present application also proposes an instrument mileage backup synchronization system, which is configured according to the above-mentioned instrument mileage backup synchronization method, and the system includes a vehicle instrument, a backup controller, and an external detector, and the external detector is connected to the vehicle instrument and the backup controller. Among them, the external detector adopts a 431 diagnostic instrument.

[0026] The present application also proposes a vehicle, which includes a device or system for applying the above-mentioned instrument mileage backup synchronization method.

[0027] The technical effects of the present invention are:

[0028] (1) When the meter is turned on, it needs to receive and judge a lot of content. However, the backup operation of the meter in this application is triggered by an external detector, which avoids the mileage value backup judgment every time the meter is powered on, avoids unnecessary calculations, and saves computing resources.

[0029] (2) The application covers 90% of the working conditions, among which whether to perform backup depends on the user's judgment, and will not cause the risk of accidental rewriting caused by instrument troubleshooting, component replacement, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 The present invention is a flowchart of an instrument mileage backup synchronization method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] The following is a further detailed description of the specific implementation of the present invention through the description of the embodiments with reference to the accompanying drawings, with the purpose of helping those skilled in the art to have a more complete, accurate and in-depth understanding of the inventive concept and technical solution of the present invention and to facilitate its implementation. In order to make the technical solution of the present invention clearer, the present invention is explained through the following embodiments.

[0032] A method for synchronizing instrument mileage backup, the process of which is as follows: Figure 1 shown.

[0033] Step S1: The external detector sends a backup request to the meter and each backup controller to start mileage backup.

[0034] The backup controller of this embodiment includes a body controller, an engine controller, a motor controller, an ignition controller, a vehicle controller, etc. The external detector of this embodiment adopts a 431 diagnostic instrument. The 431 diagnostic instrument is a commonly used automobile computer fault diagnosis device in the prior art and supports the UDS diagnostic protocol. It is a conventional device that any OEM or 4S store will have, and has the advantage of simple operation. In this embodiment, the 431 diagnostic instrument is configured to send a backup request to the meter and each backup controller to start the mileage backup, and at the same time can receive feedback from the meter and each backup controller to display it to the user. The external detector of this application only serves as a bridge between backup triggering and information transmission, and does not judge the backup of mileage values, which facilitates the configuration of the external detector and is more convenient for users to operate.

[0035] Step S2: After receiving the backup request from the external detector, the meter and each backup controller upload the recorded mileage value to the vehicle network matrix and read it through the external detector.

[0036] In this embodiment, the 431 diagnostic instrument can read the mileage values ​​recorded by the instrument and each backup controller by calling the $22 service of the UDS protocol. For example, the 431 diagnostic instrument reads the mileage values ​​of the backup controllers ICM (ignition controller), BCM (body controller), EMS (engine manager), and VCU (vehicle control unit), and the data identifier (DID) is recorded as 002E. The corresponding read diagnostic instruction is:

[0037] 7DF 0322002E 00000000 / / Read each value

[0038] 75A 0662006E xx xx xx 00 / / ICM feedback

[0039] 7700662006E xx xx xx 00 / / BCM feedback

[0040] 7E80662006E xx xx xx 00 / / EMS feedback

[0041] 7EA 0662006E xx xx xx 00 / / VCU feedback

[0042] Step S3: the external detector sends the mileage values ​​of each backup controller read to the meter, and the meter then determines whether the backup controller meets the backup requirements in combination with the mileage values ​​stored in the meter.

[0043] In this embodiment, the mileage value of the meter is represented by V1, the mileage value of the body controller is represented by V2, the mileage value of the transmitter or motor controller is represented by V3, and the mileage value of other backup controllers is represented by VN. Based on the backup requirements of this embodiment, the method of this application can cover 90% of the working conditions. The specific backup requirements include:

[0044] (1) If the current meter mileage value is the same as the mileage value stored in all backup controllers, and the mileage values ​​stored in all backup controllers are also the same, it is considered that the backup requirements are not met and the backup controller is not rewritten, that is: V1 = V2 = V3 = VN.

[0045] (2) If the current meter mileage value is greater than the mileage values ​​stored in all backup controllers, and the mileage values ​​stored in all backup controllers are the same, it is considered that the backup requirements are not met and the backup controller is not rewritten, that is: V1>V2=V3=VN.

[0046] (3) If the current meter mileage value is less than the mileage values ​​stored in all backup controllers, and the difference between them is less than the preset coefficient, it is considered that the backup requirements are not met and the backup controller is not rewritten. The mileage values ​​stored in all backup controllers are the same, that is, V1<V2=V3=VN, and the difference between them is less than the preset coefficient Y.

[0047] (4) If the current instrument mileage value is less than the mileage value stored in all backup controllers, but the difference between them is greater than or equal to the preset coefficient, it is considered that the backup requirements are met and all backup controllers are rewritten, where the mileage values ​​stored in all backup controllers are the same, that is: V1<V2=V3=VN, and the difference between them is greater than or equal to the preset coefficient Y.

[0048] (5) If the current meter mileage value is the same as the mileage value stored in one backup controller, but the mileage values ​​stored in the remaining backup controllers are the same, and the current meter mileage value is greater than the mileage values ​​stored in the remaining backup controllers, it is considered that the backup requirements are not met and the backup controller is not rewritten, that is: V1=V2>V3=VN.

[0049] (6) If the current meter mileage value is the same as the mileage value stored in one backup controller, but the mileage values ​​stored in the remaining backup controllers are the same, and the current meter mileage value is less than the mileage values ​​stored in the remaining backup controllers, it is considered that the backup requirements are not met and the backup controller is not rewritten, that is: V1 = V2 < V3 = VN.

[0050] (7) If the current instrument mileage value is less than the mileage value stored in all backup controllers, and there is at least one current instrument mileage value and the mileage value stored in the backup controller whose difference is greater than or equal to the preset coefficient, it is considered that the backup requirements are met and all backup controllers are rewritten, for example: V1<(V2>V3=VN), where there is at least one current instrument mileage value and the mileage value stored in the backup controller whose difference is greater than or equal to the preset coefficient.

[0051] In this embodiment, the preset coefficient Y is determined by the maximum value of the mileage that can be reset before the car leaves the factory. Assuming that the maximum value of the mileage that can be reset before the car leaves the factory is set to 200 kilometers, the mileage value can be set to 0 for cars with a mileage less than 200 kilometers.

[0052] Furthermore, the instrument will feed back the judgment result of the corresponding backup requirement to the external detector to inform the user, and the user will further decide whether to execute the backup rewrite of all backup controllers through the external detector. That is, whether to perform backup depends on the user's judgment, and there will be no risk of erroneous rewriting caused by instrument troubleshooting, part replacement, etc.

[0053] Step S4: For the backup controller that meets the backup requirements, the meter mileage value is written into the corresponding backup controller through an external detector to overwrite the original mileage value stored in the backup controller.

[0054] In this embodiment, when the user determines that the backup rewrite is possible, for the backup controller that meets the backup requirements, the 431 diagnostic instrument writes the meter mileage value into the backup controller that needs to be backed up through the $2E service of the UDS protocol. Assuming that the meter mileage value is 1000KM, the data identifier (DID) written is 002E, and the backup controller written is ICM, the corresponding backup instructions are as follows:

[0055] 74A 0210030000000000

[0056] 75A 0250030000000000

[0057] 74A 0227030000000000

[0058] 75A 0267030000000000

[0059] 74A 0227040000000000

[0060] 75A 0267040000000000

[0061] 74A 052E 002E 03E80000

[0062] 75A 036E 002E 00000000

[0063] To ensure the success of the backup, the present embodiment further reads back the backup controller that has completed the backup to verify whether the backup is successful, that is, the method of the present application further includes:

[0064] Step S5: The external detector reads back the backup controller that has completed the backup to verify whether the backup is successful.

[0065] In this embodiment, the 431 diagnostic instrument calls the $22 service of the UDS protocol again to read the mileage value of the backup controller. Taking the ICM readback as an example, the positive and negative response instructions obtained by reading back whether the ICM is written correctly are as follows:

[0066] Positive response:

[0067] 74A 0210030000000000

[0068] 75A 0250030000000000

[0069] 74A 0322002E 00000000

[0070] 75A 0562002E 03E80000

[0071] Negative response:

[0072] 74A 0210030000000000

[0073] 75A 0250030000000000

[0074] 74A 0322002E 00000000

[0075] 75A 0462002E XX 000000

[0076] Wherein, XX indicates the reason why the readback verification failed.

[0077] At the same time, the present application also proposes an instrument mileage backup synchronization system, which is configured according to the above-mentioned instrument mileage backup synchronization method. The system includes a vehicle instrument, a backup controller, and an external detector, and the external detector is connected to the vehicle instrument and the backup controller. Among them, the external detector is used to send a backup request to the instrument to trigger the mileage backup, and read the mileage value recorded in the vehicle instrument and the backup controller from the vehicle network matrix and send it to the instrument; the instrument is used to determine whether to back up the backup controller based on the mileage value recorded in the vehicle instrument and the backup controller, and the judgment result is sent to the external detector for feedback to the user, and the corresponding mileage value is sent to the backup controller that needs to be backed up; the backup controller is used to update the mileage value based on the mileage value sent by the instrument.

[0078] The present application also proposes a vehicle, which includes a device or system for applying the above-mentioned instrument mileage backup synchronization method.

[0079] The instrument needs to receive and judge a lot of content when it is turned on, and the backup operation of the instrument in this application is triggered by an external detector. The external detector only serves as a bridge between backup triggering and information transmission, avoiding the mileage value backup judgment every time the instrument is powered on, and will not waste unnecessary calculations, saving computing resources. The method of this application is easy to apply, and the coverage range can reach 90% of the working conditions. Whether to perform a backup depends on the user's judgment, and there will be no risk of accidental rewriting caused by instrument troubleshooting, replacement of parts, etc.

[0080] The present invention is described above by way of example in conjunction with the accompanying drawings. Obviously, the specific implementation of the present invention is not limited to the above-mentioned methods. As long as various non-substantial improvements are made using the method concept and technical solution of the present invention; or the above concept and technical solution of the present invention are directly applied to other occasions without improvement, they are all within the protection scope of the present invention.

Claims

1. A method for synchronizing instrument mileage backup, characterized in that: The method comprises: Step S1, the external detector sends a backup request to the meter and each backup controller to start mileage backup; Step S2, the meter and each backup controller upload the recorded mileage value to the vehicle network matrix and read it through an external detector; Step S3, the external detector sends the mileage values ​​of each backup controller read to the meter, and the meter then determines whether the backup controller meets the backup requirements in combination with the mileage values ​​stored in the meter; Step S4: For the backup controller that meets the backup requirements, the meter mileage value is written into the corresponding backup controller through an external detector to overwrite the original mileage value stored in the backup controller.

2. The method for synchronizing instrument mileage backup according to claim 1, characterized in that: The method further comprises: Step S5: The external detector reads back the backup controller that has completed the backup to verify whether the backup is successful.

3. The method for synchronizing instrument mileage backup according to claim 1, characterized in that: The backup controller includes a body controller, an engine controller, a motor controller, and an ignition controller.

4. The method for synchronizing meter mileage backup according to claim 1, characterized in that: The backup requirements in step S2 include: (1) If the current meter mileage value is the same as the mileage value stored in all backup controllers, and the mileage values ​​stored in all backup controllers are also the same, it is considered that the backup requirements are not met and the backup controller is not rewritten; (2) If the current meter mileage value is greater than the mileage values ​​stored in all backup controllers, and the mileage values ​​stored in all backup controllers are the same, it is considered that the backup requirements are not met and the backup controllers are not rewritten; (3) If the current meter mileage value is less than the mileage values ​​stored in all backup controllers, and the difference between them is less than a preset coefficient, it is deemed that the backup requirement is not met and the backup controller is not rewritten. The mileage values ​​stored in all backup controllers are the same. (4) If the current meter mileage value is less than the mileage value stored in all backup controllers, but the difference between them is greater than or equal to the preset coefficient, it is considered that the backup requirements are met and all backup controllers are rewritten, wherein the mileage values ​​stored in all backup controllers are the same; (5) If the current meter mileage value is the same as the mileage value stored in one backup controller, but the mileage values ​​stored in the other backup controllers are the same, and the current meter mileage value is greater than the mileage values ​​stored in the other backup controllers, it is considered that the backup requirements are not met and the backup controller is not rewritten; (6) If the current meter mileage value is the same as the mileage value stored in one backup controller, but the mileage values ​​stored in the other backup controllers are the same, and the current meter mileage value is less than the mileage values ​​stored in the other backup controllers, it is considered that the backup requirements are not met and the backup controller is not rewritten; (7) If the current meter mileage value is less than the mileage value stored in all backup controllers, and there is at least one mileage value of the current meter mileage value and the mileage value stored in the backup controller whose difference is greater than or equal to the preset coefficient, it is considered that the backup requirements are met and all backup controllers are rewritten.

5. The method for synchronizing instrument mileage backup according to claim 4, characterized in that: The preset coefficient is determined by the maximum value of the mileage that can be reset to zero before the car leaves the factory.

6. A method for synchronizing meter mileage backup according to any one of claims 1 to 5, characterized in that: The instrument feeds back the judgment result of the corresponding backup requirement to the external detector to inform the user, and the user further decides whether to execute the backup rewrite of all backup controllers through the external detector.

7. The instrument mileage backup synchronization system according to claim 1, characterized in that: The external detector adopts 431 diagnostic instrument.

8. An instrument mileage backup synchronization system, characterized in that: The system is configured according to an instrument mileage backup synchronization method according to any one of claims 1 to 7, and includes a vehicle instrument, a backup controller, and an external detector, wherein the external detector is connected to the vehicle instrument and the backup controller.

9. A vehicle, characterized in that: The vehicle includes a device or system for applying an instrument mileage backup synchronization method according to any one of claims 1-7.

Images