Method and apparatus for vehicle maintenance event detection and recording

Abstract

The present disclosure provides a method and device for vehicle maintenance event detection and recording, and discloses a method, device, system and product for vehicle maintenance event detection and recording. An exemplary device includes: a maintenance event detector for detecting a first maintenance event including at least one of a tire rotation event or a fluid change event; a parameter recorder for storing the vehicle position, time and vehicle travel distance when the first maintenance event occurs in a service log; and a distance calibrator for determining a target distance for a second maintenance event based on the information stored in the service log.

Description

Technical Field

[0001] The present disclosure relates generally to vehicles and, more particularly, to vehicle maintenance event detection and recording. Background Art

[0002] In recent years, vehicles have required less scheduled maintenance (fluid changes, tire rotations, air filter changes, etc.) than in the past. While this trend has reduced the time users spend maintaining their vehicles, it has also caused consumers to miss or delay scheduled maintenance milestones for their vehicles. Missing or delaying scheduled maintenance not only results in additional wear and tear on the vehicle, it can also void the consumer's warranty.

[0003] Furthermore, even if a consumer does complete all scheduled maintenance on their vehicle at the recommended times, accurate and detailed records of maintenance events (fluid changes, tire rotations, etc.) need to be maintained to take advantage of the vehicle's warranty. For example, a tire warranty claim for a vehicle may be invalidated by not rotating the tires at the appropriate (e.g., target) intervals or not having a documented record of rotating the tires at the target intervals. Summary of the invention

[0004] The present invention discloses a device for vehicle maintenance event detection and recording. The exemplary device includes: a maintenance event detector for detecting a first maintenance event including at least one of a tire rotation event or a fluid change event; a parameter recorder for storing a vehicle position, a time, and a vehicle travel distance when the first maintenance event occurs in a service log; and a distance scaler (targeter) for determining a target distance for a second maintenance event based on the information stored in the service log.

[0005] Another exemplary apparatus includes a vehicle maintenance diagnostic processor programmed to detect a first tire rotation event, and wherein the processor is to record at least one of a vehicle position, a time, and a vehicle distance traveled for the first tire rotation event, and to calculate a target distance for a second tire rotation event based on the recorded information.

[0006] An exemplary method includes: detecting a first maintenance event including at least one of a tire rotation event or a fluid change event; in response to detecting the first maintenance event, storing a vehicle location, a time, and a vehicle travel distance when the first maintenance event occurred in a service log; and determining a target distance for a second maintenance event based on the information stored in the service log. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 An exemplary vehicle including a vehicle maintenance diagnostic processor is shown by which the examples disclosed herein may be implemented.

[0008] Figure 2A and Figure 2B Shown in Figure 1 Example vehicle maintenance events performed on a vehicle of .

[0009] Figure 3 is further elaborated Figure 1 A block diagram of a vehicle maintenance diagnostic processor by which the examples disclosed herein may be implemented is provided.

[0010] Figure 4 Is for tire rotation events caused by Figure 1 An exemplary service log generated by a vehicle maintenance diagnostic processor.

[0011] Figure 5 is for fluid change events Figure 1 An exemplary service log generated by a vehicle maintenance diagnostic processor.

[0012] Figures 6 to 10 is a flowchart representing an exemplary method that can be used Figure 1 The vehicle maintenance diagnostic processor executes to detect and / or record information related to vehicle maintenance events.

[0013] Fig.11 is structured to execute machine-readable instructions to implement Figures 6 to 10 Methods and Figure 1 and / or Figure 3 A block diagram of an exemplary processor platform for an exemplary vehicle maintenance diagnostic processor.

[0014] The drawings are not drawn to scale. Wherever possible, the same reference numbers will be used throughout the drawings and accompanying written description to refer to the same or like parts. DETAILED DESCRIPTION

[0015] Many modern vehicles require less scheduled maintenance (fluid changes, tire rotations, air filter changes, etc.) than in the past. While this trend is often viewed as providing a better experience for consumers, it has also led to consumers missing and / or skipping scheduled maintenance milestones for their vehicles. Missing or skipping scheduled maintenance can void a consumer's warranty in addition to causing additional wear and tear on the vehicle.

[0016] One such example of this is oil changes and their interaction with tire rotation. In the past, it was often recommended (e.g., set a goal) to rotate the vehicle's tires whenever the vehicle's oil was changed. This resulted in the vehicle undergoing both tire rotation and oil changes every 10,000 miles. However, in some vehicles and / or using certain types of oil, vehicles can now operate 20,000 miles or more between oil changes, and many vehicle / tire manufacturers have not changed their recommendations regarding tire rotation schedules. Therefore, for vehicles with extended oil change maintenance windows, users will be required to rotate their vehicle's tires in addition to rotating the vehicle's tires every time the oil is changed.

[0017] Additionally, in some cases, a consumer may complete all scheduled maintenance on their vehicle at a target time, but may not maintain accurate and detailed records of maintenance events (fluid changes, tire rotations, etc.) In such an example, the consumer may not be able to use their warranty if the warranty provider requires a detailed service log to ensure that the consumer is properly maintaining their vehicle.

[0018] The examples disclosed herein automatically detect, record, and verify maintenance events completed on a vehicle. More specifically, the examples detect at least one of a tire rotation event or a fluid change event. The examples detect a tire rotation event when one or more tires change positions on the vehicle, and detect a fluid change when the level of a fluid changes from a first level to a second level. Although the examples disclosed herein are described as being applied to tire rotation events and fluid change events of a vehicle, the teachings of the present disclosure may be more generally applied to any other maintenance event performed on a vehicle.

[0019] As will be explained in greater detail below, examples described herein provide a vehicle maintenance diagnostic processor to detect and record at least one of tire rotation or fluid changes.

[0020] In some examples, in response to detecting at least one of a tire rotation or a fluid change, the vehicle maintenance diagnostic processor may also determine at least one of a location and / or service station, a date and time, and a total vehicle distance traveled when the maintenance event occurred. In some examples, the processor may also record the maintenance event parameters in a service record storage.

[0021] Additionally or alternatively, in response to detecting at least one of a tire rotation or a fluid change, the vehicle maintenance diagnostic processor may verify the tire rotation or the fluid change. In some examples, verifying the tire rotation event may also include determining that each tire of the vehicle is rotated to a recommended (e.g., target) position on the vehicle, and verifying the fluid change event may also include determining that the level of the changed fluid is filled to a recommended (e.g., target) level. In response to detecting that the maintenance event is invalid, the vehicle maintenance diagnostic processor may also generate an alert to notify a user of the vehicle that maintenance was performed incorrectly.

[0022] Additionally or alternatively, the vehicle maintenance diagnostic processor may suggest a vehicle driving distance (e.g., a driving distance goal) for future maintenance events. In some examples, the vehicle maintenance diagnostic processor may suggest a driving distance goal for tire rotations such that the total distance driven on a first tire rotation configuration (e.g., a tire position configuration) is balanced with the total distance driven on a second tire position configuration. Alternatively, in some examples, the vehicle maintenance diagnostic processor may suggest a driving distance goal for a fluid change based on a manufacturer-specified fluid change distance (e.g., a manufacturer-recommended (e.g., target) driving distance between oil changes). In some examples, the vehicle maintenance diagnostic processor may also record the driving distance goal for future maintenance events in a service record storage.

[0023] Additionally or alternatively, based on the determined travel distance goal for future maintenance events, the vehicle maintenance diagnostic processor may also determine, based on the current vehicle travel distance, whether maintenance is required (e.g., maintenance is targeted) or will be targeted in the near future (e.g., within the next week, within the next 500 miles, within the next 100 miles, etc.). In response to determining that maintenance is targeted or will be targeted in the near future, the vehicle maintenance diagnostic processor may also notify the user of the vehicle of the upcoming maintenance, and in some examples, may suggest to the user of the vehicle a service station and time to complete the required (e.g., targeted) maintenance.

[0024] As will be discussed in more detail below in accordance with the teachings of the present disclosure, the vehicle maintenance diagnostic processor can have various configurations that may depend on the type of vehicle and / or the specific characteristics of the maintenance event required for the vehicle. In the examples disclosed herein, these configurations may be changed or altered to optimize the ability of the vehicle maintenance diagnostic processor to properly diagnose vehicle maintenance events and record information related to the events.

[0025] refer to Figure 1 , the example vehicle maintenance diagnostic processor 100 disclosed herein operates in an example vehicle 102. In some examples, the vehicle 102 may have one or more tires 104. Figure 1In the illustrated example of FIG. 1 , vehicle 102 has four (4) tires 104A, 104B, 104C, and 104D and tire 104A is in the right front (FR) position, tire 104B is in the left front (FL) position, tire 104C is in the right rear (BR) position, and tire 104D is in the left rear (BL) position. Coupled to each tire 104 is an exemplary tire pressure monitoring system (TPMS) sensor 106. Figure 1 In the illustrated example of , tire 104A includes TPMS sensor 106A, tire 104B includes TPMS sensor 106B, tire 104C includes TPMS sensor 106C, and tire 104D includes TPMS sensor 106D.

[0026] In some examples, the TPMS sensor 106 collects data on one or more tires 104. For example, the TPMS sensor 106 can collect pressure data of the tire 104. Additionally or alternatively, the TPMS sensor 106 can collect temperature data of the tire 104. Additionally or alternatively, the TPMS sensor 106 can collect sensor orientation data (e.g., the TPMS sensor 106 is vertical, the TPMS sensor 106 is horizontal, the TPMS sensor 106 is 30° from horizontal, etc.). Additionally or alternatively, the TPMS sensor 106 can determine the angular rotation (e.g., angular displacement) of the tire 104 during the monitoring period (e.g., the tire 104A rotates 450 degrees in 3 seconds, the tire 104B rotates 480 degrees in 3 seconds, etc.).

