US20160162852A1 - Motor Vehicle Monitoring Method for Determining Driver Negligence of an Engine - Google Patents

Motor Vehicle Monitoring Method for Determining Driver Negligence of an Engine Download PDF

Info

Publication number
US20160162852A1
US20160162852A1 US15/045,602 US201615045602A US2016162852A1 US 20160162852 A1 US20160162852 A1 US 20160162852A1 US 201615045602 A US201615045602 A US 201615045602A US 2016162852 A1 US2016162852 A1 US 2016162852A1
Authority
US
United States
Prior art keywords
value
revolutions per
vehicle
odometer value
odometer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US15/045,602
Other versions
US9361607B1 (en
Inventor
Kenneth Carl Steffen Winiecki
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US15/045,602 priority Critical patent/US9361607B1/en
Priority to PCT/IB2016/052611 priority patent/WO2016178194A1/en
Application granted granted Critical
Publication of US9361607B1 publication Critical patent/US9361607B1/en
Publication of US20160162852A1 publication Critical patent/US20160162852A1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W40/00Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
    • B60W40/08Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to drivers or passengers
    • B60W40/09Driving style or behaviour
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102Bill distribution or payments
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60QARRANGEMENT OF SIGNALLING OR LIGHTING DEVICES, THE MOUNTING OR SUPPORTING THEREOF OR CIRCUITS THEREFOR, FOR VEHICLES IN GENERAL
    • B60Q9/00Arrangement or adaptation of signal devices not provided for in one of main groups B60Q1/00 - B60Q7/00, e.g. haptic signalling
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/20Administration of product repair or maintenance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/01Customer relationship services
    • G06Q30/012Providing warranty services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0645Rental transactions; Leasing transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08Insurance
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/008Registering or indicating the working of vehicles communicating information to a remotely located station
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0808Diagnosing performance data
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W2050/0062Adapting control system settings
    • B60W2050/0075Automatic parameter input, automatic initialising or calibrating means
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2510/00Input parameters relating to a particular sub-units
    • B60W2510/06Combustion engines, Gas turbines
    • B60W2510/0604Throttle position
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2510/00Input parameters relating to a particular sub-units
    • B60W2510/06Combustion engines, Gas turbines
    • B60W2510/0638Engine speed
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2510/00Input parameters relating to a particular sub-units
    • B60W2510/06Combustion engines, Gas turbines
    • B60W2510/0666Engine power
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2520/00Input parameters relating to overall vehicle dynamics
    • B60W2520/10Longitudinal speed
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2530/00Input parameters relating to vehicle conditions or values, not covered by groups B60W2510/00 or B60W2520/00
    • B60W2530/18Distance travelled
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2556/00Input parameters relating to data
    • B60W2556/10Historical data
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/08Interaction between the driver and the control system
    • GPHYSICS
    • G01MEASURING; TESTING
    • G01CMEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
    • G01C21/26Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
    • G01C21/34Route searching; Route guidance
    • G01C21/36Input/output arrangements for on-board computers
    • G01C21/3626Details of the output of route guidance instructions
    • G01C21/3629Guidance using speech or audio output, e.g. text-to-speech
    • GPHYSICS
    • G01MEASURING; TESTING
    • G01CMEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C22/00Measuring distance traversed on the ground by vehicles, persons, animals or other moving solid bodies, e.g. using odometers, using pedometers
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06MCOUNTING MECHANISMS; COUNTING OF OBJECTS NOT OTHERWISE PROVIDED FOR
    • G06M1/00Design features of general application
    • G06M1/28Design features of general application for zeroising or setting to a particular value
    • G06M1/30Design features of general application for zeroising or setting to a particular value using heart-shaped or similar cams; using levers
    • G06M1/303Design features of general application for zeroising or setting to a particular value using heart-shaped or similar cams; using levers with drums
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C2205/00Indexing scheme relating to group G07C5/00
    • G07C2205/02Indexing scheme relating to group G07C5/00 using a vehicle scan tool
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841Registering performance data
    • G07C5/085Registering performance data using electronic data carriers
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16ZINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
    • G16Z99/00Subject matter not provided for in other main groups of this subclass

Abstract

A motor vehicle monitoring method for determining driver negligence is carried out by a company in order to determine a final assessment for the vehicle. The method for determining driver negligence enables the company to calculate an average revolutions per initial odometer value and an average revolutions per secondary odometer value, where the average revolutions per secondary odometer value is a direct indication about operating state of the vehicle or an action of an end user during a designated time period. Then the company is able to adjust the contact agreement for the designated time period upon the final assessment, wherein the responsible party that violates the contact agreement is only liable for the respective damages. The method for determining driver negligence also validates the odometer and speedometer values from illegal tampering.

Description

  • The current application is a continuation-in-part (CIP) application of a U.S. non-provisional application Ser. No. 14/705,163 filed on May 6, 2015. The U.S. non-provisional application Ser. No. 14/705,163 claims a priority to the U.S. Provisional Patent application Ser. No. 62/025,909 filed on Jul. 17, 2014, the U.S. Provisional Patent application Ser. No. 62/025,911 filed on Jul. 17, 2014, the U.S. Provisional Patent application Ser. No. 62/025,915 filed on Jul. 17, 2014 and the U.S. Provisional Patent application Ser. No. 62/025,917 filed on Jul. 17, 2014.
  • FIELD OF THE INVENTION
  • The present invention relates generally to the field of automotive systems. More specifically, the present invention is a method of determining a driver's negligence during the break-in period of a new engine, a lease agreement, a rental agreement, and an insurance premium calculation based upon monitoring, recording and communicating data representative of operator and vehicle driving characteristics.
  • BACKGROUND OF THE INVENTION
  • Most vehicle related companies such as rental companies, car dealerships, and insurance companies utilize the total mileage of a vehicle so that each of these companies are able to determine their respective contacts based upon the total mileage and other related variables. Although different variables are utilized by these companies, the total mileage of the vehicles is considered to be the most important aspect as the total mileage is directly related to the mechanical condition of the engine and the other components of the drivetrain. However, the relationship between the total mileage and the condition of the engine can be misleading in some instances. For example, some high mileage cars may have engines that have been well maintained and revved with low engine revolutions while some low mileage cars may have engines that have been abused and revved with high engine revolutions. Normally a buyer would purchase the lower mileage car assuming it has the better engine compared to the high mileage car. In relation to the example, the lower mileage car has the worse conditioned engine compared to the engine of the higher mileage car. This provides a real challenge for used car buyers because they cannot find out the how the engine of a particular used car is operated for by the previous owner. The rental companies, car dealerships, and insurance companies are also faced with this problem as they would only consider the total mileage and not the total number of engine revolutions along with the total mileage.
  • The present invention takes into consideration the number of total revolutions of the engine and the total distance traveled by the vehicle or the total runtime of the engine so that the average revolutions per distance unit can be calculated. Resulting data of the present invention can be displayed within the control panel of the vehicle and uploaded to a remote serve as the resulting data provides valuable information not only for car buyers but also for car dealers, car rental companies, insurance companies, and many other similar vehicle related entities. More specifically, the present invention is a method of determining a driver's negligence of an engine based upon monitoring, recording and communicating data representative of operator and vehicle driving characteristics. For example, the resulting data is reflective upon the drivers' willingness to not abide by new engine break in procedures is adjustable retrospectively and can be prospectively set by relating the break in driving characteristics to predetermined safety standards. The present invention also determines a vehicle lease surcharge, a vehicle rental surcharge, and an insurance premium calculation based upon monitoring, recording and communicating data representative of operator and vehicle driving characteristics. The present invention further provides protection against odometer and speedometer tampering through the monitoring, recording and communicating data representative of operator and vehicle driving characteristics.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a flow chart illustrating the overall method of the present invention.
  • FIG. 2 is a flow chart illustrating visual display of the initial engine revolutions and the secondary engine revolutions within the overall method of the present invention.
  • FIG. 3 is a flow chart illustrating the warning notification detections within the overall method of the present invention.
  • FIG. 4 is a flow chart illustrating the warning notification detections within the overall method of the present invention and the speedometer being operational.
  • FIG. 5 is a flow chart illustrating the warning notification detections within the overall method of the present invention and the speedometer being non-operational.
  • FIG. 6 is a flow chart illustrating the warning notification detections within the overall method of the present invention and the odometer being non-operational.
  • FIG. 7 is a flow chart illustrating the warning notification detections within the overall method of the present invention and the engine load valve.
  • FIG. 8 is a flow chart illustrating the warning notification detections within the overall method of the present invention and throttle position value.
  • FIG. 9 is a flow chart illustrating the warning notification detections within the overall method of the present invention and the vehicle pitch and vehicle angle.
  • FIG. 10 is a flow chart illustrating the overall method of the present invention, wherein the present invention is implemented to determine the outcome of the engine warranty.
  • FIG. 11 is a flow chart illustrating the overall method of the present invention, wherein the present invention is implemented to determine the outcome of the lease agreement.
  • FIG. 12 is a flow chart illustrating the overall method of the present invention, wherein the present invention is implemented to determine the outcome of the rental agreement.
  • FIG. 13 is a flow chart illustrating the overall method of the present invention, wherein the present invention is implemented to determine the outcome of the insurance policy premium.
  • DETAIL DESCRIPTIONS OF THE INVENTION
  • All illustrations of the drawings are for the purpose of describing selected versions of the present invention and are not intended to limit the scope of the present invention.
  • The present invention is a motor vehicle monitoring method for determining driver negligence of an engine. The present invention collects raw data elements in regards to engine revolutions and the distance traveled, which are representative of an operating state of the vehicle or an action of the operator of the vehicle. The total distance traveled by a vehicle, a plurality of engine revolutions, and an average revolutions per distance unit (ARDU) valve for the total distance traveled, which are utilized for the calculations of the present invention, are sequentially shown through an odometer of the vehicle. More specifically, the ARDU valve is calculated by an engine control unit (ECU) of the vehicle as the plurality of engine revolutions that is timestamped within the ECU is divided by the total distance traveled by the vehicle.
  • The steps of the present invention are implemented on a vehicle by a company so that the company is able to determine a final assessment for the vehicle through the present invention. In reference to FIG. 1, the present invention requires an initial odometer value and an average revolutions per initial odometer value for the vehicle so that the company can start implementing the present invention. More specifically, the initial odometer value is displayed within the odometer as the initial odometer value represents the total distance traveled by the vehicle up to that instant. The average revolutions per initial odometer value is displayed within the odometer as the average revolutions per initial odometer value is cautiously calculated through the division of a plurality of initial engine revolutions by the initial odometer value. In other words, the plurality of initial engine revolutions of the present invention represents the plurality of engine revolutions of the vehicle up to that instant.
  • In reference to FIG. 1, the initial odometer value and the average revolutions per initial odometer value are then recorded by the company so that the vehicle can be prepped for a designated time period. The designated time period of the present invention is a time frame that is allocated for the vehicle by the company, wherein the time frame is either predetermined by the company or determined upon a mutual agreement between the company and an end user. For example, a three-year car lease, a five-year engine warranty, one-week car rental agreement, and a six-month insurance premium can be seen as the designated time period within the present invention. The designated time period represents the total time period that the company plans to implement the present invention, wherein the end user of the present invention becomes liable to unapproved mechanical issues of the vehicle that are identified through the present invention.
  • In reference to FIG. 1, a reset button that is linked to the odometer is pressed to initiate a secondary odometer value, an average revolutions per secondary odometer value, and a plurality of secondary engine revolutions for the present invention. Even though the reset button creates a temporally starting point for the secondary odometer value, the average revolutions per secondary odometer value, and the plurality of secondary engine revolutions within the odometer of the vehicle, the ECU separately records the total distance traveled, the ARDU value, and the plurality of engine revolutions of the vehicle. Then the vehicle is either released into the custody of the end user for the designated time period or monitored throughout the designated time period upon completion of a contract agreement. Additionally, the unapproved mechanical issues and other contract related conditions are informed to the end user during the completion of the contract agreement so that the end user is fully aware about the consequences of contract violations.
  • Once the end user returns the vehicle after the designated time period, the secondary odometer value and the average revolutions per secondary odometer value for the designated time period are recorded in order to continuously implement the present invention. More specifically, the secondary odometer value that represents the total distance traveled within the designated time period is displayed within a trip meter of the odometer as the reset button initiates the temporally starting point for the secondary odometer value. Similarly, the average revolutions per secondary odometer value and the plurality of secondary engine revolutions are also displayed within the trip meter of the vehicle as the reset button initiates the temporally starting point for average revolutions per secondary odometer value and the plurality of secondary engine revolutions. The average revolutions per secondary odometer value is calculated by the ECU through the division of the plurality of secondary engine revolutions by the secondary odometer value, wherein the total engine revolutions since the activation of the reset button represents the plurality of secondary engine revolutions.
  • In reference to FIG. 3, the secondary odometer value and the average revolutions per secondary odometer value of the vehicle are validated for the designated time period. In other words, a control panel of the vehicle is checked for a warning notification for odometer and speedometer tampering as the warning notification indicates any kind of odometer irregularities. More specifically, an outlier value for the average revolutions per secondary odometer value is stored within the ECU of the vehicle so that the ECU is able to detect abnormal behavior of the average revolutions per secondary odometer value with respect to the secondary odometer value. The outlier value is preset slightly higher than the maximum allowable ARDU valve of the engine, where the outlier value functions as a threshold value to detect any odometer and speedometer tampering of the vehicle. At any given time, if the average revolutions per secondary odometer value of the vehicle is greater than or equal to the outlier value within the designated time period, the ECU determines that the odometer of the vehicle is compromised. Then the ECU generates and sends a warning signal for odometer and speedometer tampering to the control panel. Then the warning notification of the warning signal for odometer and speedometer tampering is visually displayed on the control panel, wherein the warning notification only provides a visual notification. Once the warning notification is displayed with the control panel, the ECU records an entity for the warning notification in order to keep track of the total number of displayed warning notifications for the vehicle. For example, if the vehicle has displayed twenty warning notifications during the designated time period, the ECU records twenty different entities for each of the warning notifications.
  • In reference to FIG. 2, the ECU can also send the initial odometer value, the average revolutions per initial odometer value, and the plurality of initial engine revolutions into a remote computing device with a communication mean including, but is not limited to, an on-board diagnostic (OBD) connector, a universal serial bus (USB), a local area wireless technology, a cellular network, and a wireless technology standard for exchanging data over short distances. More specifically, the plurality of initial engine revolutions and the initial odometer value can be exported into the remote computing device so that the plurality of initial engine revolutions and the average revolutions per initial odometer value are able to graphically display on a timeline graph. As a result, the company is able to access the data regarding how the vehicle is driven by the end user of the vehicle in order to properly diagnose the condition of the engine and the driving style of the end user. The timeline graph also displays the total number of warning notification and the total number of activation for the reset button. This allows the company to visually identify any kind of unnecessary activities that may have been conducted during the designated time period. Since the total distance traveled, the ARDU value, and the plurality of engine revolutions of the vehicle respectively represent the initial odometer value, the average revolutions per initial odometer value, and the plurality of initial engine revolutions, the company is able to visually analyze the designated time period with respect to the overall timeline graph. Additionally, the company is also able to individually isolate small time periods within the designated time period to detect the outlier values. For example, the average revolutions per secondary engine revolutions of a vehicle can be less than the threshold value for the duration of the designated time period. However, the timeline graph may visually indicate small time periods where the average revolutions per secondary engine revolutions exceeds the threshold value. Then the company is able to determine the outcome of the final assessment with respect to the small time periods that exceeds the threshold value.
  • In reference to FIG. 4, the outlier value for the average revolutions per secondary odometer value may occur due to excessive acceleration that is also known as the unnecessary engine revving. Since each secondary engine revolution is timestamped with the ECU, the ECU is able to keep track of the plurality of secondary revolutions throughout the designated time period. A speedometer of the vehicle generates a vehicle speed at a given time period and connected to the ECU, where the ECU simultaneously records the vehicle speed for each timestamped secondary engine revolution if the speedometer is at an operational condition. Then the ECU is able to cross-reference the vehicle speed from the speedometer and the average revolutions per secondary odometer value to confirm the outlier value of the designated time period. As a result, the ECU is able to conclude the cause of the outlier value from the vehicle speed from the speedometer and the average revolutions per secondary odometer value.
  • In reference to FIG. 5, the outlier value for the average revolutions per secondary odometer value may occur due to excessive acceleration that is also known as the unnecessary engine revving. Since each secondary engine revolution is timestamped with the ECU, the ECU is able to keep track of the plurality of secondary revolutions throughout the designated time period. Generally, the speedometer of the vehicle generates the vehicle speed at a given time period while the ECU simultaneously records the vehicle speed for each timestamped secondary engine revolution when the speedometer is at an operational condition. Additionally, a global positioning system (GPS) device that is connected to the ECU also generates and records the vehicle speed. For example, the GPS device generates different information, including, but not limited to, the vehicle speed, spaced-based navigation coordinates, environmental conditions, and time information. However, if the speedometer is at a non-operation conditional due to any reason, the ECU retrieves the vehicle speed for the given time period from the GPS device. Then the ECU is able to cross-reference the vehicle speed from the GPS device and the average revolutions per secondary odometer value to confirm the outlier value of the designated time period. As a result, the ECU is able to conclude the cause of the outlier value from the vehicle speed from the GPS device and the average revolutions per secondary odometer value.
  • In reference to FIG. 6, the outlier value for the average revolutions per secondary odometer value may occur due to the non-operational condition of the odometer. Since each secondary engine revolution is timestamped with the ECU, the ECU is able to keep track of the plurality of secondary revolutions throughout the designated time period. Generally, the odometer of the vehicle generates the odometer value at a given time period while the ECU simultaneously records the vehicle speed for each timestamped secondary engine revolution when the speedometer is at an operational condition.
  • Additionally, the GPS device generates and records a total distance traveled by the vehicle. In other words, the total distance traveled from the GPS device is equivalent to the secondary odometer value. However, if the odometer is at a non-operation conditional due to any reason, the ECU retrieves the total distance traveled for the given time period from the GPS device. Then the ECU is able to cross-reference the distance traveled from the GPS device and the average revolutions per secondary odometer value to confirm the outlier value of the designated time period. As a result, the ECU is able to conclude the cause of the outlier value from the total distance traveled from the GPS device and the average revolutions per secondary odometer value.
  • In reference to FIG. 7, the outlier value for the average revolutions per secondary odometer value may occur due to heavy towing or pulling. Since each secondary engine revolution is timestamped with the ECU, the ECU is able to keep track of the plurality of secondary revolutions throughout the designated time period. An engine load valve sensor of the vehicle generates an engine load value of the vehicle at a given time period and connected to the ECU so that the ECU is able to record the engine load value. The ECU is then able to cross-reference the engine load value from the engine load valve sensor and the average revolutions per secondary odometer value to confirm the outlier value of the designated time period. As a result, the ECU is able to conclude the cause of the outlier value from the engine load value and the average revolutions per secondary odometer value.
  • In reference to FIG. 8, the outlier value for the average revolutions per secondary odometer value may occur due to unnecessary engine loads. Since each secondary engine revolution is timestamped with the ECU, the ECU is able to keep track of the plurality of secondary revolutions throughout the designated time period. A throttle position sensor of the vehicle generates a throttle position value of the vehicle at a given time period and connected to the ECU so that the ECU is able to record the throttle position value. The ECU is then able to cross-reference the throttle position value from the throttle position sensor and the average revolutions per secondary odometer value to confirm the outlier value of the designated time period. As a result, the ECU is able to conclude the cause of the outlier value from the throttle position value and the average revolutions per secondary odometer value.
  • In reference to FIG. 9, the outlier value for the average revolutions per secondary odometer value may occur due to different road profiles such as uphill and downhill. Since each secondary engine revolution is timestamped with the ECU, the ECU is able to keep track of the plurality of secondary revolutions throughout the designated time period. An electronic stability controller of the vehicle generates a vehicle pitch and vehicle angle at a given time period and connected to the ECU so that the ECU is able to record the vehicle pitch and the vehicle angle. Then the ECU is able to cross-reference the vehicle pitch from the electronic stability controller and the average revolutions per secondary odometer value to confirm the outlier value of the designated time period. As a result, the ECU is able to conclude the cause of the outlier value from the vehicle pitch and the average revolutions per secondary odometer value. Additionally, the ECU is also able to cross-reference the vehicle angle from the electronic stability controller and the average revolutions per secondary odometer value to confirm the outlier value of the designated time period. As a result, the ECU is able to conclude the cause of the outlier value from the vehicle angle and the average revolutions per secondary odometer value.
  • After validating the secondary odometer value and the average revolutions per secondary odometer value, the final assessment can be determined with a standard engine revolutions per distance unit as the final step of the present invention. The standard engine revolutions per distance unit provides a guideline for the average revolutions per secondary odometer value so that necessary changes can be implemented to the contract agreement. The changes that can be made to the contract agreement upon the average revolutions per secondary odometer value are pre-stated and explained to the end user before the completion of the contract agreement. Then the company is able to adjust the contact agreement upon the final assessment, wherein the responsible party that violates the contact agreement is only liable for the respective damages or the unapproved mechanical issues.
  • In reference to FIG. 10, the present invention can be implemented by the car dealership in order to properly conclude the outcome of an engine warranty, where the engine warranty becomes the contract agreement for the vehicle. More specifically, after validating the secondary odometer value and the average revolutions per secondary odometer value, a current odometer value and an average revolutions per current odometer value of the vehicle are recorded by the company. Then the initial odometer value is subtracted from the current odometer value in order to conform the secondary odometer value. The average revolutions per secondary odometer value is then compared with the standard engine revolutions per distance unit in order to determine the outcome of the engine warranty in the event of an engine failure during the break in period of the engine. For example, if the average revolutions per secondary odometer value is greater than the standard engine revolutions per distance unit, the car dealership can conclude that the engine failure during the break in period occurs due to the operating state of the vehicle and the negligent actions of the end user. As a result, the car dealership can void the engine warranty as the final assessment. However, if the average revolutions per secondary odometer value is lower than the standard engine revolutions per distance unit, the car dealership can conclude that the engine failure during the break in period occurs due to a defected engine. As a result, the car dealership accepts the engine warranty as the final assessment.
  • In reference to FIG. 11, the present invention can be implemented by the car dealership in order to properly conclude the outcome of a lease agreement, where the lease agreement becomes the contract agreement for the vehicle. More specifically, after validating the secondary odometer value and the average revolutions per secondary odometer value, a current odometer value and an average revolutions per current odometer value of the vehicle are recorded by the company. Then the initial odometer value is subtracted from the current odometer value in order to conform the secondary odometer value. The average revolutions per secondary odometer value is then compared with the standard engine revolutions per distance unit in order to determine the outcome of the lease agreement after the vehicle has been returned. For example, if the average revolutions per secondary odometer value is greater than the standard engine revolutions per distance unit, the car dealership can conclude that at least one surcharge should be added due to the operating state of the vehicle and the negligent actions of the end user. As a result, the car dealership adds the at least one surcharge to the lease agreement as the final assessment. However, if the average revolutions per secondary odometer value is lower than the standard engine revolutions per distance unit, the car dealership can conclude that at least one discount should be added due to compliance of the end user. As a result, the car dealership adds the at least one discount to the lease agreement as the final assessment.
  • In reference to FIG. 12, the present invention can be implemented by the car rental companies in order to properly conclude the outcome of a rental agreement, where the rental agreement becomes the contract agreement for the vehicle. More specifically, after validating the secondary odometer value and the average revolutions per secondary odometer value, a current odometer value and an average revolutions per current odometer value of the vehicle are recorded by the company. Then the initial odometer value is subtracted from the current odometer value in order to conform the secondary odometer value. The average revolutions per secondary odometer value is then compared with the standard engine revolutions per distance unit in order to determine the outcome of the rental agreement after the vehicle has been returned. For example, if the average revolutions per secondary odometer value is greater than the standard engine revolutions per distance unit, the car rental company may conclude that at least one surcharge should be added due to the operating state of the vehicle and the negligent actions of the end user. As a result, the car rental company adds the at least one surcharge to the rental agreement as the final assessment. However, if the average revolutions per secondary odometer value is lower than the standard engine revolutions per distance unit, the car rental company may conclude that at least one discount should be added due to compliance of the end user. As a result, the car rental company adds the at least one discount to the rental agreement as the final assessment.
  • In reference to FIG. 13, the present invention can be implemented by the insurance companies in order to properly conclude the outcome of an insurance premium policy, where the insurance policy premium becomes the contract agreement for the vehicle. More specifically, after validating the secondary odometer value and the average revolutions per secondary odometer value, a current odometer value and an average revolutions per current odometer value of the vehicle are recorded by the company. Then the initial odometer value is subtracted from the current odometer value in order to conform the secondary odometer value. The average revolutions per secondary odometer value is then compared with the standard engine revolutions per distance unit in order to determine the outcome of the insurance policy premium. For example, if the average revolutions per secondary odometer value is greater than the standard engine revolutions per distance unit, the insurance company can conclude that at least one surcharge should be added due to the operating state of the vehicle and the negligent actions of the end user. As a result, the insurance company adds the at least one surcharge to the insurance policy premium as the final assessment. However, if the average revolutions per secondary odometer value is lower than the standard engine revolutions per distance unit, the insurance company can conclude that at least one discount should be added due to compliance of the end user. As a result, the insurance company adds the at least one discount to the insurance policy premium as the final assessment.
  • Although the invention has been explained in relation to its preferred embodiment, it is to be understood that many other possible modifications and variations can be made without departing from the spirit and scope of the invention as hereinafter claimed.

Claims (20)

What is claimed is:
1. A method of monitoring a vehicle for determining driver negligence, the method comprises the step of:
(A) providing an odometer in a vehicle, wherein the odometer generating an initial odometer value to represent a total distance traveled by the vehicle;
(B) providing an engine control unit (ECU) and a global positioning system (GPS) device connected to the ECU in the vehicle, wherein the ECU generates an average revolutions per initial odometer value by repeatedly dividing a plurality of initial engine revolutions by the initial odometer value;
(C) recording the initial odometer value, the average revolutions per initial odometer value, and the plurality of initial engine revolutions in order to prepare the vehicle for a designated time period;
(D) pressing a reset button linked to the odometer in order to initiate a secondary odometer value, an average revolutions per secondary odometer value, and a plurality of secondary engine revolutions;
(E) releasing the vehicle to an end user for the designated time period upon completion of a contract agreement;
(F) recording the secondary odometer value and the average revolutions per secondary odometer value for the designated time period, wherein the plurality of secondary engine revolutions is divided by the secondary odometer value to calculate the average revolutions per secondary odometer value;
(G) validating the secondary odometer value and the average revolutions per secondary odometer value of the vehicle for the designated time period; and
(H) determining a final assessment with a standard engine revolutions per distance unit upon the validation of the secondary odometer value and the average revolutions per secondary odometer value.
2. The method of monitoring a vehicle for determining driver negligence, the method as claimed in claim 1 comprises the step of:
sending the initial odometer value, the average revolutions per initial odometer value, and the plurality of initial engine revolutions into a remote computing device with a communication mean comprising an on-board diagnostic (OBD) connector, a universal serial bus (USB), a local area wireless technology, a cellular network, or a wireless technology standard for exchanging data over short distances;
graphically displaying the plurality of initial engine revolutions and the average revolutions per initial odometer value in a timeline graph; and
graphically displaying a total number of activation for the reset button in the timeline graph.
3. The method of monitoring a vehicle for determining driver negligence, the method as claimed in claim 1 comprises the step of:
providing an outlier value for the average revolutions per secondary odometer value within the ECU, wherein the outlier value is a threshold value to detect any odometer and speedometer tampering of the vehicle;
generating and sending a warning signal for odometer and speedometer tampering with the ECU,
if the average revolutions per secondary odometer value is greater than or equal to the outlier value within the designated time period; and
visually displaying a warning notification of the warning signal for odometer and speedometer tampering with a control panel connected to the ECU in the vehicle.
4. The method of monitoring a vehicle for determining driver negligence, the method as claimed in claim 3 comprises the step of:
providing a speedometer connected to the ECU in the vehicle, wherein the speedometer generates a vehicle speed at a given time period;
timestamping each secondary engine revolution with the ECU;
simultaneously recording the vehicle speed with the ECU,
if the speedometer is at an operational condition; and
cross-referencing the vehicle speed from the ECU and the average revolutions per secondary odometer value to confirm the outlier value.
5. The method of monitoring a vehicle for determining driver negligence, the method as claimed in claim 3 comprises the step of:
providing a speedometer connected to the ECU in the vehicle, wherein the speedometer generates a vehicle speed at a given time period;
timestamping each secondary engine revolution with the ECU;
simultaneously generating and recording the vehicle speed with the GPS device;
retrieving the vehicle speed for the given time period from the GPS device,
if the speedometer is at a non-operational condition; and
cross-referencing the vehicle speed from the GPS device and the average revolutions per secondary odometer value to confirm the outlier value.
6. The method of monitoring a vehicle for determining driver negligence, the method as claimed in claim 3 comprises the step of:
timestamping each secondary engine revolution with the ECU;
simultaneously generating and recording a total distance traveled with the GPS device, wherein the total distance traveled is the secondary odometer value;
retrieving the total distance traveled for the given time period from the GPS device,
if the odometer is at a non-operational condition; and
cross-referencing the total distance traveled from the GPS device and the average revolutions per secondary odometer value to confirm the outlier value.
7. The method of monitoring a vehicle for determining driver negligence, the method as claimed in claim 3 comprises the step of:
providing an engine load valve sensor connected to the ECU in the vehicle, wherein the engine load valve sensor generates an engine load value;
timestamping each secondary engine revolution with the ECU;
simultaneously recording the engine load value with the ECU; and
cross-referencing the engine load value and the average revolutions per secondary odometer value to confirm the outlier value.
8. The method of monitoring a vehicle for determining driver negligence, the method as claimed in claim 3 comprises the step of:
providing a throttle position sensor connected to the ECU in the vehicle, wherein the throttle position sensor generates a throttle position value;
timestamping each secondary engine revolution with the ECU;
simultaneously recording the throttle position value with the ECU; and
cross-referencing the throttle position value and the average revolutions per secondary odometer value to confirm the outlier value.
9. The method of monitoring a vehicle for determining driver negligence, the method as claimed in claim 3 comprises the step of:
providing an electronic stability controller connected to the ECU in the vehicle, wherein the electronic stability controller generates a vehicle pitch and a vehicle angle;
timestamping each secondary engine revolution with the ECU;
simultaneously recording the vehicle pitch and the vehicle angle with the ECU;
cross-referencing the vehicle pitch and the average revolutions per secondary odometer value to confirm the outlier value; and
cross-referencing the vehicle angle and the average revolutions per secondary odometer value to confirm the outlier value.
10. The method of monitoring a vehicle for determining driver negligence, the method as claimed in claim 1 comprises the step of:
recording a current odometer value and an average revolutions per current odometer value of the vehicle;
subtracting the initial odometer value from the current odometer value in order to conform the secondary odometer value; and
comparing the average revolutions per secondary odometer value with the standard engine revolutions per distance unit in order to determine the outcome of an engine warranty.
11. The method as claimed in claim 10 comprises, wherein the engine warranty of the engine is voided as the final assessment, if the average revolutions per secondary odometer value is greater than the standard engine revolutions per distance unit.
12. The method as claimed in claim 10 comprises, wherein the engine warranty of the engine is accepted as the final assessment, if the average revolutions per secondary odometer value is lower than the standard engine revolutions per distance unit.
13. The method as claimed in claim 1 comprises the steps of:
recording a current odometer value and an average revolutions per current odometer value of the vehicle;
subtracting the initial odometer value from the current odometer value in order to conform the secondary odometer value; and
comparing the average revolutions per secondary odometer value with the standard engine revolutions per distance unit in order to determine the outcome of a lease agreement.
14. The method as claimed in claim 13 comprises, wherein at least one surcharge is added to the lease agreement as the final assessment, if the average revolutions per secondary odometer value is greater than the standard engine revolutions per distance unit.
15. The method as claimed in claim 13 comprises, wherein at least one discount is added to the lease agreement as the final assessment, if the average revolutions per secondary odometer value is lower than the standard engine revolutions per distance unit.
16. The method as claimed in claim 1 comprises the steps of:
recording a current odometer value and an average revolutions per current odometer value of the vehicle;
subtracting the initial odometer value from the current odometer value in order to conform the secondary odometer value; and
comparing the average revolutions per secondary odometer value with the standard engine revolutions per distance unit in order to determine the outcome of a rental agreement.
17. The method as claimed in claim 16 comprises, wherein at least one surcharge is added to the car rental agreement as the final assessment, if the average revolutions per secondary odometer value is greater than the standard engine revolutions per distance unit.
18. The method as claimed in claim 16 comprises, wherein at least one discount is added to the car rental agreement as the final assessment, if the average revolutions per secondary odometer value is lower than the standard engine revolutions per distance unit.
19. The method as claimed in claim 1 comprises the steps of:
recording a current odometer value and an average revolutions per current odometer value of the vehicle;
subtracting the initial odometer value from the current odometer value in order to conform the secondary odometer value; and
comparing the average revolutions per secondary odometer value with the standard engine revolutions per distance unit in order to determine the outcome of an insurance policy premium.
20. The method as claimed in claim 19 comprises, wherein at least one surcharge is added to the insurance policy premium as the final assessment, if the average revolutions per secondary odometer value is greater than the standard engine revolutions per distance unit.
US15/045,602 2014-07-17 2016-02-17 Motor vehicle monitoring method for determining driver negligence of an engine Active US9361607B1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/045,602 US9361607B1 (en) 2014-07-17 2016-02-17 Motor vehicle monitoring method for determining driver negligence of an engine
PCT/IB2016/052611 WO2016178194A1 (en) 2014-07-17 2016-05-06 Motor vehicle monitoring method for determining driver negligence of an engine

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US201462025915P 2014-07-17 2014-07-17
US201462025909P 2014-07-17 2014-07-17
US201462025911P 2014-07-17 2014-07-17
US201462025917P 2014-07-17 2014-07-17
US14/705,163 US9299109B2 (en) 2014-07-17 2015-05-06 Motor vehicle monitoring method for determining driver negligence of an engine
US15/045,602 US9361607B1 (en) 2014-07-17 2016-02-17 Motor vehicle monitoring method for determining driver negligence of an engine

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/705,163 Continuation-In-Part US9299109B2 (en) 2014-07-17 2015-05-06 Motor vehicle monitoring method for determining driver negligence of an engine

Publications (2)

Publication Number Publication Date
US9361607B1 US9361607B1 (en) 2016-06-07
US20160162852A1 true US20160162852A1 (en) 2016-06-09

Family

ID=55074961

Family Applications (2)

Application Number Title Priority Date Filing Date
US14/705,163 Active US9299109B2 (en) 2014-07-17 2015-05-06 Motor vehicle monitoring method for determining driver negligence of an engine
US15/045,602 Active US9361607B1 (en) 2014-07-17 2016-02-17 Motor vehicle monitoring method for determining driver negligence of an engine

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US14/705,163 Active US9299109B2 (en) 2014-07-17 2015-05-06 Motor vehicle monitoring method for determining driver negligence of an engine

Country Status (2)

Country Link
US (2) US9299109B2 (en)
WO (1) WO2016178194A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019043444A1 (en) * 2017-09-04 2019-03-07 Ebrahimian Ziba System and method for monitoring vehicle history

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017191513A1 (en) * 2015-11-17 2017-11-09 Kenneth Carl Steffen Winiecki Motor vehicle monitoring method for determining driver negligence of an engine
US10102531B2 (en) * 2016-01-13 2018-10-16 Donald Remboski Real time failure analysis and accurate warranty claim assesment
CN106682741A (en) * 2016-11-16 2017-05-17 国网山东省电力公司青岛供电公司 Equipment maintenance method and equipment maintenance device
CN109754153A (en) * 2018-11-23 2019-05-14 北京交通大学 A kind of driver violation disaster risk estimation method based on duration model

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3903736A (en) * 1966-06-30 1975-09-09 Bissett Berman Corp Service computer using electrolytic cell storage member
JPS58190766A (en) * 1982-04-20 1983-11-07 Regie Natl Usines Renault Display for tachometer of automobile
US5569848A (en) * 1995-01-06 1996-10-29 Sharp; Everett H. System, method and apparatus for monitoring tire inflation pressure in a vehicle tire and wheel assembly
NL1011501C2 (en) * 1999-03-09 2000-09-12 Wiebren De Jonge The Traffic Information & Pricing (TIP) system.
US7092803B2 (en) * 2000-08-18 2006-08-15 Idsc Holdings, Llc Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components
US7155321B2 (en) * 2001-08-06 2006-12-26 Idsc Holdings Llc System, method and computer program product for remote vehicle diagnostics, monitoring, configuring and reprogramming
US6964258B2 (en) * 2003-10-31 2005-11-15 S & S Cycle, Incorporated Engine revolution limiter
US20080288379A1 (en) * 2004-06-29 2008-11-20 Allin Patrick J Construction payment management system and method with automated electronic document generation features
US7606948B2 (en) * 2004-12-02 2009-10-20 Hitachi Global Storage Technologies Netherlands B.V. System and method for generating warranty and pricing information for data storage apparatus
US7206720B2 (en) * 2005-02-24 2007-04-17 Lapant Todd Computer-controlled auxiliary fuel tank system with multi-function monitoring system and user calibration capabilities
US7449995B1 (en) * 2005-11-14 2008-11-11 Eula Clanton-Holloway Oil change meter
US7610128B2 (en) * 2007-05-23 2009-10-27 Paccar Inc Securely calculating and storing vehicle odometer data
US8095265B2 (en) * 2008-10-06 2012-01-10 International Business Machines Corporation Recording, storing, and retrieving vehicle maintenance records
US8700255B2 (en) * 2008-10-08 2014-04-15 Trimble Navigation Limited Devices, systems, and methods for monitoring driver and vehicle behavior
US9053469B1 (en) * 2009-07-10 2015-06-09 United Services Automobile Association System and method for providing usage based vehicle insurance
US9367967B2 (en) * 2009-09-29 2016-06-14 GM Global Technology Operations LLC Systems and methods for odometer monitoring
US8423239B2 (en) * 2009-11-23 2013-04-16 Hti Ip, L.L.C. Method and system for adjusting a charge related to use of a vehicle during a period based on operational performance data
US20120150758A1 (en) * 2010-12-14 2012-06-14 Elwha LLC, a limited liability corporation of the State of Delaware Efficiency of use of a common product
JP2013036393A (en) * 2011-08-08 2013-02-21 Hitachi Constr Mach Co Ltd Engine control system of work machine
US9256842B2 (en) * 2012-06-27 2016-02-09 International Business Machines Corporation Determining fuel economy by fuel source location
US9008947B1 (en) * 2014-03-11 2015-04-14 Kenneth Carl Steffen Winiecki Method of calculating average revolutions per independent unit
US9373200B2 (en) * 2014-06-06 2016-06-21 Vivint, Inc. Monitoring vehicle usage

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019043444A1 (en) * 2017-09-04 2019-03-07 Ebrahimian Ziba System and method for monitoring vehicle history

Also Published As

Publication number Publication date
US9299109B2 (en) 2016-03-29
US20160019654A1 (en) 2016-01-21
US9361607B1 (en) 2016-06-07
WO2016178194A1 (en) 2016-11-10

Similar Documents

Publication Publication Date Title
US9361607B1 (en) Motor vehicle monitoring method for determining driver negligence of an engine
US10430800B2 (en) Faster product improvement
US11436683B1 (en) System and method for incentivizing driving characteristics by monitoring operational data and providing feedback
US10169931B2 (en) Service improvement by better incoming diagnosis data, problem specific training and technician feedback
US9361739B2 (en) Odometer monitoring and redundant storage system
EP1557780A1 (en) Monitoring system for determining and communicating a cost of insurance
US20100057479A1 (en) System and method to compute vehicle health index from aggregate data
US10417841B2 (en) Faster new feature launch
US20180114378A1 (en) Enhanced Vehicle Bad Fuel Sensor With Crowdsourcing Analytics
CN112134952B (en) Vehicle management system and method based on Internet of vehicles, electronic equipment and storage medium
US20200364800A1 (en) Systems and method for calculating liability of a driver of a vehicle
JP2020012832A (en) Method of calculating average revolutions per independent unit
US9761138B2 (en) Automatic yard move status
US20200160434A1 (en) Server apparatus and information provision method
US9678214B2 (en) Determination of GPS compliance malfunctions
JP2020086610A (en) Server device and information providing method
JP2020086613A (en) Server device and information providing method
WO2017191513A1 (en) Motor vehicle monitoring method for determining driver negligence of an engine
US10570837B2 (en) Method of calculating average revolutions per independent unit with a GPS navigation system
WO2023187851A1 (en) Vehicle data analysis method and device
CA3001286A1 (en) Method of calculating average revolutions per independent unit
CN111199452A (en) Server device and information providing method
JP2023144255A (en) Vehicle data analyzing method and apparatus

Legal Events

Date Code Title Description
STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2551); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY