Description:FIELD OF INVENTION
[0001] The present invention is generally related to a system and method for synchronizing odometer data in a vehicle, and more particularly to a system and method for synchronization of odometer data between an Instrument Cluster (IC) and a Motor Control Unit (MCU).
BACKGROUND OF INVENTION
[0002] In modern vehicles, the odometer data is a critical piece of information, as it reflects the total distance traveled by the vehicle. Traditionally, this data is stored in the Instrument Cluster (IC). However, existing solutions face significant challenges in scenarios where the IC fails. When such a failure occurs, it becomes impossible to retrieve the actual odometer data, leading to inaccuracies and potential issues in vehicle maintenance, resale, and legal compliance.
[0003] One solution to overcome this problem is to store the odometer data in an additional control unit within the vehicle, such as the Motor Control Unit (MCU) or Engine Control Unit (ECU). In this setup, if the IC is replaced, the MCU will retain the vehicle's odometer data. This value can then be loaded or set into the newly fitted IC, or an IC software algorithm can be designed to automatically retrieve and update the odometer data from the MCU, ensuring seamless synchronization and accuracy.
[0004] Indian Patent IN 201621022275, issued to Mahindra & Mahindra Limited, discloses a system for protecting vehicle odometer and engine hour data in the event of an IC or Engine Electronic Control Unit (EECU) failure. In this system, the odometer and engine hour readings are saved in the electronically erasable read-only memory (EEPROM) of the instrument cluster. Every time the IC receives the vehicle odometer and engine hour readings, it compares them with the last saved readings. If there is manipulation in the readings or if the IC is replaced, the current readings are compared to the last stored readings. If the current reading is less than the last stored reading, the difference between the two consecutive readings is added to the last stored reading to obtain the real-time, absolute reading.
[0005] This specification recognizes the need for a system and method to ensure that odometer data remains consistent and reliable, regardless of IC failures or replacements, thereby enhancing the reliability and accuracy of vehicle information systems. Furthermore, there is a need for a system and method to perform forced synchronization of odometer data between the MCU and IC if any component is replaced while maintaining flexibility for the service team.
[0006] Thus, in view of the above, there is a long-felt need in the industry to address the aforementioned deficiencies and inadequacies.
SUMMARY OF THE INVENTION
[0007] A system and method for synchronizing odometer data in a vehicle are provided substantially, as shown in and/or described in connection with at least one of the figures.
[0008] An aspect of the present disclosure relates to a method for synchronizing odometer data in a vehicle. The method initiates with a step of replacing the failed IC or MCU component. Then the method includes a provision of conducting a test drive of the vehicle for up to 100km. This provision ensures the service station has flexibility to test drive the newly fitted part and the vehicle is working fine ensuring the fault diagnosis is correct and no further changes in system are required. The method includes a step of a) establishing, by a communication network bus, a communication of a processor with a battery management system (BMS), a vehicle control unit (VCU), an instrument cluster (IC), and a motor control unit (MCU). The method includes a step of b) initiating, by the processor, a synchronization operation. The method includes a step of c) retrieving, by the processor, the odometer data of the IC and the MCU. The method includes a step of d) comparing, by the processor, the retrieved odometer data of the IC and the MCU to obtain a comparison value. The method includes a step of e) instructing, by the processor, based on the comparison value, the MCU to store the odometer data of the IC in an MCU memory upon determining that the odometer data of the IC is greater than the odometer data of the MCU. The method includes a step of f) instructing, by the processor, based on the comparison value, the IC to store the odometer data of the MCU in an IC memory upon determining the odometer data of the MCU is greater than the odometer data of the IC. The method includes a step of g) synchronizing, by the processor, the odometer data between the IC and MCU, to ensure the vehicle operation. In an aspect, steps a) to g) are performed in the vehicle during the replacement of the IC and MCU at an authorized service station.
[0009] In an aspect, the comparison value is indicative of whether the odometer data of the IC is greater than the odometer data of the MCU or not.
[0010] In an aspect, the communication network bus is a controller area network (CAN) bus.
[0011] In an aspect, the BMS is installed in a battery to monitor and protect the operations of the battery.
[0012] Another aspect of the present disclosure relates to a system for synchronizing odometer data in a vehicle. The system includes an instrument cluster (IC); a vehicle control unit (VCU); a motor control unit (MCU); a battery; a battery management system (BMS); an authorized diagnostic module, referred to as processor hereafter is connected to On Board Diagnostics (OBD) port present in vehicle. The IC is configured with an IC memory to store odometer data, and a display screen to display data related to speed, remaining range, state of charge of the battery, and odometer. The VCU is configured to control a plurality of functions of the vehicle. The MCU is configured with an MCU memory to control the operation of an electric motor of the vehicle. The battery is configured to provide the power to the electric motor. The BMS is installed in the battery to monitor and protect the operations of the battery. The authorized diagnostic module includes the processor that establishes communication with the IC, the VCU, the MCU, and the BMS over a communication network bus. The processor is configured to initiate a synchronization operation. The processor is configured to retrieve the odometer data of the IC and the MCU. The processor is configured to compare the retrieved odometer data of the IC and the MCU to obtain a comparison value. The processor is configured to instruct, based on the comparison value, the MCU to store the odometer data of the IC in the MCU memory upon determining that the odometer data of the IC is greater than the odometer data of the MCU. The processor is configured to instruct, based on the comparison value, the IC to store the odometer data of the MCU in the IC memory upon determining the odometer data of the MCU is greater than the odometer data of the IC. The processor is configured to synchronize the odometer data between the IC and MCU, to ensure vehicle operation.
[0013] In an aspect, the comparison value is indicative of whether the odometer data of the IC is greater than the odometer data of the MCU or not.
[0014] In an aspect, the communication network bus is based on a controller area network (CAN) bus.
[0015] In an aspect, the MCU computes the odometer data by computing speed data and then broadcasts the odometer data and speed data on the CAN bus to IC.
[0016] In an aspect, the authorized diagnostic module is configured to detect discrepancies between the odometer data of the IC and the MCU.
[0017] In an aspect, the authorized diagnostic module generates an alert if the discrepancy between the odometer data of the IC and the MCU exceeds a predefined threshold.
[0018] In an aspect, the processor is further configured to: transmit the synchronized odometer data to a remote server for backup and analysis.
[0019] In an aspect, the IC memory and the MCU memory each include a non-volatile memory for storing odometer data persistently.
[0020] Accordingly, one advantage of the present invention is that there is no loss of actual odometer value or warranty kilometers due to the failure or tampering of the IC or MCU.
[0021] Accordingly, one advantage of the present invention is that it allows for easy and semi-automated synchronization of odometer values using a diagnostic tool at authorized service centers only.
[0022] Accordingly, one advantage of the present invention is that there is no human intervention required to enter odometer values, thereby eliminating the possibility of odometer value manipulation.
[0023] Accordingly, one advantage of the present invention is that the driver is unable to drive the vehicle beyond 100 km (configurable) if the IC or MCU is replaced. This 100 km buffer is provided for service testing and checking purposes.
[0024] These features and advantages of the present disclosure may be appreciated by reviewing the following description of the present disclosure, along with the accompanying figures wherein reference numerals refer to like parts.