[0027] In some examples, each TPMS sensor 106 has an identifier (eg, a serial number) that is unique to that sensor. Figure 1 In the illustrated example of , each of the TPMS sensors 106A, 106B, 106C, and 106D has a unique serial number. In some examples, each of the TPMS sensors 106A, 106B, 106C, and 106D is also used to transmit at least one of pressure data, orientation data, angular rotation data (e.g., displacement data), temperature data, and the unique serial number to the vehicle maintenance diagnostic processor 100.

[0028] Tire 104 is also coupled to one or more wheel assemblies 107, each wheel assembly 107 including a wheel assembly rotation sensor 108. Figure 1In the illustrated example of , tire 104A is coupled to wheel assembly 107A, wheel assembly 107A includes wheel assembly rotation sensor 108A, tire 104B is coupled to wheel assembly 107B, wheel assembly 107B includes wheel assembly rotation sensor 108B, tire 104C is coupled to wheel assembly 107C, wheel assembly 107C includes wheel assembly rotation sensor 108C, and tire 104D is coupled to wheel assembly 107D, wheel assembly 107D includes wheel assembly rotation sensor 108D. In some examples, wheel assembly rotation sensors 108 determine the instantaneous orientation of each wheel assembly 107 (e.g., wheel assembly rotation sensor 108 is horizontal, wheel assembly rotation sensor 108 is vertical, wheel assembly rotation sensor 108 is 30 degrees from vertical, etc.).

[0029] Additionally or alternatively, the wheel assembly rotation sensor 108 may determine the orientation of the wheel assembly 107 at discrete intervals (e.g., the wheel assembly rotation sensor 108 may detect every 6 degrees of rotation of the wheel assembly 107, every 30 degrees of rotation of the wheel assembly 107, etc.). Additionally or alternatively, the wheel assembly rotation sensor 108 may determine the angular rotation (e.g., angular displacement) of the wheel assembly 107 within the monitoring period (e.g., wheel assembly 107A rotates 450 degrees in 3 seconds, wheel assembly 107B rotates 7,800 degrees in 12 seconds, etc.). In some examples, the wheel assembly rotation sensor 108 may also transmit at least one of the angular rotation data (e.g., displacement data) or the orientation data of each wheel assembly 107 to the vehicle maintenance diagnostic processor 100. Additionally, each wheel assembly rotation sensor 108 remains in its original position on the vehicle 102. For example, wheel assembly rotation sensor 108A will always be a FR wheel assembly rotation sensor, wheel assembly rotation sensor 108B will always be a FL wheel assembly rotation sensor, wheel assembly rotation sensor 108C will always be a BR wheel assembly rotation sensor, and wheel assembly rotation sensor 108D will always be a BL wheel assembly rotation sensor.

[0030] The vehicle 102 also includes a fluid 110. In some examples, the fluid 110 may be oil, windshield washer fluid, brake fluid, transmission fluid, or any other fluid used for operation of the vehicle 102. Typically, the fluid 110 needs to be changed or refilled at periodic intervals. To measure the level of the fluid before and / or after the fluid is changed and / or refilled, the vehicle 102 also includes a fluid level sensor 112 coupled to a reservoir containing the fluid 110. In some examples, the fluid level sensor 112 may also communicate the level of the fluid 110 to the vehicle maintenance diagnostic processor 100.

[0031] In some examples of the vehicle 102, the vehicle maintenance diagnostic processor 100 is also connected to the exemplary network 114. For example, Figure 1 The network 114 of the illustrated example is the Internet. However, the network 114 may be implemented using any suitable wired and / or wireless network, including, for example, one or more data buses, one or more local area networks (LANs), one or more wireless LANs, one or more cellular networks, one or more private networks, one or more public networks, etc. The network 114 enables the exemplary vehicle maintenance diagnostic processor 100 to communicate with the vehicle maintenance database 116. As used herein, the term "communication" (including variations thereof) encompasses direct communication and / or indirect communication through one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or constant communication, but rather includes selective communication at periodic or non-periodic intervals, as well as one-time events.

[0032] A vehicle maintenance database 116 connected to the vehicle maintenance diagnostic processor 100 via the network 114 is used to record data (e.g., information obtained, messages generated, etc.) generated by the vehicle maintenance diagnostic processor 100 for the vehicle 102. In some examples, the vehicle maintenance database 116 can record data from multiple vehicle maintenance diagnostic processors 100 included in multiple vehicles 102. For example, the vehicle maintenance database 116 can record data from a fleet of vehicles 102. The vehicle maintenance database 116 can be implemented by volatile memory (e.g., synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS dynamic random access memory (RDRAM), etc.) and / or non-volatile memory (e.g., flash memory). The vehicle maintenance database 116 can be additionally or alternatively implemented by one or more double data rate (DDR) memories, such as DDR, DDR2, DDR3, mobile DDR (mDDR), etc. The vehicle maintenance database 116 can be additionally or alternatively implemented by one or more mass storage devices, such as hard disk drives, optical drives, digital versatile disk drives, etc. Although in the illustrated example, the vehicle maintenance database 116 is illustrated as a single database, the vehicle maintenance database 116 may be implemented by any number and / or type of databases. Furthermore, the vehicle maintenance database 116 may be located in the vehicle 102 or in a central location external to the vehicle 102. Furthermore, the data stored in the vehicle maintenance database 116 may be in any data format, such as, for example, binary data, comma-delimited data, tab-delimited data, structured query language (SQL) structures, etc.

[0033] Figure 2A and Figure 2B is an illustrative example of a maintenance event 200, where the maintenance event 200 is completed on the vehicle 102. In the illustrated example, Figure 2A The vehicle 102 is shown prior to the maintenance event 200, and Figure 2B The vehicle 102 is shown after a maintenance event 200 .

[0034] Maintenance event 200 includes a rotation of tire 104. Figure 2A and Figure 2B In the illustrated example of , tire 104A and TPMS sensor 106A have moved from the FR position to the BL position on vehicle 102. Therefore, tire 104A and TPMS sensor 106A are now coupled to wheel assembly 107D and wheel assembly rotation sensor 108D. Additionally, tire 104B and TPMS sensor 106B have moved from the FL position to the BR position on vehicle 102. Therefore, tire 104B and TPMS sensor 106B are now coupled to wheel assembly 107C and wheel assembly rotation sensor 108C. Additionally, tire 104C and TPMS sensor 106C have moved from the BR position to the FL position on vehicle 102. Therefore, tire 104C and TPMS sensor 106C are now coupled to wheel assembly 107B and wheel assembly rotation sensor 108B. Additionally, tire 104D and TPMS sensor 106D have moved from the BL position to the FR position on vehicle 102. Thus, tire 104D and TPMS sensor 106D are now coupled to wheel assembly 107A and wheel assembly rotation sensor 108A.

[0035] Although in Figure 2A and Figure 2B An exemplary tire rotation pattern (e.g., an X pattern or a cross pattern) is shown in maintenance event 200 of FIG. 1 , but any exemplary tire rotation pattern may be used. For example, front to back rotation (e.g., FL and FR rotate to BL and BR, respectively, and BL and BR rotate to FL and FR, respectively), rearward crossover (e.g., FL and FR rotate to BR and BL, respectively, and BL and BR rotate to FL and FR, respectively), forward crossover (e.g., FL and FR rotate to BL and BR, respectively, and BL and BR rotate to FR and FL, respectively), or any other rotation of the FL, FR, BL, and BR tires 104 may be used.

[0036] Additionally, maintenance event 200 includes a change in fluid 110. Figure 2A and Figure 2B In the illustrated example of FIG. 1 , after the maintenance event 200 is completed, the fluid 110 is removed from Figure 2A The first level in becomes Figure 2B In addition, although the second level of the fluid 110 is shown as being greater than the first level of the fluid 110 , the second level of the fluid 110 may also be less than or equal to the first level of the fluid 110 .

[0037] Figure 3 yes Figure 1 3. A block diagram of an exemplary implementation of an exemplary vehicle maintenance diagnostic processor 100 of FIG. 3. In some examples, the vehicle maintenance diagnostic processor 100 may include an exemplary tire position data collector 302, an exemplary fluid level data collector 304, an exemplary maintenance event detector 306, an exemplary parameter recorder 308, an exemplary GPS (global positioning system) 310, an exemplary clock 312, an exemplary odometer 314, an exemplary maintenance event validator 316, an exemplary incorrect maintenance alert generator 318, an exemplary distance calibrator 320, an exemplary target maintenance alert generator 322, an exemplary maintenance scheduler 324, and an exemplary service record storage 326.

[0038] An exemplary tire position data collector 302 included or otherwise implemented by the vehicle maintenance diagnostic processor 100 can receive at least one of tire orientation data, tire angular rotation data, and TPMS sensor serial number data from the TPMS sensors 106A, 106B, 106C, and 106D and wheel assembly angular rotation data from the wheel assembly rotation sensors 108A, 108B, 108C, and 108D. In some examples, the tire position data collector 302 also determines the position of one or more tires 104A, 104B, 104C, and 104D based on the data received from the TPMS sensors 106 and the wheel assembly rotation sensors 108.

[0039] Furthermore, in some examples, the position of one or more tires 104A, 104B, 104C, and 104D may be determined by monitoring the instantaneous orientation with respect to the gravity data collected from the TPMS sensors 106A, 106B, 106C, and 106D and the wheel assembly angular rotation data acquired from the wheel assembly rotation sensors 108A, 108B, 108C, and 108D over a predetermined period (e.g., 5 minutes, 1 mile, 10 revolutions of the tire 104, etc.). Monitoring the data also includes comparing the orientation data of the one or more TPMS sensors 106 with the angular rotation data from one or more of the wheel assembly rotation sensors 108. For example, when the vehicle 102 turns, the displacement of each TPMS sensor 106 corresponds to the displacement of only one wheel assembly rotation sensor 108. This is a result of each tire 104 having a unique angular rotation speed / different angular rotation speed from the other tires 104 when turning. For example, when turning, only one tire 104 (at one moment in time) may have a displacement of 720°. Therefore, the TPMS sensor 106 having the same orientation (eg, 30°) before and after the 720° angular displacement of the wheel assembly rotation sensor 108 is the TPMS sensor 106 corresponding to the wheel assembly rotation sensor 108 and thus to the wheel assembly 107 .

[0040] For example, in Figure 2B In the example of FIG. 1 , the TPMS sensor 106A and the wheel assembly rotation sensor 108D identified by their unique serial numbers are at the BL position on the vehicle 102. After determining the position of the TPMS sensor 106A, the tire position data collector 302 can also determine that the tire 104A coupled to the TPMS sensor 106A is at the BL position on the vehicle 102. In some examples, the position of each tire 104 is determined in this manner. For example, in Figure 1 2, the location of each of tires 104A, 104B, 104C, and 104D is determined in this manner. In some examples, tire location data collector 302 may also distribute the location of one or more of tires 104 to maintenance event detector 306. Additionally or alternatively, other algorithms for identifying the location of one or more TPMS sensors 106 on vehicle 102 may be used.

[0041] An exemplary fluid level data collector 304 included in or otherwise implemented by the vehicle maintenance diagnostic processor 100 can receive the level of the fluid 110 from the fluid level sensor 112. In some examples, the fluid 110 can be oil, windshield washer fluid, brake fluid, transmission fluid, or any other fluid used for operation of the vehicle 102. In addition, the fluid level data collector 304 can receive a description of the fluid 110 whose level is determined by the fluid level sensor 112. In some examples, the fluid level data collector 304 can also distribute the fluid level and description of the fluid 110 to the maintenance event detector 306.

[0042] An exemplary maintenance event detector 306 included in or otherwise implemented by the vehicle maintenance diagnostic processor 100 can determine whether one or more maintenance events have occurred for the vehicle 102 based on data received from at least one of the tire position data collector 302 and the fluid level data collector 304. In some examples, the maintenance event detector 306 can determine that a tire rotation has occurred based on one or more positions of the tire 104 received from the tire position data collector 302 that are different from previously known positions of the tire 104 retrieved from the service record storage 326.

[0043] Additionally or alternatively, the maintenance event detector 306 may determine that a fluid change has occurred (e.g., detecting a discrete change in the level of the fluid 110) based on a level of the fluid 110 received from the fluid level data collector 304 that is different from a previously known level of the fluid 110 retrieved from the service record storage 326. Additionally or alternatively, for an exemplary vehicle 102 in which the fluid level sensor 112 is functional when the vehicle 102 is turned off, the maintenance event detector 306 may determine that a fluid change has occurred based on the level of the fluid 110 changing from a first level to empty (e.g., 0% fill, 0 liters, 0 gallons, etc.). Additionally or alternatively, when the fluid change is an oil change, the maintenance event detector 306 may determine that an oil change has occurred based on detecting a slowly building oil pressure (which is characteristic of an engine after at least one of an oil change and / or an oil filter change).

[0044] In response to determining that at least one of a tire rotation and / or a fluid change has occurred, the maintenance event detector 306 notifies the exemplary parameter recorder 308 of the maintenance event in addition to distributing information related to the maintenance event (e.g., whether the maintenance event is a tire rotation or a fluid change, the position of one or more tires 104 after the tire rotation, the level of the fluid 110 after the fluid change, which fluid was changed after the fluid change, etc.) to at least one of the maintenance event validator 316 and the service record storage 326.

[0045] The example parameter recorder 308 included in or otherwise implemented by the vehicle maintenance diagnostic processor 100 can retrieve data from at least one of the example GPS 310, the example clock 312, and the example odometer 314 in response to receiving a notification from the maintenance event detector 306 that a maintenance event has occurred. The GPS 310, the clock 312, and the odometer 314 included in or otherwise implemented by the vehicle maintenance diagnostic processor 100 can respectively determine the location of the vehicle 102 (e.g., 49.845 degrees N, 47.567 degrees W), the date and time (e.g., 2 / 27 / 17, 4:56 PM CST), and the total distance traveled by the vehicle 102 (e.g., 46,768 miles). In some examples, the odometer 314 can also distribute the total distance traveled by the vehicle 102 to the target maintenance alert generator 322. Additionally, in some examples, parameter logger 308 may determine a service station (e.g., a repair shop, dealership, oil change shop, car wash, etc.) by associating the GPS-based location of vehicle 102 with the service station based on known service station locations from a GPS mapping program.

[0046] An exemplary maintenance event verifier 316 included in or otherwise implemented by the vehicle maintenance diagnostic processor 100 is capable of verifying that one or more maintenance events performed on the vehicle 102 were properly performed. In some examples, in response to the maintenance event detector 306 determining that the maintenance event is a tire rotation, the maintenance event verifier 316 verifies that each tire 104 is rotated to a target position, determines a target position for the tires 104 based on a previous position of each tire 104, and retrieves a target tire rotation solution from the service record storage 326. For example, if the previous position of the tires 104 includes the tire 104A in FL, the tire 104B in FR, the tire 104C in BL, and the tire 104D in BR and the tire rotation solution is a cross tire rotation, then the target position for the tires 104 includes the tire 104A in BR, the tire 104B in BL, the tire 104C in FR, and the tire 104D in FL.

[0047] In response to determining that each current position of tires 104 matches the target position of tires 104, maintenance event validator 316 distributes a rotation valid flag to at least one of incorrect maintenance alert generator 318 and service record storage 326. Alternatively, in response to determining that one or more of the current positions of tires 104 do not match the target position of tires 104, maintenance event validator 316 distributes a rotation invalid flag to at least one of incorrect maintenance alert generator 318 and service record storage 326 along with an identifier of one or more tires 104 (e.g., at least one of tires 104A, 104B, 104C, or 104D) that were not rotated to the target position.

[0048] Alternatively, in response to the maintenance event detector 306 determining that the maintenance event is a fluid change, the maintenance event verifier 316 verifies that the fluid 110 is filled to a target level (e.g., 75% full, 4 inches, 3 liters, etc.) within a tolerance range (e.g., + / - 5%, + / - 0.25 inches, + / - 0.1 liters, etc.), where the target level of the fluid 110 and the tolerance on the target level can be retrieved from the service record storage 326. In some examples, determining that the fluid 110 is filled within the tolerance of the target level of the fluid 110 also includes determining whether the fluid 110 is within a range specified by the target level of the fluid 110 and the tolerance on the target level. For example, 3.95 liters is within the range specified as 4 liters + / - 0.1 liters. Similarly, 3.7 liters is not within the range specified as 4 liters + / - 0.1 liters.

[0049] In response to determining that the level of the fluid 110 is within the range specified by the target level of the fluid 110 and the tolerance about the target level, the maintenance event verifier 316 distributes the fluid change valid flag to at least one of the improper maintenance alert generator 318 and the service record storage 326. Alternatively, in response to determining that the level of the fluid 110 is not within the range specified by the target level of the fluid 110 and the tolerance about the target level, the maintenance event verifier 316 distributes the fluid change invalid flag along with an identifier of the fluid 110 (e.g., oil, brake fluid, transmission fluid, windshield washer fluid, etc.) and the level of the fluid 110 to at least one of the improper maintenance alert generator 318 and the service record storage 326.

[0050] An example incorrect maintenance alert generator 318 included in or otherwise implemented by the vehicle maintenance diagnostic processor 100 can generate an alert in response to receiving an invalid maintenance flag from the maintenance event validator 316. In some examples, the incorrect maintenance alert generator 318 will generate an alert for distribution to a display, audio system, or other device capable of notifying a user of the vehicle 102.

[0051] In some examples, the generated alert may include a notification that the fluid 110 is not filled to a target level. Additionally or alternatively, the generated alert may include a fluid level recommendation to correct the level of the fluid 110. Additionally or alternatively, the generated alert may include a notification that one or more tires 104 are incorrectly rotated. Additionally or alternatively, the generated alert may include a list of one or more tires 104 rotated to an incorrect position. Additionally or alternatively, the generated alert may include a tire rotation recommendation to correct the incorrect tire rotation. Additionally or alternatively, the generated alert may also distribute a maintenance required flag to the example maintenance scheduler 324.

[0052] An exemplary distance calibrator 320 included in or otherwise implemented by the vehicle maintenance diagnostic processor 100 can determine a target (e.g., recommended) distance for a future maintenance event to occur. In some examples, when determining the target distance for a future tire rotation, the distance calibrator 320 retrieves one or more tire rotation service records from the service record storage 326. The distance calibrator 320 can also determine a total distance that the vehicle 102 has traveled in at least one of the first tire rotation configuration and the second tire rotation configuration using the retrieved tire rotation service records. In some examples, determining the total distance that the vehicle 102 has traveled in at least one of the first tire rotation configuration and the second tire rotation configuration also includes summing the distance traveled during one or more time periods when the vehicle 102 is utilizing the first tire rotation configuration and summing the distance traveled during one or more time periods when the vehicle 102 is utilizing the second tire rotation configuration, respectively.