BRIEF DESCRIPTION OF THE DRAWINGS
[0025] The accompanying drawings illustrate the embodiment of devices, systems, methods, and other aspects of the disclosure. Any person with ordinary skills in the art will appreciate that the illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures represent an example of the boundaries. In some examples, one element may be designed as multiple elements, or multiple elements may be designed as one element. In some examples, an element shown as an internal component of one element may be implemented as an external component in another and vice versa. Furthermore, the elements may not be drawn to scale.
[0026] Various embodiments will hereinafter be described in accordance with the appended drawings, which are provided to illustrate, not limit, the scope, wherein similar designations denote similar elements, and in which:
[0027] FIG. 1 illustrates a block diagram of an architecture of a system (100) for synchronizing odometer data in a vehicle, in accordance with at least one embodiment.
[0028] FIG. 2 illustrates an operational flowchart of a method for synchronization of odometer data, in accordance with at least one embodiment.
[0029] FIG. 3 illustrates a flowchart of operations performed by a diagnostic tool, in accordance with at least one embodiment.
[0030] FIG. 4 illustrates a flowchart of a method for synchronizing odometer data in a vehicle during the replacement of the IC and MCU at an authorized service station, in accordance with at least one embodiment.

DETAILED DESCRIPTION OF THE EMBODIMENTS HEREIN
[0031] The present disclosure is best understood with reference to the detailed figures and description set forth herein. Various embodiments have been discussed with reference to the figures. However, those skilled in the art will readily appreciate that the detailed descriptions provided herein with respect to the figures are merely for explanatory purposes, as the methods and systems may extend beyond the described embodiments. For instance, the teachings presented and the needs of a particular application may yield multiple alternative and suitable approaches to implement the functionality of any detail described herein. Therefore, any approach may extend beyond certain implementation choices in the following embodiments.
[0032] References to “one embodiment,” “at least one embodiment,” “an embodiment,” “one example,” “an example,” “for example,” and so on indicate that the embodiment(s) or example(s) may include a particular feature, structure, characteristic, property, element, or limitation but that not every embodiment or example necessarily includes that particular feature, structure, characteristic, property, element, or limitation. Further, repeated use of the phrase “in an embodiment” does not necessarily refer to the same embodiment.
[0033] Methods of the present invention may be implemented by performing or completing manually, automatically, or a combination thereof, selected steps or tasks. The term “method” refers to manners, means, techniques, and procedures for accomplishing a given task including, but not limited to, those manners, means, techniques, and procedures either known to or readily developed from known manners, means, techniques, and procedures by practitioners of the art to which the invention belongs. The descriptions, examples, methods, and materials presented in the claims and the specification are not to be construed as limiting but rather as illustrative only. Those skilled in the art will envision many other possible variations within the scope of the technology described herein.
[0034] FIG. 1 illustrates a block diagram of an architecture of a system 100 for synchronizing odometer data in a vehicle, in accordance with at least one embodiment. Examples of the vehicle include but are not limited to a two-wheeler electric vehicle and two-wheeler vehicle. The system 100 includes an instrument cluster (IC) 102; a vehicle control unit (VCU) 108; a motor control unit (MCU) 110; a battery 114; a battery management system (BMS) 116; a processor 118; and an authorized diagnostic module 120.
[0035] The IC 102 is configured with an IC memory 104 to store odometer data, and a display screen 106 to display data related to speed, remaining range, state of charge of the battery, and odometer. The VCU 108 is configured to control a plurality of functions of the vehicle. According to an embodiment herein, the Vehicle Control Unit (VCU) 108 serves as a central brain for managing various functions within the vehicle. The key functions of the VCU 108 include but are not limited to powertrain control; vehicle dynamics and stability; safety and driver assistance; comfort and convenience; energy management; diagnostics and monitoring; and communication and coordination. Thus, the VCU 108 is integral to the efficient and safe operation of modern vehicles, coordinating numerous subsystems to ensure optimal performance, safety, and driver convenience.
[0036] The MCU 110 is configured with an MCU memory 112 to control the operation of an electric motor of the vehicle. According to an embodiment herein, the MCU 110 is responsible for managing the operation of an electric motor in various applications, including electric and hybrid vehicles. Its primary functions of MCU 110 include but are not limited to regulating motor speed and torque; power conversion; efficiency optimization; thermal management; and safety and protection.
[0037] The battery 114 is configured to provide the power to the electric motor. The BMS 116 is installed in the battery 114 to monitor and protect the operations of the battery 114. The authorized diagnostic module 120 includes the processor 118 that establishes communication with the IC 102, the VCU 108, the MCU 110, and the BMS 116 over a communication network bus 122. In an embodiment, the authorized diagnostic module 120 is connected to an open CAN connector or “On Board Diagnostic” (OBD) port in vehicle harness.
[0038] In some embodiments, the methods, systems, and media disclosed herein include software, server, and/or database modules, or use of the same. In view of the disclosure provided herein, authorized diagnostic module 120 is a software module that is created by techniques known to those of skill in the art using machines, software, and languages known to the art. The software modules disclosed herein are implemented in a multitude of ways. In various embodiments, a software module comprises a file, a section of code, a programming object, a programming structure, or combinations thereof. In further various embodiments, a software module comprises a plurality of files, a plurality of sections of code, a plurality of programming objects, a plurality of programming structures, or combinations thereof. In various embodiments, the one or more software modules comprise, by way of non-limiting examples, a web application, a mobile application, and a standalone application. In some embodiments, software modules are in one computer program or application. In other embodiments, software modules are in more than one computer program or application. In some embodiments, software modules are hosted on one machine. In other embodiments, software modules are hosted on more than one machine. In further embodiments, software modules are hosted on cloud computing platforms. In some embodiments, software modules are hosted on one or more machines in one location. In other embodiments, software modules are hosted on one or more machines in more than one location.
[0039] In an embodiment, the communication network bus 122 is based on a controller area network (CAN) bus. In an embodiment, the MCU 110 computes the odometer data by computing speed data and then broadcasts the odometer data and speed data on the CAN bus 122 to IC 102. The processor 118 is configured to initiate a synchronization operation. The processor 118 is configured to retrieve the odometer data of the IC 102 and the MCU 110. The processor 118 is configured to compare the retrieved odometer data of the IC 102 and the MCU 110 to obtain a comparison value. In an embodiment, the comparison value is indicative of whether the odometer data of the IC 102 is greater than the odometer data of the MCU 110 or not. The processor 118 is configured to instruct, based on the comparison value, the MCU 110 to store the odometer data of the IC 102 in the MCU memory 112 upon determining that the odometer data of the IC 102 is greater than the odometer data of the MCU 110. The processor 118 is configured to instruct, based on the comparison value, the IC 102 to store the odometer data of the MCU 110 in the IC memory 104 upon determining the odometer data of the MCU 110 is greater than the odometer data of the IC 102. The processor 118 is configured to synchronize the odometer data between the IC 102 and MCU 110, to ensure vehicle operation.
[0040] In an embodiment, the authorized diagnostic module 120 is configured to detect discrepancies between the odometer data of the IC 102 and the MCU 110. In an embodiment, the authorized diagnostic module 120 generates an alert if the discrepancy between the odometer data of the IC and the MCU exceeds a predefined threshold. In an exemplary embodiment, the authorized diagnostic module 120 acts as a diagnostic tool. In an embodiment, the processor 118 is further configured to transmit the synchronized odometer data to a remote server for backup and analysis. In an embodiment, the IC memory 104 and the MCU memory 112 each include a non-volatile memory for storing odometer data persistently.
[0041] According to an embodiment herein, the system may include a traction motor that includes a sensor to detect the speed of the vehicle. This sensor is connected to the MCU and then the MCU calculates the speed based on the input signal received from the sensor inside the traction motor.
[0042] FIG. 2 illustrates an operational flowchart 200 of a method for synchronization of odometer data, in accordance with at least one embodiment. FIG. 2 is explained in conjunction with FIG. 1. In a normal operation, at block 202, an ignition key of the vehicle is activated. At block 204, the method includes a step of receiving an odometer value from the MCU 110 by the IC upon activation of the ignition key. The method further includes a step 206 of comparing the received MCU odometer value with the last stored odometer value in the IC memory. The method then includes a step 208 of storing the received MCU odometer value in the IC memory and, at block 210, displaying it on a dashboard or a display screen if both odo values are equal.
[0043] The present disclosure further describes a method for forced synchronization of odometer (odo) values between an Instrument Cluster (IC) and a motor control unit (MCU) in the vehicle following component replacement. The method includes a step of detecting a mismatch between the Odometer values stored in the IC and MCU upon replacement of either component. At block 212, the method starts the calculation of the odo value using the current speed of the vehicle. The method includes a step 214 of initiating internal calculations within the IC to determine a new odometer value, which is, at block 216, displayed on the dashboard along with a synchronization warning. The method then includes a step 218 of requesting the MCU to stop the motor if the calculated Odometer value exceeds 100km during the synchronization process, facilitating service station testing.
[0044] Thus, during normal operation, whenever the ignition key is turned on, the IC receives the odometer value from the MCU. It compares the received MCU odometer value with the last stored value in the IC memory. If both values are equal, the odometer value received from the MCU will be stored in the IC memory and displayed on the dashboard.
[0045] In an operation where the IC or MCU has been replaced or tampered with, the odometer values stored in the IC and MCU will not match. In this case, the IC will start calculating on its own. The IC will display an odometer value that is the sum of the calculated odometer value and the last stored odometer value. The IC will also display an "Odo sync warning" on the display. If the calculated odometer value of the IC exceeds 100 km, the IC will send a motor stop request to the MCU and continue to display the "Odo sync warning." This provision of 100 km is intended for service station testing.
[0046] FIG. 3 illustrates a flowchart 300 of operations performed by a diagnostic tool, in accordance with at least one embodiment. At block 302, an operation of the diagnostic tool is initiated. Then, at block 304, ‘Odo Sync’ is selected by a user or driver on a display screen. Further, at block 306, the diagnostic tool receives the MCU odometer value and IC odometer value via the CAN bus. At block 308, it is determined whether the MCU odometer value is less than the IC odometer value. If the MCU odometer value is less than the IC odometer value, then at block 310, the IC odometer value is written to the MCU EEPROM. If the MCU odometer value is greater than the IC odometer value, then at block 312, the MCU odometer value is written to the IC EEPROM.
[0047] As used herein, and unless the context dictates otherwise, the term “configured to” or “coupled to” is intended to include both direct coupling (in which two elements that are coupled to each other contact each other) and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms “configured to”, “configured with”, “coupled to” and “coupled with” are used synonymously. Within the context of this document terms “configured to”, “coupled to” and “coupled with” are also used euphemistically to mean “communicatively coupled with” over a network, where two or more devices can exchange data with each other over the network, possibly via one or more intermediary device.
[0048] FIG. 4 illustrates a flowchart 400 of a method for synchronizing odometer data in a vehicle during the replacement of the IC and MCU at an authorized service station, in accordance with at least one embodiment. FIG. 4 is explained in conjunction with FIG. 1. In operation, the method initiates with a step of replacing the failed IC or MCU component. Then the method includes a step of conducting a test drive of the vehicle for up to 100km. The method includes a step 402 of a) establishing, by a communication network bus, a communication of a processor with a battery management system (BMS), a vehicle control unit (VCU), an instrument cluster (IC), and a motor control unit (MCU). The method includes a step 404 of b) initiating, by the processor, a synchronization operation. The method includes a step 406 of c) retrieving, by the processor, the odometer data of the IC and the MCU. The method includes a step 408 of d) comparing, by the processor, the retrieved odometer data of the IC and the MCU to obtain a comparison value. The method includes a step 410 of e) instructing, by the processor, based on the comparison value, the MCU to store the odometer data of the IC in an MCU memory upon determining that the odometer data of the IC is greater than the odometer data of the MCU. The method includes a step 412 of f) instructing, by the processor, based on the comparison value, the IC to store the odometer data of the MCU in an IC memory upon determining the odometer data of the MCU is greater than the odometer data of the IC. The method includes a step 414 of g) synchronizing, by the processor, the odometer data between the IC and MCU, to ensure the vehicle operation. In an embodiment, steps a) to g) are performed in the vehicle during the replacement of the IC and MCU at an authorized service station.
[0049] In an embodiment, the comparison value is indicative of whether the odometer data of the IC is greater than the odometer data of the MCU or not. In an embodiment, the communication network bus is a controller area network (CAN) bus. In an embodiment, the BMS is installed in a battery to monitor and protect the operations of the battery.
[0050] Thus, there is no loss of actual odometer value or warranty kilometers due to the failure or tampering of the IC or MCU. The system and method of the present invention for synchronizing odometer data in the vehicle allows for easy and semi-automated synchronization of odometer values using an authorized diagnostic tool at authorized service centers only. Further, there is no human intervention required to enter odometer values, thereby eliminating the possibility of odometer value manipulation.
[0051] It should be apparent to those skilled in the art that many more modifications besides those already described are possible without departing from the inventive concepts herein. The inventive subject matter, therefore, is not to be restricted except in the scope of the appended claims. Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, utilized, or combined with other elements, components, or steps that are not expressly referenced.
[0052] No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the invention.
[0053] It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the scope of the invention. There is no intention to limit the invention to the specific form or forms enclosed. On the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the scope of the invention, as defined in the appended claims. Thus, it is intended that the present invention cover the modifications and variations of this invention, provided they are within the scope of the appended claims and their equivalents.
, Claims:1. A method for synchronizing odometer data in a vehicle, comprising the steps of:
a) establishing, by a communication network bus, a communication of a processor with a battery management system (BMS), a vehicle control unit (VCU), an instrument cluster (IC), and a motor control unit (MCU);
b) initiating, by the processor, a synchronization operation;
c) retrieving, by the processor, the odometer data of the IC and the MCU;
d) comparing, by the processor, the retrieved odometer data of the IC and the MCU to obtain a comparison value;
e) instructing, by the processor, based on the comparison value, the MCU to store the odometer data of the IC in an MCU memory upon determining that the odometer data of the IC is greater than the odometer data of the MCU;
f) instructing, by the processor, based on the comparison value, the IC to store the odometer data of the MCU in an IC memory upon determining the odometer data of the MCU is greater than the odometer data of the IC; and
g) synchronizing, by the processor, the odometer data between the IC and MCU, to ensure the vehicle operation.