[0053] In some examples, determining the vehicle distance for the next tire rotation to balance (e.g., equalize) the distance traveled on the first tire configuration and the second tire configuration also includes: determining the difference between the total distance traveled on the first tire configuration (the cumulative distance that the vehicle 102 has traveled for one or more periods using the first tire configuration) and the total distance traveled on the second tire configuration (e.g., the cumulative distance that the vehicle 102 has traveled for one or more periods using the second tire configuration). For example, when the vehicle has traveled a cumulative distance of 38,000 miles on the first tire configuration and a cumulative distance of 41,000 miles on the second tire configuration, the difference is 3,000 miles. Similarly, when the total distance that the vehicle has traveled on the first tire configuration is less than the total distance that has been traveled on the second configuration, the difference will be negative (e.g., -3,000 miles, -1,500 miles, etc.). When calculating the difference, the distance calibrator 320 may also add the difference to the manufacturer-specified recommended (e.g., target) rotation distance. For example, if the difference is 3,000 miles and the manufacturer recommended (e.g., target) distance is 10,000 miles, the distance calibrator 320 may set the tire rotation target to 13,000 miles from the current odometer 314. Similarly, if the difference is -1,500 miles and the manufacturer recommended (e.g., target) distance is 10,000 miles, the distance calibrator 320 may set the tire rotation target to 8,500 miles from the current odometer 314. In some examples, the distance calibrator 320 may also distribute the target distance for tire rotation to at least one of the target maintenance alert generator 322 and the service record storage 326.

[0054] In some examples, when determining the target distance for a future fluid change, the distance calibrator 320 retrieves one or more fluid change service records from the service record storage 326. In addition, the distance calibrator 320 may determine the target distance based on a maintenance schedule for the vehicle 102. In some examples, this also includes adding the target distance between fluid change events to the vehicle distance at the previous fluid change event, each distance retrieved from the service record storage 326. For example, if an oil change occurs when the odometer 314 reads 3,000 miles and the target driving distance between oil changes is 8,000 miles, the distance calibrator 320 will set a target of 11,000 miles (i.e., the odometer 314 reading) for the second oil change. In some examples, the distance calibrator 320 may also distribute the target distance for the fluid change to at least one of the target maintenance alert generator 322 and the service record storage 326.

[0055] An exemplary targeted maintenance alert generator 322 included in or otherwise implemented by the vehicle maintenance diagnostic processor 100 can generate an alert when a targeted (e.g., required or recommended) maintenance is soon required (e.g., within 1 week, within 500 miles, within 1,000 miles, etc.) or is overdue for targeted maintenance. In some examples, this can also include determining a buffer distance (e.g., a particular distance until a maintenance event is required) before targeting maintenance at which a user of the vehicle 102 is to be warned of the upcoming maintenance event. The targeted maintenance alert generator 322 utilizes the calculated buffer distance in addition to the target maintenance distance calculated by the distance scaler 320 to determine a vehicle alert distance to warn the user of the vehicle 102 of the upcoming maintenance event. In some examples, determining the vehicle alert distance to warn the user also includes subtracting the buffer distance from the target maintenance distance.

[0056] The targeted maintenance alert generator 322 may also retrieve the current vehicle distance from the odometer 314. Using this value, the targeted maintenance alert generator 322 determines whether the current vehicle distance retrieved from the odometer 314 is greater than the vehicle alert distance.

[0057] In response to the current vehicle distance (e.g., odometer 314 distance) being greater than or equal to the vehicle alert distance, the targeted maintenance alert generator 322 may generate an alert for distribution to a display, audio system, or other device capable of notifying a user of the vehicle 102. In some examples, the alert may include the vehicle distance (e.g., odometer 314 distance) when maintenance is required. Additionally or alternatively, the alert may include the distance until maintenance is required (e.g., subtracting the odometer 314 distance from the vehicle alert distance).

[0058] Alternatively, in response to the current vehicle distance (eg, odometer 314 distance) being less than the vehicle alert distance, the vehicle 102 continues normal operation and the targeted maintenance alert generator 322 completes no further action.

[0059] An exemplary maintenance scheduler 324 included in or otherwise implemented by the vehicle maintenance diagnostic processor 100 can suggest a service station and time for scheduled maintenance to refill the fluid 110 to a target level and / or rotate the tire 104 to a target position. In some examples, the maintenance scheduler 324 can also schedule the maintenance event at the suggested service station and the suggested time in response to the user of the vehicle 102 accepting the suggested service station and time. In some examples, the maintenance scheduler 324 can also suggest a service station and time for scheduled maintenance based on at least one of a schedule (e.g., a calendar) of the user of the vehicle 102 and a schedule (e.g., a calendar) of one or more service stations.

[0060] Additionally or alternatively, the maintenance scheduler 324 may suggest a service station and time based on the distance to one or more nearby service stations. Additionally or alternatively, the maintenance scheduler 324 may suggest a service station and time based on one or more reviews of one or more nearby service stations. Additionally or alternatively, the maintenance scheduler 324 may suggest a service station and time based on a preference to have service done at a dealership rather than a repair shop (or vice versa). Additionally or alternatively, the maintenance scheduler may suggest a service station based on user-defined preferences.

[0061] In some examples, if the vehicle 102 is an autonomous (e.g., autonomous) vehicle, the maintenance scheduler 324 can suggest service stations and times based on the location and time at which the car is expected to be parked. For example, if the calendar of the user of the vehicle 102 shows that the user works on Tuesdays from 9:00AM to 5:00PM, the maintenance scheduler can suggest service stations near the user's work location and times in the range specified by the user's work schedule (e.g., some time between 9:00AM and 5:00PM). In addition, in response to the user accepting the suggested service station and time (e.g., Bob's Auto Service, 4 miles from the user's work location, at 1:00PM), the maintenance scheduler 324 can also accept the service station and time for the maintenance event, and the vehicle 102 can drive itself in and out of the maintenance event. In such an example, the vehicle maintenance diagnostic processor 100 will detect and record data in the same manner as if the user of the vehicle 102 drove to and from the selected service station.

[0062] like Figure 3As shown, the exemplary service record storage 326 is capable of storing service information for at least one of one or more tire rotation maintenance events and / or one or more fluid change maintenance events. In some examples, the service information may also include a previous tire rotation configuration, a current tire rotation configuration, a fluid change description, a validity check of the maintenance event, the location and / or service station where the maintenance event was completed, the vehicle distance at the maintenance event (e.g., odometer 314 distance), the time of the maintenance event, the distance since the last maintenance event, the total distance over a given tire rotation configuration, and at least one of a target distance for the next maintenance event. In some examples, the service record storage 326 may store the service records in a data table. For example, the service record storage 326 may store the service records in at least one of the service log 400 and the service log 500, respectively. Figure 4 and Figure 5 In some examples, the service log storage 326 may also distribute one or more service logs (eg, the service log 400 and / or the service log 500 ) to the vehicle maintenance database 116 via the network 114 .

[0063] Additionally or alternatively, the exemplary service record storage 326 may store at least one target distance between tire rotations, one or more target tire rotation configurations (e.g., crisscross, rearward cross, forward cross, front to rear, side to side, etc.), one or more target distances between fluid changes (e.g., target distances between oil changes, brake fluid changes, windshield washer fluid changes, transmission fluid changes, etc.), and one or more target fluid levels.

[0064] The service record storage 326 may be implemented by volatile memory (e.g., synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS dynamic random access memory (RDRAM), etc.) and / or non-volatile memory (e.g., flash memory). The service record storage 326 may be additionally or alternatively implemented by one or more double data rate (DDR) memories, such as DDR, DDR2, DDR3, DDR4, mobile DDR (mDDR), etc. The service record storage 326 may be additionally or alternatively implemented by one or more mass storage devices, such as hard disk drives, optical disk drives, digital versatile disk drives, etc. Although in the illustrated example, the service record storage 326 is shown as a single database, the service record storage 326 may be implemented by any number and / or type of databases. In addition, the data stored in the service record storage 326 may be in any data format, such as, for example, binary data, comma-delimited data, tab-delimited data, structured query language (SQL) structures, etc.

[0065] Figure 4 An exemplary service log 400 for a tire rotation maintenance event is shown as generated by the vehicle maintenance diagnostic processor 100 and also stored in the service record storage 326. The service log 400 (which in some examples may be implemented as a data table) includes one or more previous tire configurations 402A, one or more new tire configurations 402B, one or more validity checks 404, one or more vehicle locations 406, one or more vehicle distances 408, one or more times and dates 410, one or more total configuration distances 412, and one or more target tire rotation distances 414. In addition, the exemplary service log 400 includes one or more tire rotation service records 416, 418, 420, 422, and 424. Figure 4 In the example of FIG. 1 , the manufacturer recommends that the distance between tire rotations for vehicle 102 be 9,000 miles.

[0066] For example, the tire rotation service record 416 shows that the tires 104 of the vehicle 102 were rotated from configuration 1 to configuration 2 and that it was a valid rotation. In addition, the rotation was completed at Bob's Auto Service in Detroit, Michigan at 4:52 PM on 9 / 24 / 16 and the vehicle 102 had 9,000 miles on it at the time of the rotation. Since this was the first tire rotation completed for the vehicle 102, the total distance traveled on configuration 1 was 9,000 miles. In order to balance the distance traveled on configurations 1 and 2, the distance calibrator 320 determines that the next tire rotation should be completed when the vehicle distance is 18,000 miles (i.e., the vehicle 102 traveled 9,000 miles on configuration 2, thereby balancing the distance traveled on configurations 1 and 2).

[0067] In addition, the tire rotation service record 418 shows that the tires 104 of the vehicle 102 were rotated from configuration 2 to configuration 1 and that it was a valid rotation. Furthermore, the rotation was completed at Bill's Tire in Chicago, IL at 8:30 AM on 11 / 12 / 16 and the vehicle 102 had 19,500 miles on it at the time of the rotation. After this tire rotation, the total distance traveled on configuration 2 was 10,500 miles. In order to balance the distance traveled on configuration 1 and configuration 2, the distance calibrator 320 determines that the next tire rotation should be completed when the vehicle distance is 30,000 miles (i.e., the vehicle 102 traveled 10,500 miles on configuration 1, thereby balancing the distance traveled on configuration 1 and configuration 2).

[0068] In addition, the tire rotation service record 420 shows that the tires 104 of the vehicle 102 were rotated from configuration 1 to configuration 2 and that it was a valid rotation. In addition, the rotation was completed at the tire rotation service in Milwaukee, Wisconsin at 1 / 3 / 17 12:30 PM and the vehicle 102 had 29,000 miles on it at the time of the rotation. After this tire rotation, the total distance traveled on configuration 1 was 18,500 miles. In order to balance the distance traveled on configuration 1 and configuration 2, the distance calibrator 320 determines that the next tire rotation should be completed when the vehicle distance is 37,000 miles (i.e., the vehicle 102 has traveled 8,000 miles on configuration 2, thereby balancing the distance traveled on configuration 1 and configuration 2).

[0069] In addition, the tire rotation service record 422 shows that the tires 104 of the vehicle 102 were rotated from configuration 2 to configuration 1 and that it was a valid rotation. In addition, the rotation was completed at Bill's Tire in Chicago, Illinois at 6:00 PM on 2 / 27 / 17 and the vehicle 102 had 37,000 miles on it at the time of the rotation. After this tire rotation, the total distance traveled on configuration 2 was 18,500 miles. As the distance traveled on configuration 1 and configuration 2 are currently balanced, the distance calibrator 320 determines that the next tire rotation should be completed when the distance between rotations is the manufacturer's recommended distance (9,000 miles in the example shown) and determines that the rotation should be completed when the vehicle distance is 46,000 miles.

[0070] In addition, the tire rotation service record 424 shows that the tires 104 of the vehicle 102 were rotated from configuration 1 to configuration X (e.g., neither configuration 1 nor configuration 2) and that it was an invalid rotation. In addition, the rotation was completed at Bob's Auto Service in Detroit, Michigan at 11:00 AM on 7 / 8 / 17 and the vehicle had 46,500 miles on it at the time of the rotation. After this tire rotation, the total distance traveled on configuration 1 was 28,000 miles. However, because the rotation was completed incorrectly, the distance calibrator 320 sets a goal to correct the incorrect tire rotation as quickly as possible. Thus, in the example shown, the distance calibrator 320 sets a goal to complete the next tire rotation when the vehicle has a distance of 46,500 miles.

[0071] Figure 5An exemplary service log 500 for a fluid change maintenance event is shown as generated by the vehicle maintenance diagnostic processor 100 and also stored in the service record storage 326. The service log 500 (which in some examples may be implemented as a data table) includes one or more fluid change descriptions 502, one or more validity checks 504, one or more vehicle locations 506, one or more vehicle distances 508, one or more times and dates 510, one or more distances since a previous change 512, and one or more target next fluid change distances 514. In addition, the exemplary service log 500 includes one or more fluid change service records 516, 518, 520, and 522.

[0072] For example, the fluid change service record 516 shows that the fluid 110 that was changed was brake fluid and that it was a valid fluid change. Additionally, the fluid change was completed at Bob's Auto Service in Detroit, Michigan on 8 / 22 / 16 at 2:54 PM and there were 8,500 miles on the vehicle 102 at the time of the fluid change. Since this was the first brake fluid change performed on the vehicle 102, the distance since the last change was 8,500 miles. Additionally, the manufacturer-recommended (e.g., target) distance between brake fluid changes is 40,000 miles. Therefore, the target distance for the next brake fluid change is 48,500 miles.

[0073] In addition, the fluid change service record 518 shows that the fluid 110 that was changed was oil and that it was a valid fluid change. In addition, the fluid change was completed at Tim's Oil Change in Chicago, IL on 12 / 5 / 16 at 10:35 AM and that there were 19,000 miles on the vehicle 102 at the time of the fluid change. Since this was the first oil change performed on the vehicle 102, the distance since the last change was 19,000 miles. In addition, the manufacturer's recommended (e.g., target) distance between oil changes is 20,000 miles. Therefore, the target distance for the next oil change is 39,000 miles.

[0074] Additionally, the fluid change service record 520 shows that the fluid 110 that was changed was coolant and that it was a valid fluid change. Additionally, the fluid change was completed on 1 / 24 / 17 at 2:17 PM at a fluid change service in Milwaukee, Wisconsin, and there were 29,000 miles on the vehicle 102 at the time of the fluid change. Since this was the first coolant change performed on the vehicle 102, the distance since the last change was 29,000 miles. Additionally, the manufacturer-recommended (e.g., target) distance between coolant changes is 35,000 miles. Therefore, the target distance for the next coolant change is 64,000 miles.

[0075] In addition, the fluid change service record 522 shows that the fluid 110 that was changed was oil. However, the fluid change was ineffective (i.e., too much or not enough oil was added to the vehicle 102 after the fluid change). In addition, the fluid change was completed at Tim's Oil Change in Chicago, IL on 3 / 6 / 17 at 7:05 PM, and the vehicle 102 had 38,500 miles on it at the time of the fluid change (500 miles less than the next target fluid change distance 514 determined by the fluid change service record 518). Since the previous oil change on the vehicle 102 was completed at 19,000 miles, the distance since the last change is 19,500 miles. However, since the fluid change was completed incorrectly, the distance calibrator 320 sets a goal to correct the incorrect fluid change as quickly as possible. Therefore, in the example shown, the distance calibrator 320 sets a goal to complete the next oil change when the vehicle distance is 38,500 miles.

[0076] Although Figure 3 The implementation is shown in Figure 1 The vehicle maintenance diagnostic processor 100 is an exemplary embodiment of the present invention. Figure 3 One or more of the elements, processes and / or devices shown in the drawings may be combined, divided, rearranged, omitted, eliminated and / or implemented in any other manner. In addition, the exemplary tire position data collector 302, the exemplary fluid level data collector 304, the exemplary maintenance event detector 306, the exemplary parameter recorder 308, the exemplary GPS 310, the exemplary clock 312, the exemplary odometer 314, the exemplary maintenance event validator 316, the exemplary incorrect maintenance alert generator 318, the exemplary distance calibrator 320, the exemplary target maintenance alert generator 322, the exemplary maintenance scheduler 324, the exemplary service record storage 326 and / or (more generally) Figure 3The exemplary vehicle maintenance diagnostic processor 100 may be implemented by hardware, software, firmware, and / or any combination of hardware, software, and / or firmware. Thus, for example, any of the exemplary tire position data collector 302, the exemplary fluid level data collector 304, the exemplary maintenance event detector 306, the exemplary parameter recorder 308, the exemplary GPS 310, the exemplary clock 312, the exemplary odometer 314, the exemplary maintenance event validator 316, the exemplary incorrect maintenance alert generator 318, the exemplary distance calibrator 320, the exemplary target maintenance alert generator 322, the exemplary maintenance scheduler 324, the exemplary service record storage 326, and / or (more generally) the exemplary vehicle maintenance diagnostic processor 100 may be implemented by one or more analog or digital circuits, logic circuits, programmable processors, application specific integrated circuits (ASICs), programmable logic devices (PLDs), and / or field programmable logic devices (FPLDs). When reading any of the device or system claims of this patent for covering purely software and / or firmware implementations, at least one of the exemplary tire position data collector 302, exemplary fluid level data collector 304, exemplary maintenance event detector 306, exemplary parameter recorder 308, exemplary GPS 310, exemplary clock 312, exemplary odometer 314, exemplary maintenance event validator 316, exemplary incorrect maintenance alert generator 318, exemplary distance calibrator 320, exemplary target maintenance alert generator 322, exemplary maintenance scheduler 324, and / or exemplary service record storage 326 is hereby expressly defined as comprising a non-transitory computer-readable storage device or storage disk, such as a memory, a digital versatile disk (DVD), a compact disk (CD), a Blu-ray disk, etc., including software and / or firmware. In addition, Figure 3 The exemplary vehicle maintenance diagnostic processor 100 includes Figure 3 In addition to or instead of those shown in Figure 3 Those shown in , may include one or more elements, processes and / or devices, and / or may include more than one of any or all of the shown elements, processes and devices.

[0077] Figures 6 to 10 The diagram shows a method for implementing Figure 1 Flowchart of an exemplary method of the vehicle maintenance diagnostic processor 100. In these examples, the method can be implemented using machine-readable instructions, which include instructions for a processor (such as the following combined Fig.11The program may be embodied in software stored on a non-transitory computer-readable storage medium such as a CD-ROM, floppy disk, hard drive, digital versatile disk (DVD), Blu-ray disk, or memory associated with the processor 1112, but the entire program and / or portions thereof may alternatively be executed by a device other than the processor 1112 and / or embodied in firmware or dedicated hardware. In addition, although reference is made to Figures 6 to 10 The flowchart shown describes an exemplary procedure, but many other methods of implementing the exemplary vehicle maintenance diagnostic processor 100 may be used instead. For example, the order of execution of the blocks may be changed, and / or some of the blocks described may be changed, eliminated, or combined. Additionally or alternatively, any or all of the blocks may be implemented by one or more hardware circuits (e.g., discrete and / or integrated analog and / or digital circuits, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), comparators, operational amplifiers (op-amps), logic circuits, etc.) that are structured to perform corresponding operations without executing software or firmware.