2. The method as claimed in claim 1, wherein the comparison value is indicative of whether the odometer data of the IC is greater than the odometer data of the MCU or not.

3. The method as claimed in claim 1, comprises a step of transmitting, by the processor, synchronized odometer data to a remote server for backup and analysis.

4. The method as claimed in claim 1, wherein the communication network bus is a controller area network (CAN) bus.

5. The method as claimed in claim 1, wherein the BMS is installed in a battery to monitor and protect the operations of the battery.

6. A system (100) for synchronizing odometer data in a vehicle, comprising:
an instrument cluster (IC) (102) configured with an IC memory (104) to store odometer data, and a display screen (106);
a vehicle control unit (VCU) (108) configured to control a plurality of functions of the vehicle;
a motor control unit (MCU) (110) configured with an MCU memory (112) to control operation of an electric motor of the vehicle;
a battery (114) to provide the power to the electric motor; and
a battery management system (BMS) (116) installed in the battery (114) to monitor and protect operations of the battery (114);
characterized in that,
an authorized diagnostic module (120) comprises a processor (118) that establishes communication with the IC (102), the VCU (108), the MCU (110), and the BMS (116) over a communication network bus (122), wherein the processor (118) is configured to:
initiate a synchronization operation;
retrieve the odometer data of the IC (102) and the MCU (110);
compare the retrieved odometer data of the IC (102) and the MCU (110) to obtain a comparison value;
instruct, based on the comparison value, the MCU (110) to store the odometer data of the IC (102) in the MCU memory (112) upon determining that the odometer data of the IC (102) is greater than the odometer data of the MCU (110);
instruct, based on the comparison value, the IC (102) to store the odometer data of the MCU (110) in the IC memory (104) upon determining the odometer data of the MCU (110) is greater than the odometer data of the IC (102); and
synchronize the odometer data between the IC (102) and MCU (110), to ensure the vehicle operation.

7. The system (100) as claimed in claim 6, wherein the comparison value is indicative of whether the odometer data of the IC (102) is greater than the odometer data of the MCU (110) or not.

8. The system (100) as claimed in claim 6, wherein the communication network bus (122) is based on a controller area network (CAN) bus.

9. The system (100) as claimed in claim 6, wherein the MCU (110) computes the odometer data by computing speed data and then broadcasts the odometer data and speed data on the CAN bus (122) to IC (102).

10. The system (100) as claimed in claim 6, wherein the authorized diagnostic module (120) is configured to detect discrepancies between the odometer data of the IC (102) and the MCU (110).