[0078] As mentioned above, Figures 6 to 10 The exemplary processes of can be implemented using coded instructions (e.g., computer and / or machine readable instructions) stored on a non-transitory computer and / or machine readable medium (such as a hard drive, flash memory, read-only memory, compact disk, digital versatile disk, cache, random access memory, and / or any other storage device or storage disk, where information is stored for any duration (e.g., for a long time, permanently, for a brief instance, for temporary buffering, and / or for caching information)). As used herein, the term non-transitory computer readable medium is expressly defined to include any type of computer readable storage device and / or storage disk, and excludes propagating signals and excludes transmission media. "Including" and "comprising" (and all forms and tenses thereof) are used as open terms in this article. Therefore, whenever a claim lists any form of "include" or "comprise" (e.g., comprises, includes, comprising, including, etc.) followed by anything, it should be understood that additional elements, items, etc. may be present without exceeding the scope of the corresponding claim. As used herein, when the phrase "at least" is used as a transitional term in the preamble of a claim, it is open-ended in the same manner that the terms "comprising" and "including" are open-ended.

[0079] Figure 6The example method 600 begins at block 602. At block 602, the example tire position data collector 302 receives tire information (e.g., tire pressure, tire temperature, tire orientation, tire rotation, TPMS sensor serial number, etc.) from the TPMS sensors 106A, 106B, 106C, and 106D and receives wheel assembly information (e.g., wheel assembly rotation, etc.) from the wheel assembly rotation sensors 108A, 108B, 108C, and 108D. Additionally, at block 602, the example fluid level data collector 304 receives fluid level information (e.g., 50% full, 25% empty, 4 liters, 3 gallons, etc.) from the fluid level sensor 112. Additionally, at block 602, the tire position data collector 302 and the fluid level data collector 304 may distribute the received information to the example maintenance event detector 306.

[0080] At block 604, the maintenance event detector 306 determines whether a vehicle maintenance event has occurred using the information received at block 602. For example, in response to determining that one or more tires 104 of the vehicle 102 have changed position based on information collected from the TPMS sensors 106A, 106B, 106C, and 106D and the wheel assembly rotation sensors 108A, 108B, 108C, and 108D, the maintenance event detector 306 determines that a tire rotation event has occurred. Additionally or alternatively, in response to determining that the level of the fluid 110 has changed from a first level to a second level based on information collected from the fluid level sensor 112, the maintenance event detector 306 determines that a fluid change event has occurred. In response to at least one of a tire rotation event and / or a fluid change event occurring, processing transfers to block 606. Alternatively, in response to neither a tire rotation event nor a fluid change event occurring, processing returns to block 602.

[0081] At block 606, the maintenance event detector 306 notifies the parameter recorder 308 of the detection. In response to the notification, the parameter recorder 308 retrieves at least one of: the location of the vehicle 102 at the time of the vehicle maintenance event from the GPS 310, the time when the maintenance event was completed from the clock 312, and the total distance traveled by the vehicle at the time of the vehicle maintenance event from the odometer 314.

[0082] At block 608, the parameter recorder 308 also determines a service station (e.g., a repair shop, dealership, oil change shop, car wash, etc.) by associating the GPS-based location of the vehicle 102 with the service station based on the known service station locations of the GPS mapping program using the location of the vehicle 102 retrieved at block 606. For example, if the GPS location of the vehicle 102 at the time of the maintenance event was 42.338N, -88.661E and the nearest service location was Bob's Tire Rotation Service at 42.339N, -88.660E, the parameter recorder 308 can determine that the maintenance event was completed at Bob's Tire Rotation Service.

[0083] At block 610, the maintenance event detector 306 will determine whether the maintenance event detected at block 604 is a tire rotation. In response to determining that the maintenance event is not a tire rotation (e.g., the maintenance event is a fluid change), processing transfers to block 612. Alternatively, in response to determining that the maintenance event is a tire rotation, processing transfers to block 614.

[0084] At block 612, combined Figure 7 In further detail and in response to determining that the vehicle maintenance event is a fluid change, the vehicle maintenance diagnostic processor 100 will execute a complete diagnostic routine for the fluid change event. Similarly, at block 614, in conjunction with Figure 8 In further detail and in response to determining that the vehicle maintenance event is a tire rotation event, the vehicle maintenance diagnostic processor 100 will perform a full diagnostic routine for the tire rotation event. In response to completing at least one of block 612 and block 614 , processing transfers to block 616 .

[0085] At block 616, at least one of the parameter recorder 308, the maintenance event validator 316, and the distance scaler 320 distributes the diagnostic information to the service record storage 326 for storage. In some examples, the diagnostic information stored in the service record storage 326 may include at least one of a GPS location for the maintenance event, a service station for the maintenance event, a date and time of the maintenance event, a distance traveled by the vehicle at the time of the maintenance event, a tire configuration after the maintenance event, a fluid level after the maintenance event, a validity flag for the maintenance event, and a target distance for future maintenance events.

[0086] At block 618, the vehicle maintenance diagnostic processor 100 determines whether it is desired to continue monitoring the vehicle maintenance diagnostic. In some examples, the vehicle maintenance diagnostic is continuously monitored. Additionally or alternatively, the vehicle maintenance diagnostic is monitored as long as the vehicle 102 is in motion. Additionally or alternatively, the vehicle maintenance diagnostic is monitored based on a schedule determined by a computer using at least one of a predetermined schedule and / or a schedule that is dynamically updated based on one or more parameters of the vehicle 102. In response to determining that it is desired to continue monitoring the vehicle maintenance diagnostic, processing returns to block 602 of the exemplary method 600. Alternatively, in response to determining that it is no longer desired to continue monitoring the vehicle maintenance diagnostic, Figure 6 The exemplary method 600 ends.

[0087] Figure 7 The following diagram shows the process that can be performed to perform fluid change diagnostics ( Figure 6 , block 612), the diagnosis is performed in response to detecting a fluid change. Referring to the previous figures and associated descriptions, Figure 7 The exemplary method of begins execution at block 702 where the distance calibrator 320 determines a target distance for a second fluid change. In some examples, the distance calibrator 320 may determine the target distance based on a maintenance schedule for the vehicle 102. For example, if an oil change occurs at 3,000 miles and the target driving distance between oil changes is 8,000 miles, the distance calibrator 320 will set a target of 11,000 miles for the second oil change.

[0088] At block 704, maintenance event validator 316 retrieves at least one of a target fluid fill level and a fluid fill level tolerance for fluid 110 from service record storage 326. At block 706, maintenance event validator 316 also retrieves from service record storage 326 a current fluid fill level previously acquired from fluid level sensor 112.

[0089] At box 708, the maintenance event validator 316 uses at least one of the target fluid fill level, the fluid fill level tolerance, and the current fluid fill level to determine whether the most recent fluid change is valid. In some examples, determining whether the most recent fluid change is valid can also include calculating the difference between the current fluid fill level and the target fluid fill level and determining whether the resulting value is less than the fluid fill level tolerance. For example, if the current fluid fill level is 4 inches, the target fluid fill level is 4.5 inches, and the fluid fill level tolerance is + / -1 inch, the difference is 0.5 inches, which is less than 1 inch, so the fluid change is valid. In response to determining that the fluid 110 is not filled to within the tolerance of the target level, processing transfers to box 710. Alternatively, in response to determining that the fluid 110 is filled to the target level, processing transfers to box 712.

[0090] At block 710 , in response to determining that the fluid 110 is not filled to within tolerance of the target level, the improper maintenance alert generator 318 will generate an alert for distribution to a display, audio system, or other device capable of notifying a user of the vehicle 102 .

[0091] At box 712, in response to determining that the level of fluid 110 is within the target tolerance, vehicle 102 continues normal operation and the incorrect maintenance alert generator 318 does not generate an alert. After completing at least one of box 710 or box 712, Figure 7 The exemplary method ends and processing returns to Figure 6 Block 616 of the exemplary method 600 .

[0092] Figure 8 The following diagram shows the process that can be performed to perform tire rotation diagnosis ( Figure 6 , block 614), the diagnosis is performed in response to detecting tire rotation. Referring to the previous figures and associated descriptions, Figure 8 The exemplary method of the invention begins at block 802, and combines Fig. 9 In further detail, at block 802 , the distance calibrator 320 determines a target distance for the next tire rotation event.

[0093] After determining the target distance for the next tire rotation event, processing transfers to block 804. At block 804, the maintenance event validator 316 retrieves the previous tire rotation configuration from the service record storage 326. In some examples, the retrieved previous configuration may be one of the first tire configuration or the second tire configuration. At block 806, the maintenance event validator 316 will also retrieve the target post-rotation tire configuration from the service record storage 326. In some examples, the target post-rotation tire configuration will be a configuration relative to the previous tire rotation configuration determined at block 804. For example, if the previous configuration was the first configuration, the target post-rotation configuration will be the second configuration. Similarly, if the previous configuration was the second configuration, the target post-rotation configuration will be the first configuration.

[0094] At block 808 , the maintenance event verifier 316 determines the tire configuration after the tire rotation. In some examples, determining the tire configuration after the rotation also includes determining the current position of one or more tires 104 of the vehicle 102 using one or more TPMS sensors 106 in conjunction with one or more wheel assembly rotation sensors 108 .

[0095] At block 810, the maintenance event validator 316 determines whether the most recent tire rotation is valid using the target rear tire configuration retrieved at block 806 and the current position of the one or more tires 104 determined at block 808. In some examples, determining whether the most recent tire rotation is valid also includes determining whether the current position of the one or more tires 104 matches the position suggested by the target rear tire configuration. In response to determining that the one or more tires 104 are not in the target position, processing transfers to block 812. Alternatively, in response to determining that each tire 104 is in the target position, processing transfers to block 814.

[0096] At block 812, in response to determining that one or more tires 104 are not in the target position, the incorrect maintenance alert generator 318 generates an alert for distribution to a display, audio system, or other device capable of notifying a user of the vehicle 102. In some examples, the generated alert may include a notification that one or more tires 104 are incorrectly rotated. Additionally or alternatively, the generated alert may include a list of the one or more tires 104 that are rotated to an incorrect position.

[0097] At box 814, in response to determining that each tire 104 is in the target position, the vehicle 102 continues to operate normally and the incorrect maintenance alert generator 318 does not generate an alert. After completing at least one of box 812 or box 814, Figure 8 The exemplary method ends and processing returns to Figure 6 Block 616 of the exemplary method 600 .

[0098] Fig. 9 , which can be performed to set a distance target for the next tire rotation ( Figure 8 , block 802). Fig. 9 The exemplary method shown in describes a vehicle 102 utilizing two (2) tire rotation configurations, but the examples disclosed herein may function with any number of tire rotation configurations (e.g., tire position configurations). Referring to the preceding figures and associated descriptions, Fig. 9 The exemplary method of begins execution at block 902 where the distance calibrator 320 retrieves one or more tire rotation service records from the service record storage 326 .

[0099] At block 904, distance calibrator 320 determines a total distance that vehicle 102 has traveled in the first tire rotation configuration using the tire rotation service record retrieved at block 902. In some examples, determining the total distance that vehicle 102 has traveled in the first tire rotation configuration further includes summing the distances traveled during one or more periods that vehicle 102 is utilizing the first tire rotation configuration.

[0100] At block 906, the distance calibrator 320 determines the total distance that the vehicle 102 has traveled in the second tire rotation configuration using the tire rotation service record retrieved at block 902. In some examples, determining the total distance that the vehicle 102 has traveled in the second tire rotation configuration also includes summing the distances traveled during one or more time periods that the vehicle 102 is utilizing the second tire rotation configuration. Alternatively, determining the total distance that the vehicle 102 has traveled in the second tire rotation configuration may also include subtracting the distance that the vehicle 102 has traveled in the first tire rotation configuration (determined at block 904) from the total distance that the vehicle 102 has traveled.

[0101] At block 908, the distance calibrator 320 determines whether the most recent tire rotation event was a rotation to the first tire configuration or the second tire configuration (e.g., whether the current tire configuration is the first tire configuration or the second tire configuration) using the service record retrieved at block 902. In response to determining that the most recent rotation was a rotation to the first tire configuration, processing transfers to block 910. Alternatively, in response to determining that the most recent rotation was a rotation to the second rotation configuration, processing transfers to block 912.

[0102] At block 910 , in response to determining that the current tire configuration is the first tire configuration, the distance calibrator 320 will also determine the vehicle distance rotated from the first tire configuration to the second tire configuration so that the total distance on the first tire configuration matches the total distance on the second tire configuration.

[0103] In some examples, determining the vehicle distance for the next tire rotation to balance (e.g., equalize) the distances traveled on the first tire configuration and the second tire configuration also includes determining a difference between the total distance traveled on the first tire configuration determined at block 902 and the total distance traveled on the second tire configuration determined at block 904. In calculating the difference, the distance calibrator 320 also adds the difference to the manufacturer-specified recommended (e.g., target) rotation distance and the distance at the previous tire rotation. In some examples, the value from this sum is the target distance for the next tire rotation.

[0104] Similarly, at block 912, in response to determining that the current tire configuration is the second tire configuration, the distance calibrator 320 will also determine the vehicle distance to rotate back to the first tire configuration so that the total distance on the second tire configuration matches the total distance on the first tire configuration. In some examples, determining the vehicle distance for the next tire rotation at block 912 to balance (e.g., equalize) the distances traveled on the first and second tire configurations also utilizes the algorithm described in conjunction with block 910.

[0105] At block 914, the distance calibrator 320 also distributes the target distance determined at block 910 or block 912 to the service record storage 326. In response to the storage of the target distance, Fig. 9Example 802 ends and processing returns to Figure 8 Block 804 of the exemplary method.

[0106] Fig.10 The exemplary method 1000 begins at block 1002. At block 1002, the targeted maintenance alert generator 322 determines a buffer distance before targeting maintenance (e.g., a specific distance until a maintenance event is targeted) at which a user of the vehicle 102 is to be warned about an upcoming or overdue maintenance event.

[0107] At block 1004, target maintenance alert generator 322 determines a vehicle alert distance using the buffer distance calculated at block 1002 in addition to the target maintenance distance previously calculated by distance scaler 320 to warn a user of vehicle 102 of an upcoming or overdue maintenance event. In some examples, determining the vehicle alert distance to warn the user further includes subtracting the buffer distance from the target maintenance distance.

[0108] At block 1006, the target maintenance alert generator 322 retrieves the current vehicle distance from the odometer 314. At block 1008, the target maintenance alert generator 322 determines whether the current vehicle distance retrieved from the odometer 314 is greater than the vehicle alert distance. In response to the current vehicle distance (e.g., the odometer 314 distance) being greater than or equal to the vehicle alert distance, processing transfers to block 1010. Alternatively, in response to the current vehicle distance being less than the vehicle alert distance, processing transfers to block 1012.

[0109] At block 1010, the targeted maintenance alert generator 322 generates an alert for distribution to a display, audio system, or other device capable of notifying a user of the vehicle 102. In some examples, the alert may include a vehicle distance (e.g., odometer 314 distance) when maintenance is required (e.g., maintenance is targeted). Additionally or alternatively, the alert may include a distance until maintenance is targeted (e.g., odometer 314 distance subtracted from the vehicle alert distance). Additionally or alternatively, the alert may include a suggested service station and time to schedule a maintenance event for the vehicle 102 using the maintenance scheduler 324.

[0110] At block 1012, in response to the current vehicle distance (e.g., odometer 314 distance) being less than the vehicle alert distance, the vehicle 102 continues normal operation and the target maintenance alert generator 322 does not generate an alert. After completing at least one of block 1010 or block 1012, Fig.10 The exemplary method 1000 ends.

[0111] Fig.11 Is able to execute instructions to implement Figures 6 to 10 Methods and Figure 3The processor platform 1100 may be, for example, a server, a personal computer, a mobile device (e.g., a cell phone, a smart phone, a tablet computer (such as an iPad) or a processor platform 1100 of the vehicle maintenance diagnostic processor 100. TM )), personal digital assistant (PDA), Internet appliance, DVD player, CD player, digital video recorder, Blu-ray player, game console, personal video recorder, set-top box, or any other type of computing device.

[0112] The processor platform 1100 of the illustrated example includes a processor 1112. The processor 1112 of the illustrated example is hardware. For example, the processor 1112 can be implemented by one or more integrated circuits, logic circuits, microprocessors or controllers from any desired series or manufacturer. The hardware processor can be a semiconductor-based (e.g., silicon-based) device. In this example, the processor 1112 implements the exemplary vehicle maintenance diagnostic processor 100, which in some examples may include or otherwise implement an exemplary tire position data collector 302, an exemplary fluid level data collector 304, an exemplary maintenance event detector 306, an exemplary parameter recorder 308, an exemplary GPS 310, an exemplary clock 312, an exemplary odometer 314, an exemplary maintenance event verifier 316, an exemplary incorrect maintenance alarm generator 318, an exemplary distance calibrator 320, an exemplary target maintenance alarm generator 322, and an exemplary maintenance scheduler 324.

[0113] The processor 1112 of the illustrated example includes a local memory 1113 (e.g., a cache). The processor 1112 of the illustrated example communicates with a main memory including a volatile memory 1114 and a non-volatile memory 1116 via a bus 1118. The volatile memory 1114 may be implemented by a synchronous dynamic random access memory (SDRAM), a dynamic random access memory (DRAM), a RAMBUS dynamic random access memory (RDRAM), and / or any other type of random access memory device. The non-volatile memory 1116 may be implemented by a flash memory and / or any other desired type of memory device. Access to the main memory 1114, 1116 is controlled by a memory controller.

[0114] The processor platform 1100 of the illustrated example also includes an interface circuit 1120. The interface circuit 1120 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and / or a PCI express interface.

[0115] In the example shown, one or more input devices 1122 are connected to the interface circuit 1120. The input devices 1122 allow a user to enter data and / or commands into the processor 1112. The input devices may be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, buttons, a mouse, a touch screen, a trackpad, a trackball, an isopoint device, and / or a voice recognition system.

[0116] One or more output devices 1124 are also connected to the interface circuit 1120 of the illustrated example. The output device 1124 can be implemented, for example, by a display device (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display, a cathode ray tube display (CRT), a touch screen, a tactile output device, a printer, and / or a speaker). Therefore, the interface circuit 1120 of the illustrated example typically includes a graphics driver card, a graphics driver chip, and / or a graphics driver processor.

[0117] The interface circuitry 1120 of the illustrated example also includes communication devices, such as transmitters, receivers, transceivers, modems, and / or network interface cards, to facilitate the exchange of data with an external machine (e.g., any type of computing device) via a network 1126 (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, a coaxial cable, a cellular telephone system, etc.).

[0118] The processor platform 1100 of the illustrated example also includes one or more mass storage devices 1128 for storing software and / or data. Examples of such mass storage devices 1128 include floppy disk drives, hard disk drives, optical disk drives, Blu-ray disk drives, RAID systems, and digital versatile disk (DVD) drives.

[0119] Figures 6 to 10 The encoded instructions 1132 may be stored in the mass storage device 1128, in the volatile memory 1114, in the non-volatile memory 1116, and / or on a removable tangible computer-readable storage medium (eg, a CD or DVD).

[0120] As can be appreciated from the foregoing, exemplary methods, apparatus, and articles of manufacture have been disclosed that enable the detection and recording of vehicle maintenance events to be automated, including at least one of tire rotations and fluid changes. Vehicles that do not receive scheduled maintenance may suffer unnecessary wear and tear that vehicles that do receive scheduled maintenance do not suffer. Additionally, uncompleted maintenance and unrecorded maintenance may void the warranty on a vehicle owned by a consumer. Thus, automatically detecting and recording maintenance events will not only reduce wear and tear on the vehicle, but will also simplify warranty disputes regarding maintenance completed on the vehicle. Additionally, manufacturers or dealers may use these notifications to suggest or incentivize the use of their facilities to purchase services.

[0121] Although certain exemplary methods, apparatus, and articles of manufacture have been disclosed herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus, and articles of manufacture that fully fall within the scope of the claims of this patent.

[0122] According to the present invention, there is provided an apparatus having: a maintenance event detector for detecting a first maintenance event including at least one of a tire rotation event or a fluid change event; a parameter recorder for storing a vehicle position, a time, and a vehicle travel distance when the first maintenance event occurs in a service log; and a distance calibrator for determining a target distance for a second maintenance event based on the information stored in the service log.

[0123] According to an embodiment, the maintenance event detector will also: detect a tire rotation event when one or more tires change position on the vehicle; and detect a fluid change event when the level of the fluid changes from a first level to a second level.

[0124] According to an embodiment, the above invention is also characterized by a maintenance event verifier: used to determine whether the second tire position configuration matches the target second tire position configuration when a tire rotation event is detected; and when a fluid change event is detected, determine whether the second level of the fluid is within the tolerance of the target level of the fluid.

[0125] According to an embodiment, the above invention also features an improper maintenance alert generator that alerts a user of the vehicle when: the second tire position configuration does not match a target second tire position configuration; or the second level of fluid is not within a tolerance of a target level of fluid.

[0126] According to an embodiment, the distance calibrator is further used to determine a target distance for a second maintenance event, the second maintenance event comprising a tire rotation event, such that when the tire rotation event is detected, the distance traveled on the first tire position configuration matches the distance traveled on at least the second tire position configuration.

[0127] According to an embodiment, the parameter recorder will also be used to determine the service station that completed the first maintenance event based on the vehicle location.

[0128] According to an embodiment, the above invention is further characterized by a targeted maintenance alert generator for alerting a user of the vehicle to target a second maintenance event based on a current vehicle travel distance and a target distance for the second maintenance event.

[0129] According to the present invention, an apparatus is provided having a vehicle maintenance diagnostic processor programmed to detect a first tire rotation event, and wherein the processor records at least one of a vehicle position, a time, and a vehicle travel distance for the first tire rotation event and calculates a target distance for a second tire rotation event based on the recorded information.

[0130] According to an embodiment, the vehicle maintenance diagnostic processor is further programmed to detect a first tire rotation event when a first tire position configuration changes to a second tire position configuration, the tire position being determined by comparing orientation data of one or more tire pressure monitoring system sensors with displacement data of one or more wheel assemblies.

[0131] According to an embodiment, the vehicle maintenance diagnostic processor is further programmed to determine a target distance for a second tire rotation event such that when the first tire rotation event is detected, the distance traveled on the first tire position configuration matches the distance traveled on at least the second tire position configuration.

[0132] According to an embodiment, the vehicle maintenance diagnostic processor is further programmed to determine whether the second tire position configuration matches a target second tire position configuration when the first tire rotation event is detected.

[0133] According to an embodiment, the vehicle maintenance diagnostic processor is further programmed to alert a user of the vehicle when the second tire position configuration does not match the target second tire position configuration.

[0134] According to an embodiment, the vehicle maintenance diagnostic processor is further programmed to determine a service station that completed the first tire rotation event based on the vehicle location.

[0135] According to an embodiment, the vehicle maintenance diagnostic processor is further programmed to alert a user of the vehicle to target a second tire rotation event based on the current vehicle travel distance and the target distance for the second tire rotation event.

[0136] According to the present invention, a method includes: detecting a first maintenance event including at least one of a tire rotation event or a fluid change event; in response to detecting the first maintenance event, storing a vehicle position, a time, and a vehicle travel distance when the first maintenance event occurs in a service log; and determining a target distance for a second maintenance event based on the information stored in the service log.

[0137] According to an embodiment, detecting the first maintenance event further comprises: detecting a tire rotation event in response to one or more tires changing positions on the vehicle; and detecting a fluid change event in response to a fluid level changing from a first level to a second level.

[0138] According to an embodiment, the above invention is also characterized in that, in response to detecting a tire rotation event, it is determined whether the second tire position configuration matches the target second tire position configuration; and in response to detecting a fluid change event, it is determined whether the second level of the fluid is within the tolerance of the target level of the fluid.

[0139] According to an embodiment, determining the target distance further comprises: in response to detecting a tire rotation event, determining a target distance for a second maintenance event, wherein the second maintenance event comprises a tire rotation event such that a distance traveled on a first tire position configuration matches a distance traveled on at least a second tire position configuration.

[0140] According to an embodiment, the above invention is further characterized in that the service station where the first maintenance event is completed is determined based on associating the vehicle location with the service station.

[0141] According to an embodiment, the above invention is further characterized by alerting a user of the vehicle to target a second maintenance event based on a current vehicle travel distance and a target distance for the second maintenance event.

Claims

1. A device for detecting and recording vehicle maintenance events, comprising: a maintenance event detector for detecting a first maintenance event, the first maintenance event being a tire rotation event in which tires of a vehicle are changed from a first tire configuration to a second tire configuration; a parameter recorder for storing the vehicle position, time and vehicle travel distance when the first maintenance event occurs in a service log; as well as Distance calibrator, which is used to: determining a target distance for a second maintenance event based on information stored in the service log; as well as and modifying the target distance so that the modified target distance causes a first distance traveled on the first tire configuration to match a second distance traveled on the second tire configuration, wherein determining the target distance to match the first distance traveled on the first tire configuration to the second distance traveled on the second tire configuration comprises determining a difference between a total distance traveled on the first tire configuration and a total distance traveled on the second tire configuration.

2. The apparatus of claim 1, wherein the maintenance event detector is further configured to: detecting the tire rotation event when one or more tires change position on the vehicle; and A fluid change event is detected when the level of the fluid changes from a first level to a second level.

3. The apparatus of claim 2, further comprising a maintenance event validator to: upon detecting the tire rotation event, determining whether the second tire position configuration matches a target second tire position configuration; and Upon detecting the fluid change event, a determination is made as to whether the second level of the fluid is within a tolerance of a target level of the fluid.

4. The apparatus of claim 3, further comprising an improper maintenance alert generator to warn a user of the vehicle when: the second tire position configuration does not match the target second tire position configuration; or The second level of the fluid is not within the tolerance of the target level of the fluid.

5. The apparatus of claim 1, wherein the second maintenance event is a tire rotation event. 6 . The apparatus of claim 1 , wherein the parameter recorder is further configured to determine a service station that completed the first maintenance event based on the vehicle location.

7. The apparatus of claim 1, further comprising a targeted maintenance alert generator to alert a user of the vehicle to target the second maintenance event based on a current vehicle travel distance and the modified target distance for the second maintenance event.

8. The apparatus of claim 7, further comprising a maintenance scheduler to: suggesting to the user of the vehicle a service station and time for the second maintenance event; and When the user of the vehicle accepts the suggested service station and time, the second maintenance event is scheduled at the suggested service station and time.

9. A device for detecting and recording vehicle maintenance events, comprising: A vehicle maintenance diagnostic processor programmed to detect a first tire rotation event, and wherein the processor records at least one of a vehicle position, a time, and a vehicle distance traveled for the first tire rotation event, and based on the recorded information modifies a target distance for a second tire rotation event such that a distance traveled on a first tire position configuration matches a distance traveled on a second tire position configuration, wherein determining the target distance to match a distance traveled on the first tire position configuration and a distance traveled on the second tire position configuration comprises determining a difference between a total distance traveled on the first tire position configuration and a total distance traveled on the second tire position configuration.

10. The apparatus of claim 9, wherein the vehicle maintenance diagnostic processor is further programmed to detect the first tire rotation event when a first tire position configuration changes to a second tire position configuration, the tire position being determined by comparing orientation data of one or more tire pressure monitoring system sensors with displacement data of one or more wheel assemblies.

11. The apparatus of claim 10, wherein the vehicle maintenance diagnostic processor is further programmed to determine whether the second tire position configuration matches a target second tire position configuration when the first tire rotation event is detected.

12. The apparatus of claim 11, wherein the vehicle maintenance diagnostic processor is further programmed to alert a user of the vehicle when the second tire position configuration does not match the target second tire position configuration.

13. The apparatus of claim 9, wherein the vehicle maintenance diagnostic processor is further programmed to determine a service station that completed the first tire rotation event based on the vehicle location.

14. The apparatus of claim 9, wherein the vehicle maintenance diagnostic processor is further programmed to alert a user of the vehicle to target the second tire rotation event based on a current vehicle travel distance and the target distance for the second tire rotation event.

Images