US20050096809A1 - Module for monitoring vehicle operation through onboard diagnostic port - Google Patents

Module for monitoring vehicle operation through onboard diagnostic port Download PDF

Info

Publication number
US20050096809A1
US20050096809A1 US10/979,346 US97934604A US2005096809A1 US 20050096809 A1 US20050096809 A1 US 20050096809A1 US 97934604 A US97934604 A US 97934604A US 2005096809 A1 US2005096809 A1 US 2005096809A1
Authority
US
United States
Prior art keywords
onboard diagnostic
vehicle
data
memory module
diagnostic port
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.)
Abandoned
Application number
US10/979,346
Inventor
Michael Skeen
Joel Wacknov
Paul Mohr
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.)
Davis Instruments Corp
Original Assignee
Davis Instruments Corp
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 Davis Instruments Corp filed Critical Davis Instruments Corp
Priority to US10/979,346 priority Critical patent/US20050096809A1/en
Publication of US20050096809A1 publication Critical patent/US20050096809A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • 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
    • 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/12Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time in graphical form

Definitions

  • This invention relates to be on board recordation of operating data from a motor vehicle into a dedicated onboard diagnostic port memory module. More specifically, a “trip oriented” data recordation protocol is actuated during vehicle operation when the dedicated onboard diagnostic port memory module is connected to the onboard diagnostic port of the vehicle.
  • the dedicated onboard diagnostic port memory module can be preprogrammed before placement to the vehicle as to certain critical data parameters to be monitored, placed in vehicle for monitoring over an extended period of time, and finally intelligently interrogated to discharge the recorded data. A detailed record of vehicle and driver operation of a vehicle can be generated from the recorded data.
  • Onboard Diagnostic Port II So-called Onboard Diagnostic Ports are known and indeed required by The Environmental Protection Agency (EPA).
  • the current device is known as Onboard Diagnostic Port II (hereinafter OBD II).
  • OBD II Onboard Diagnostic Port II
  • the device is required to enable certain data to be sensed when the OBD II is monitored, and that data is specified by The Society of Automotive Engineers Vehicle Electrical Engineering Systems Diagnostic Standards Committee.
  • SAE J1962 The physical configuration of the OBD II output plug is specified (SAE J1962), containing a pin array which is to be electronically monitored. What is not mandated is the language of data transmission, and which pins are to emit the data.
  • SAE J1962 The OBD II mandated data to be sensed is contained in a voluminous catalog.
  • the OBD II ports are designed to be connected with standard diagnostic equipment in modern automobile repair shops. It is known to have diagnostic equipment which upon being plugged into the OBD II port, determines the “language” of a particular port, properly addresses the pin array, and finally receives and interprets for the mechanic the specified data required of the OBD II port. It is known that manufacturers have proprietary codes for correspondingly proprietary operating parameters and parts of specific vehicles. Further, it is common to load into standard diagnostic equipment the labels specified by the Diagnostic Standards Committee. When the standard diagnostic equipment detects the data required of the OBD II port, the standard diagnostic equipment gives that particular data a display label which corresponds to the data mandated by the Diagnostic Standards Committee.
  • OBD II ports are, in some circumstances, monitored by having a computer (for example a laptop or notebook computer) attached to the ports while the vehicle is operating.
  • a computer for example a laptop or notebook computer
  • a mechanic makes the computer connection, and thereafter drives or runs the vehicle to collect the desired data. Either during operation or once the data is collected, the computer displays the collected data in a programmed format.
  • malfunction indicator lamps are generally uninformative.
  • a typical display of such a malfunction indicator lamps is “Check Engine.”
  • many of these lights are programmed so that they can be turned off only by a dealer. Often the lights are triggered by events that cannot be subsequently determined by the dealer when the light is reset. In short, these lights can be and often are a source of irritation. Even more important, sometimes the lights are activated by very routine automotive conditions, such as a dirty air filter. When such conditions occur, the driver must go to the dealer and pay a “diagnostic fee,” have the dealer correct the conditions (for example replace the dirty air filter), and finally retrieve the vehicle from the dealer. A simplification in the operation of such malfunction indicator lamps would be ideal.
  • An onboard diagnostic memory module is configured to plug into the OBD II port and has a real-time clock and power supply, a microprocessor powered from the OBD II port, microprocessor operating firmware, and an attached memory (currently 4 MB).
  • the onboard diagnostic memory module is preprogrammed with data collection parameters through microprocessor firmware by connection to a PC having programming software for the module firmware. Thereafter, the onboard diagnostic memory module is moved into pin connection with the OBD II port of a vehicle. Data is recorded on a “trip” basis, preferably using starting of the engine to define the beginning of the trip and stopping of the engine to define the end of the trip. EPA-mandated operating parameters are monitored, including vehicle speed.
  • the onboard diagnostic memory module When loaded with a typical data set from connection to a vehicle, which can be up to 300 hours of trip operation (about one month of average vehicle operation), the onboard diagnostic memory module is unplugged from the vehicle and plugged into the RS 232 port of a PC. Alternatively, the vehicle installed onboard diagnostic memory module can be intelligently interrogated in a permanent position of installation in a vehicle.
  • the intelligent interrogation occurs by interpretive software from an interrogating PC or palm sized personal digital assistant (PDA) to retrieve a trip-based and organized data set including hard and extreme acceleration and deceleration, velocity (in discrete bands), distance traveled, as well as the required EPA-mandated operating parameters.
  • Telltale printouts can be generated highlighting operator habits (such as hard and extreme deceleration indicating that the driver is following too close), as well as the critical vehicle operating parameters.
  • An extraordinary event log is maintained of densely recorded data based on (probable) accident parameters.
  • Programming of the module can include resetting the malfunction indicator lamps of the vehicle. Installation of the module plugged to the OBD II port does not require vehicle modification.
  • the device is ideal for monitoring driver habits.
  • the generated plots of vehicle speed bands with respect to time with overlying hard and extreme acceleration and deceleration parameters generates a unique telltale of driver habit including the “following too close.”
  • the module is capable of operating on a driver-assigned basis. For example, the driver can be required to connect the module to any vehicle he operates with the module faithfully recording the cumulative operating parameters of the particular vehicle(s), despite language changes at the OBD II ports.
  • the device can be used to greatly facilitate repair. For example, where a vehicle owner complains of intermittent vehicle behavior, such as a vehicle stalling due to a sticking valve, the module can be plugged into the vehicle for a specific period of time while the vehicle undergoes normal operation by the operator. At the end of a preselected period of time, the module can be returned to a diagnosing PC, the problem determined, and the repair made. In determining the problem, the memory of the operator can be used to pinpoint the particular trip and the probable time of the intermittent malfunction. The mechanic can be directed to the particular data set containing the vehicle operating parameters to diagnose and repair the intermittent vehicle behavior.
  • the repair simplifications are manifold. For example, trip data sets can be correlated with the memory of the driver. The driver can then supplement the recorded information with his memory to fully reproduce the exact conditions under which a malfunction occurred. Further, where simple malfunction conditions exist, such as dirty air filters, they may be immediately identified and repaired by facilities having less than full vehicle repair capability. A dirty air filter may be replaced at the local gas station. Where a malfunction indicator light such as “Check Engine” is triggered by the dirty air filter, the vehicle operator can reset the malfunction indicator light using the programmed module.
  • a malfunction indicator light such as “Check Engine”
  • Both the vehicle operator and the vehicle owner can benefit from the device.
  • the combination of the trip-oriented data recordation (including time and trip mileage) with owner- and employee-generated information provides an uncontrovertable record of employee and vehicle operation.
  • the module can provide important corroboration to vehicle operating parameters which might otherwise be contested questions of fact related to the accident.
  • the PC can be interactive with the onboard diagnostic memory module. For example, if the operating firmware in the onboard diagnostic memory module contains a bug, correction can occur.
  • the PC can download a discrete program operable on a PC connected to the onboard diagnostic memory module.
  • the program When the program is downloaded to the PC, it then runs to replace the firmware data set in the onboard diagnostic memory module to either remedy the malfunction or install and upgrade. Further, where enhanced operation of the onboard diagnostic port memory module is required for new vehicles, Internet firmware replacement can rapidly provide the required enhanced operation.
  • the organization of the collected data into “trip”-oriented data sets is particularly useful.
  • the particularly useful organization of vehicle speed, acceleration and deceleration, and operating parameters can be collected.
  • This organization is extraordinarily useful, whether or not the module is removable from the vehicle. For example, provision may be made to download a permanently installed module using the infrared communication feature built into most hand held personal digital assistants (PDAs).
  • PDAs personal digital assistants
  • FIG. 1 is a picture of the driver console of an automobile showing an expanded view of the OBD II port, which port is typically under the dashboard near the steering column;
  • FIG. 2 is an illustration of the onboard diagnostic port being connected to a standard PC
  • FIG. 3A and 3B illustrate respectively the onboard diagnostic port memory module being connected to the onboard diagnostic port of an automobile and the connected onboard diagnostic port memory module with an illustrated firmware operated indicator lamp displayed from the module;
  • FIG. 4 is a schematic of the onboard diagnostic port memory module indicating the backup battery, clock, the memory, signal conditioner for reading the vehicle onboard diagnostic port, and finally the RS 232 driver for connection to a PC serial port;
  • FIGS. 5A-5E are wiring schematics of the onboard diagnostic port memory module used with this invention with:
  • FIG. 5A illustrating the microcontroller section
  • FIG. 5B illustrating the physical interface to the vehicle for the PWM and VPW protocols
  • FIG. 5C illustrating the physical interface to the vehicle for the ISO mode
  • FIG. 5D illustrating the optional IrDA interface allowing the module to communicate with a personal digital assistant (PDA);
  • FIG. 5E illustrating the actual connection to the vehicle
  • FIG. 6 is a firmware logic diagram of the firmware within the onboard diagnostic port memory module for recordation of data during vehicle operation
  • FIG. 7 is a software logic diagram between the onboard diagnostic port memory module and a connected PC for both furnishing the module with settings and downloading data for analysis;
  • FIGS. 8A through 8H are representative plots and tables of the recorded data where:
  • FIG. 8A is a plot of speed against elapsed time indicating normal or conservative driving
  • FIG. 8B is a plot of speed against elapsed time indicating abnormal, risk incurring driving with hard and extreme braking and accelerating;
  • FIG. 8C is a tabular presentation all of time, speed, engine speed, coolant temperature, engine load, and battery voltage useful in diagnosing engine operation;
  • FIG. 8D is a tabular presentation of elapsed time vs. speed from which acceleration and deceleration as well as distance traveled can be determined;
  • FIG. 8E is a graphical plot of coolant temperature vs. elapsed time for diagnosing engine temperature and thermostat operation
  • FIG. 8F is a tabular plot of elapsed time, speed, engine speed, engine load, and coolant temperature
  • FIG. 8G is a graphical plot of data triggering operation of an accident log wherein operating parameters are stored in a first in, last out stack for preserving data indicating a possible accident and,
  • FIG. 8H is a tabular presentation of the data triggering operation of the accident log.
  • An onboard diagnostic port 1 is typically configured under the dashboard adjacent to the steering column.
  • aofn onboard diagnostic port memory module 10 has a 8 pin connector port 11 with a 9 pin connector 12 and power supply 13 for connection to the serial port of a PC 14 .
  • data can be conventionally printed, transmitted to the Internet, or otherwise processed.
  • this invention also contemplates reading of data using IrDA ports.
  • the onboard diagnostic port memory module 10 of this invention is illustrated as being plugged into OBD II port 1 .
  • a firmware operated indicator light 2 can be used for indicating any number of selected functions including the presence of communication between the module 10 and the OBD II port.
  • FIG. 4 a schematic of onboard diagnostic port memory module 10 is illustrated.
  • Three-volt battery 11 operates real-time clock 12 for the purpose of time stamping data.
  • the time signal is given to CPU 13 .
  • signal conditioner 17 recognizes the particular language emitted by the vehicle and configures module 10 to receive data in the SAE J1850 (GM, Ford), ISO, ISO 9141 (Chrysler and most foreign cars) and KWP 2000 (many 2001 and later foreign cars) formats. Data is then channeled directly to memory 15 .
  • SAE J1850 GM, Ford
  • ISO ISO 9141
  • KWP 2000 many 2001 and later foreign cars
  • programming and downloading of onboard diagnostic port memory module 10 occurs through PC serial port 20 connection and RS 232 driver 16 .
  • firmware within CPU 13 has parameters set for data recordation.
  • inquiry is made through the RS 232 driver for CPU 13 to download memory 15 .
  • circuitry for use with this device can be understood with respect to FIGS. 5A through 5E .
  • FIG. 5A the Microcontroller Section shown in FIG. 5A
  • the PWM/VPW Physical Layer shown in FIG. 5B the PWM/VPW Physical Layer shown in FIG. 5B
  • FIG. 5C the ISO Physical Layer shown in FIG. 5C
  • the Optional IrDA Interface shown in FIG. 5D the J1962 Interface shown in FIG. 5E .
  • the onboard diagnostic memory module design contains two printed circuit boards (PCBs), which are stacked on top of each other and connected via a single connector.
  • the “top” board contains sections in FIGS. 5A , B, C, and D above, and the “bottom” board contains section in FIG. 5E .
  • the “basic” version runs on 5.0V and has a smaller serial flash memory while the advanced version runs on 3.3V and has a larger serial flash memory. Please refer to the schematics for each of the versions.
  • the microcontroller section forms the heart of the design.
  • U 8 is an ATMEL ATmega 16L microcontroller, with on board flash memory, SPI communications bus, and a UART.
  • the microcontroller is supplied with an 8 MHz clock by crystal X 2 .
  • the microcontroller is powered from 5.0V in the “basic” version of the product, and 3.3V in the “advanced” version.
  • U 2 is an ATMEL serial flash memory chip where the trip log data is stored.
  • the basic version of the onboard diagnostic memory module uses an AT45D011 1 mega-bit memory, while the advanced version uses an AT45DB041B 4 mega-bit part.
  • the serial flash memory is powered from 5.0V in the basic version and 3.3V in the advanced version.
  • U 5 is a Real Time Clock (RTC), which provides a non-volatile time source for the product.
  • RTC Real Time Clock
  • the RTC When no power is applied to the onboard diagnostic memory module, the RTC is powered from 3V battery BT 1 (see J1962 Interface Section). When the onboard diagnostic memory module is powered, power to the RTC is supplied from either 5.0V (basic) or 3.3V (advanced).
  • the clock communicates to the microcontroller (U 8 ) via a two-wire communications bus.
  • U 4 is a RS232 level shifter to provide communications with a PC.
  • U 4 has an integral charge pump to generate the proper voltage levels and operates from either 5.0V (basic) or 3.3V (advanced).
  • JP 1 is a connector that provides the link to the PC when the onboard diagnostic memory module 10 is not plugged into the vehicle.
  • diode D 2 isolates the external power source from the vehicle power source if they are connected at the same time.
  • the pin assignments are as follows: PIN SIGNAL 1 External Power (7 to 15 V) 2 RS232 Output (TXD) 3 RS232 Input (RXD) 4 SPI (MOSI) 5 SPI (MISO) 6 SPI (SCK) 7 Microcontroller Reset 8 Ground
  • the PWM/VPW Physical Layer (see FIG. 5B ) provides the physical interface to the vehicle for the PWM and VPW protocols. Common parts are shared between the implementation of the two protocols in order to minimize cost and complexity.
  • U 6 A is an Operational Amplifier (Op Amp), which drives the J1850 Plus line for both the PWM and VPW modes. It is configured as a non-inverting amplifier with a gain of four (4) and the input on pin 3 .
  • Q 1 is a NPN transistor and is used to provide a high current drive source.
  • the components R 6 , R 8 , C 16 , and R 16 create a wave shaping network that drive the input of U 6 A (for the values of these components see the BOM for the basic and advanced models).
  • the input of this network is the output of microcontroller U 8 pin 14 , PWM/VPW TXD. In the basic mode, this voltage is 5.0V when high and in the advanced model it is 3.3V when high.
  • the output of the network i.e. the input to U 6 pin 3
  • Q 2 is a NPN transistor that forms the drive for the J1850 Minus line.
  • PWM mode Q 2 is actively driven on and off in complement to Q 1 thus creating a differential signal between the J1850 Plus and J1850 Minus lines.
  • VPW mode Q 2 is forced off, leaving the J1850 Minus line disconnected.
  • R 7 and R 14 form a bias network for PWM mode. If undriven or disconnected from the vehicle, the J1850 Plus line will be pulled low and the J1850 Minus line will be pulled high (5.0V).
  • R 15 , C 17 , and Q 3 create a termination circuit for VPW mode.
  • Q 3 is turned on thus enabling the termination.
  • PWM mode Q 3 is left off.
  • U 6 B and associated circuitry form a differential receiver for PWM mode.
  • R 18 provides approximately 10% hysteresis for noise immunity.
  • Q 4 provides a level shifter and inverter for the output signal that goes to the microcontroller U 8 pin 16 (PWM/VPW RXD).
  • U 6 C and associated circuitry form a receiver for VPW mode.
  • the reference value of 3.75V is used to compare against the VPW signal (which is nominally between 8V and 0V).
  • R 23 provides about 10% hysteresis for noise immunity, and Q 5 creates a level shifter and inverter for the output signal, which is logically “OR'ed” with the signal from Q 4 via an open collector configuration.
  • Q 5 In PWM mode, Q 5 is disabled (MODE 3 forced low) and the signal to the microcontroller is derived from Q 4 .
  • Q 4 In VPW mode, Q 4 is disabled (MODE 2 forced low) and the signal to the microcontroller is derived from Q 5 .
  • the ISO Physical Layer (see FIG. 5C ) provides the physical interface to the vehicle for the ISO mode.
  • Transistor Q 6 forms the drive for the ISO L line and Q 7 forms the drive for the ISO K line.
  • U 6 D and associated circuitry form a receiver for ISO mode.
  • the reference value of approximately 6.0V is used to compare against the ISO K signal (which is nominally between 12V and 0V).
  • R 36 provides about 10% hysteresis for noise immunity, and Q 8 creates a level shifter and inverter for the output signal, which is connected to the microcontroller U 8 pin 24 .
  • JP 2 is a socket (row of plated through holes), which provides the connection to the bottom board.
  • the pin assignments are as follows: PIN SIGNAL 1 5.0 V Logic Supply 2 12 V (vehicle battery voltage) 3 ISO K 4 ISO L 5 J1850 Plus 6 J1850 Minus 7 RTC backup battery BT1 8 Ground 9 Battery voltage analog input 10 3.3 V Logic Supply
  • the Optional IrDA Interface allows the onboard diagnostic memory module to communicate with a Personal Digital Assistant (PDA) using the wireless IrDA industry standard.
  • PDA Personal Digital Assistant
  • U 10 is an “ENDEC” (Encoder/Decoder) chip that converts the serial data from the microcontroller U 8 into a pulse train suitable for IrDA communication.
  • U 10 is supplied with a clock source equal to 16 times the serial baud rate from U 8 pin 16 , XCLK.
  • U 11 is an IrDA transceiver that interfaces directly to the IR transmitter (LED D 5 ) and the IR receiver (PIN diode D 6 ).
  • both U 10 and U 11 are supplied from 3.3V in the advanced model, and 5.0V in the basic model.
  • the J1962 Interface (see FIG. 5E ) is the actual connection to the vehicle and is located entirely on the bottom board.
  • P 1 is the OBDII connector that interfaces with the vehicle: PIN SIGNAL 1 NC 2 J1850 Plus 3 NC 4 NC 5 Ground 6 NC 7 ISO K 8 NC 9 NC 10 J1850 Minus 11 NC 12 NC 13 NC 14 NC 15 ISO L 16 Vehicle Power
  • Diode D 3 is used to isolate the vehicle power source from the external power source (if connected).
  • D 4 is a Transient Voltage Suppressor (TVS) that is used to prevent voltage surges on the vehicle battery bus from damaging the onboard diagnostic memory module.
  • TVS Transient Voltage Suppressor
  • BT 1 is a primary (non rechargeable) 3V battery cell that is used as the backup power for the RTC U 5 .
  • U 1 is a 5V regulator used to power the onboard diagnostic memory module circuitry.
  • C 38 is a 0.1F “supercap” that is used to provide adequate hold up time when the onboard diagnostic memory module is unplugged from the vehicle. This is required so that the microcontroller has enough time to program the flash memory and perform an orderly shutdown before power is lost.
  • U 13 is a 3.3V regulator that is only used in the advanced model. If the unit is a basic mode, R 45 is installed instead of U 13 .
  • JP 3 is the connector the top board that provides the following signals: PIN SIGNAL 1 5.0 V Logic Supply 2 12 V (vehicle battery voltage) 3 ISO K 4 ISO L 5 J1850 Plus 6 J1850 Minus 7 RTC backup battery BT1 8 Ground 9 Battery voltage analog input 10 3.3 V Logic Supply
  • firmware logic diagram is illustrated.
  • the reader will understand that the firmware can be upgraded from time to time by the expedient of having PC 14 Internet connected, downloading a program having a new firmware configuration from a web site, running the program in the PC to replacing the firmware in the unit.
  • This type of protocol is preferred as inconsistencies in direct transfer of such a program from the web could interfere with the operation of the onboard diagnostic memory module.
  • the outlined firmware is preferred.
  • the onboard diagnostic port memory module is connected to the OBD II port of the host vehicle and detection of the connection made at 311 .
  • Sequentially, each protocol GM [VPW], Ford [PWM], ISO, and Advanced ISO [KWP] is tried at 312 from the onboard diagnostic port memory module to the automobile through the OBD II port 1 .
  • both the pin array and the parameters necessary for reading data passing through the pin array are selected. Data is capable of being read and retained.
  • onboard diagnostic port memory module 10 must determine the starting of the vehicle. In the protocol used here, where the engine has RPMs above 400, it is presumed that the vehicle is operating. Unfortunately, with at least some vehicles where constant interrogation is made for determining engine revolutions, battery failure can occur. Such battery failure results from the automobile computer being awakened, interrogating the engine for revolutions, and thereafter returning to the standby state. To avoid this effect, vehicle voltage is monitored. Where a starter motor is utilized, vehicle voltage change occurs. Only when vehicle voltage has changed by a predetermined amount, for example down two volts, is interrogation made of engine RPMs. The RPMs are chosen to be greater than those imposed by the starter motor but less than idling speed. Thus, vehicle voltage is detected at 314 and where voltage detection occurs, RPMs are measured at 315 . This causes the storage of trip start data at 316 .
  • monitoring of vehicle speed occurs on a once-a-second basis at speed monitors 320 . Thereafter, using previously recorded speeds, acceleration and deceleration is computed at 322 . This data is temporarily stored at 324 . Normal speed is recorded at 5-second intervals. Therefore, counter 325 asks each fifth speed count to be stored. Further, speed counts one through four are discarded during normal module operation at 326 .
  • a probable accident log can be maintained. Specifically, and where deceleration has a threshold greater than certain preset limits, and the vehicle speed goes to zero, a log of these unusual events can be maintained. All vehicle events occurring within the previous 20 seconds are remembered in a stack. Data stored in this stack can be subsequently accessed.
  • engine speed is monitored at 327 to determine whether RPMs are above a certain preset limit, here shown as 400 RPMs. This speed is faster than that speed generated by the starter motor but less than the normal speed of the engine when it is idling. If engine speed in the preset amount (over 400 RPMs) is detected, the recordation cycle continues. If the speed is not detected, it is presumed that the trip is ended and the end-of-trip data is stored at 328 .
  • 400 RPMs a certain preset limit
  • the onboard diagnostic port memory module is schematically illustrated having data 410 and settings 411 .
  • a communication port 420 is shown communicating between onboard diagnostic module 10 and personal computer 14 .
  • serial port identification 422 is determined. Thereafter, three discrete functions can be actuated with in onboard diagnostic module 10 .
  • the onboard diagnostic module memory can be cleared at 425 .
  • the onboard diagnostic module memory can be downloaded at 426 .
  • This can include data viewing 427 of the trip log 428 , activity log 429 , the accident log 430 , and the vehicle trouble log 431 .
  • onboard diagnostic memory module 10 could be assigned to a particular driver, and that driver could have a choice of vehicles to operate. Each time the driver plugged onboard diagnostic memory module 10 into a vehicle to be operated, vehicle identity would be recorded at 440 along with the driver's identification.
  • the onboard diagnostic port memory module can be configured at 450 .
  • Such configuration can include speed bands 451 , deceleration or brake bands 452 , acceleration bands 453 , operational parameters 454 , and finally the required time stamping clock setting at 455 .
  • a plot of a car trip is presented. Elapsed time of the trip is plotted against vehicle speed.
  • deceleration or brake bands 452 and acceleration bands 453 can be chosen to be 0.28 gravity fields for hard braking and 0.48 gravity fields for extreme braking.
  • Speed bands can likewise be selected. A typical selection could include 75 miles per hour and above [band I], 60 to 75 miles per hour [band II], 45 to 60 miles per hour [band III], and 0 to 45 miles per hour [band IV]. As can be seen in FIGS. 8A and 8B , such information can be graphically presented.
  • FIGS. 8B The particular utility of superimposing hard and extreme braking on the display data is apparent with respect to FIGS. 8B .
  • the data represented is commonly associated with the driving habit known as “following too close.”
  • numerous braking incidents are recorded in the hard and extreme categories.
  • the drive is indicating abuse of the vehicle with rapid accelerations.
  • FIG. 8C a data plot is shown listing elapsed time relative to speed, engine speed, cooling temperature, engine load, and battery voltage.
  • FIG. 8D a plot of elapsed time vs. speed in miles per hour is illustrated.
  • speed traveled is frequently recorded. From the frequent recordings, accelerations and decelerations as well as distance traveled are computed, the former by differentiation and the latter by integration. Once this data is accumulated, intermediate velocity points can be discarded with the remaining velocity points being maintained in a table such as fat shown in FIG. 8D .
  • FIG. 8E a plot of cooling temperature vs. time for a trip is illustrated. In this plot, possible malfunction of an automobile thermostat is illustrated.
  • FIG. 8F a tabular plot of elapsed time, speed, engine speed, engine load, and cooling temperature is shown. It should be understood that through conventional manipulation of PC software, arrays of data can be presented in any desired format.

Abstract

An onboard diagnostic memory module is configured to plug into the OBD II port and has a real-time clock and power supply, a microprocessor powered from a standard OBD II port, microprocessor operating firmware, and an attached memory (7 MB). In operation, the onboard diagnostic memory module is preprogrammed with data collection parameters through microprocessor firmware by connection to a PC having programming software for the module firmware. Thereafter, the onboard diagnostic memory module is moved into pin connection with the OBD II port of a vehicle. Data is recorded on a “trip” basis, preferably using starting of the engine to define the beginning of the trip and stopping of the engine to define the end of the trip. Intelligent interrogation occurs by interpretive software from an interrogating PC to retrieve a trip-based and organized data set including hard and extreme acceleration and deceleration, velocity (in discrete bands), distance traveled, as well as the required SAE-mandated operating parameters.

Description

    CROSS-REFERENCES TO RELATED APPLICATIONS
  • NOT APPLICABLE
  • STATEMENT AS TO RIGHTS TO INVENTIONS MADE UNDER FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
  • NOT APPLICABLE
  • REFERENCE TO A “SEQUENCE LISTING,” A TABLE, OR A COMPUTER PROGRAM LISTING APPENDIX SUBMITTED ON A COMPACT DISK.
  • NOT APPLICABLE
  • This invention relates to be on board recordation of operating data from a motor vehicle into a dedicated onboard diagnostic port memory module. More specifically, a “trip oriented” data recordation protocol is actuated during vehicle operation when the dedicated onboard diagnostic port memory module is connected to the onboard diagnostic port of the vehicle. The dedicated onboard diagnostic port memory module can be preprogrammed before placement to the vehicle as to certain critical data parameters to be monitored, placed in vehicle for monitoring over an extended period of time, and finally intelligently interrogated to discharge the recorded data. A detailed record of vehicle and driver operation of a vehicle can be generated from the recorded data.
  • BACKGROUND OF THE INVENTION
  • Davis Instruments of Hayward, Calif. has pioneered the onboard recordation of data through a module known as “Drive Right.” This device requires custom installation on a vehicle by a skilled mechanic, including a device for monitoring driveshaft rotation and the like. Recordation of data includes counters indicating vehicle operation within certain speed bands and acceleration and deceleration parameters. Purchase and operation of the device requires a motivated buyer willing to pay the cost of the unit as well as to accept the inconvenience and additional expense of vehicle installation. This device finds its highest applicability with owners of “fleets” of automobiles.
  • So-called Onboard Diagnostic Ports are known and indeed required by The Environmental Protection Agency (EPA). The current device is known as Onboard Diagnostic Port II (hereinafter OBD II). The device is required to enable certain data to be sensed when the OBD II is monitored, and that data is specified by The Society of Automotive Engineers Vehicle Electrical Engineering Systems Diagnostic Standards Committee. The physical configuration of the OBD II output plug is specified (SAE J1962), containing a pin array which is to be electronically monitored. What is not mandated is the language of data transmission, and which pins are to emit the data. The OBD II mandated data to be sensed is contained in a voluminous catalog.
  • Surprisingly, there are four discrete “languages” (and corresponding pin arrays) now extant in which these OBD II ports now emit data. Those languages are SAE J1850 (GM, Ford), ISO, ISO 9141 (Chrysler and most foreign cars) and KWP 2000 (many 2001 and later foreign cars). For each of the so-called languages, the standard OBD II port has different pins emitting different information in different formats.
  • The OBD II ports are designed to be connected with standard diagnostic equipment in modern automobile repair shops. It is known to have diagnostic equipment which upon being plugged into the OBD II port, determines the “language” of a particular port, properly addresses the pin array, and finally receives and interprets for the mechanic the specified data required of the OBD II port. It is known that manufacturers have proprietary codes for correspondingly proprietary operating parameters and parts of specific vehicles. Further, it is common to load into standard diagnostic equipment the labels specified by the Diagnostic Standards Committee. When the standard diagnostic equipment detects the data required of the OBD II port, the standard diagnostic equipment gives that particular data a display label which corresponds to the data mandated by the Diagnostic Standards Committee.
  • OBD II ports are, in some circumstances, monitored by having a computer (for example a laptop or notebook computer) attached to the ports while the vehicle is operating. Typically, a mechanic makes the computer connection, and thereafter drives or runs the vehicle to collect the desired data. Either during operation or once the data is collected, the computer displays the collected data in a programmed format.
  • As any driver of a modern vehicle can attest, such vehicles have warning systems including malfunction indicator lamps. In the usual case the malfunction indicator lamps are generally uninformative. For example, a typical display of such a malfunction indicator lamps is “Check Engine.” Unfortunately, many of these lights are programmed so that they can be turned off only by a dealer. Often the lights are triggered by events that cannot be subsequently determined by the dealer when the light is reset. In short, these lights can be and often are a source of irritation. Even more important, sometimes the lights are activated by very routine automotive conditions, such as a dirty air filter. When such conditions occur, the driver must go to the dealer and pay a “diagnostic fee,” have the dealer correct the conditions (for example replace the dirty air filter), and finally retrieve the vehicle from the dealer. A simplification in the operation of such malfunction indicator lamps would be ideal.
  • The above enumeration of the background and the related problems to the background is specific to the invention disclosed. The reader will recognize that frequently invention can include recognition of the problem(s) to be solved. The background set forth above was selected after the preferred embodiment of this invention was developed.
  • BRIEF SUMMARY OF THE INVENTION
  • An onboard diagnostic memory module is configured to plug into the OBD II port and has a real-time clock and power supply, a microprocessor powered from the OBD II port, microprocessor operating firmware, and an attached memory (currently 4 MB). In operation, the onboard diagnostic memory module is preprogrammed with data collection parameters through microprocessor firmware by connection to a PC having programming software for the module firmware. Thereafter, the onboard diagnostic memory module is moved into pin connection with the OBD II port of a vehicle. Data is recorded on a “trip” basis, preferably using starting of the engine to define the beginning of the trip and stopping of the engine to define the end of the trip. EPA-mandated operating parameters are monitored, including vehicle speed. From the monitored vehicle speed, hard and extreme acceleration and deceleration parameters, as well as distance traveled, is determined and logged on a trip basis. When loaded with a typical data set from connection to a vehicle, which can be up to 300 hours of trip operation (about one month of average vehicle operation), the onboard diagnostic memory module is unplugged from the vehicle and plugged into the RS 232 port of a PC. Alternatively, the vehicle installed onboard diagnostic memory module can be intelligently interrogated in a permanent position of installation in a vehicle. The intelligent interrogation occurs by interpretive software from an interrogating PC or palm sized personal digital assistant (PDA) to retrieve a trip-based and organized data set including hard and extreme acceleration and deceleration, velocity (in discrete bands), distance traveled, as well as the required EPA-mandated operating parameters. Telltale printouts can be generated highlighting operator habits (such as hard and extreme deceleration indicating that the driver is following too close), as well as the critical vehicle operating parameters. An extraordinary event log is maintained of densely recorded data based on (probable) accident parameters. Programming of the module can include resetting the malfunction indicator lamps of the vehicle. Installation of the module plugged to the OBD II port does not require vehicle modification.
  • The device is ideal for monitoring driver habits. The generated plots of vehicle speed bands with respect to time with overlying hard and extreme acceleration and deceleration parameters generates a unique telltale of driver habit including the “following too close.” Further, the module is capable of operating on a driver-assigned basis. For example, the driver can be required to connect the module to any vehicle he operates with the module faithfully recording the cumulative operating parameters of the particular vehicle(s), despite language changes at the OBD II ports.
  • Further, the device can be used to greatly facilitate repair. For example, where a vehicle owner complains of intermittent vehicle behavior, such as a vehicle stalling due to a sticking valve, the module can be plugged into the vehicle for a specific period of time while the vehicle undergoes normal operation by the operator. At the end of a preselected period of time, the module can be returned to a diagnosing PC, the problem determined, and the repair made. In determining the problem, the memory of the operator can be used to pinpoint the particular trip and the probable time of the intermittent malfunction. The mechanic can be directed to the particular data set containing the vehicle operating parameters to diagnose and repair the intermittent vehicle behavior.
  • The repair simplifications are manifold. For example, trip data sets can be correlated with the memory of the driver. The driver can then supplement the recorded information with his memory to fully reproduce the exact conditions under which a malfunction occurred. Further, where simple malfunction conditions exist, such as dirty air filters, they may be immediately identified and repaired by facilities having less than full vehicle repair capability. A dirty air filter may be replaced at the local gas station. Where a malfunction indicator light such as “Check Engine” is triggered by the dirty air filter, the vehicle operator can reset the malfunction indicator light using the programmed module.
  • Even more complicated repair scenarios are simplified. For example, when the operating data is downloaded to a PC, data coincident with a complicated malfunction can be isolated, and thereafter transmitted over the Internet to a diagnostic program specific to the vehicle involved. Thereafter, what is ordinarily a complicated diagnosis of vehicle malfunction can be rapidly reported to the mechanic or even to the vehicle operator. For example, for vehicles having custom parts with the OBD II port emitting custom codes, the codes can be sent over the Internet for diagnosis of the particular custom malfunction occurring.
  • Both the vehicle operator and the vehicle owner can benefit from the device. For example, where a company-owned vehicle is used by an operating employee required to submit expense reports, the combination of the trip-oriented data recordation (including time and trip mileage) with owner- and employee-generated information provides an uncontrovertable record of employee and vehicle operation. Further, where an accident occurs, the module can provide important corroboration to vehicle operating parameters which might otherwise be contested questions of fact related to the accident.
  • The PC can be interactive with the onboard diagnostic memory module. For example, if the operating firmware in the onboard diagnostic memory module contains a bug, correction can occur. Upon connection to the Internet, the PC can download a discrete program operable on a PC connected to the onboard diagnostic memory module. When the program is downloaded to the PC, it then runs to replace the firmware data set in the onboard diagnostic memory module to either remedy the malfunction or install and upgrade. Further, where enhanced operation of the onboard diagnostic port memory module is required for new vehicles, Internet firmware replacement can rapidly provide the required enhanced operation.
  • The organization of the collected data into “trip”-oriented data sets is particularly useful. In utilizing the system clock to time and date stamp the collected data with respect to a trip, the particularly useful organization of vehicle speed, acceleration and deceleration, and operating parameters can be collected. This organization, is extraordinarily useful, whether or not the module is removable from the vehicle. For example, provision may be made to download a permanently installed module using the infrared communication feature built into most hand held personal digital assistants (PDAs).
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a picture of the driver console of an automobile showing an expanded view of the OBD II port, which port is typically under the dashboard near the steering column;
  • FIG. 2 is an illustration of the onboard diagnostic port being connected to a standard PC;
  • FIG. 3A and 3B illustrate respectively the onboard diagnostic port memory module being connected to the onboard diagnostic port of an automobile and the connected onboard diagnostic port memory module with an illustrated firmware operated indicator lamp displayed from the module;
  • FIG. 4 is a schematic of the onboard diagnostic port memory module indicating the backup battery, clock, the memory, signal conditioner for reading the vehicle onboard diagnostic port, and finally the RS 232 driver for connection to a PC serial port;
  • FIGS. 5A-5E are wiring schematics of the onboard diagnostic port memory module used with this invention with:
  • FIG. 5A illustrating the microcontroller section;
  • FIG. 5B illustrating the physical interface to the vehicle for the PWM and VPW protocols;
  • FIG. 5C illustrating the physical interface to the vehicle for the ISO mode;
  • FIG. 5D illustrating the optional IrDA interface allowing the module to communicate with a personal digital assistant (PDA); and,
  • FIG. 5E illustrating the actual connection to the vehicle;
  • FIG. 6 is a firmware logic diagram of the firmware within the onboard diagnostic port memory module for recordation of data during vehicle operation;
  • FIG. 7 is a software logic diagram between the onboard diagnostic port memory module and a connected PC for both furnishing the module with settings and downloading data for analysis; and,
  • FIGS. 8A through 8H are representative plots and tables of the recorded data where:
  • FIG. 8A is a plot of speed against elapsed time indicating normal or conservative driving;
  • FIG. 8B is a plot of speed against elapsed time indicating abnormal, risk incurring driving with hard and extreme braking and accelerating;
  • FIG. 8C is a tabular presentation all of time, speed, engine speed, coolant temperature, engine load, and battery voltage useful in diagnosing engine operation;
  • FIG. 8D is a tabular presentation of elapsed time vs. speed from which acceleration and deceleration as well as distance traveled can be determined;
  • FIG. 8E is a graphical plot of coolant temperature vs. elapsed time for diagnosing engine temperature and thermostat operation;
  • FIG. 8F is a tabular plot of elapsed time, speed, engine speed, engine load, and coolant temperature;
  • FIG. 8G is a graphical plot of data triggering operation of an accident log wherein operating parameters are stored in a first in, last out stack for preserving data indicating a possible accident and,
  • FIG. 8H is a tabular presentation of the data triggering operation of the accident log.
  • DETAILED DESCRIPTION OF THE INVENTION
  • Referring to FIG. 1, a driver console C is shown. An onboard diagnostic port 1 is typically configured under the dashboard adjacent to the steering column.
  • Referring to FIG. 2, aofn onboard diagnostic port memory module 10 has a 8 pin connector port 11 with a 9 pin connector 12 and power supply 13 for connection to the serial port of a PC 14. At PC 14 data can be conventionally printed, transmitted to the Internet, or otherwise processed. As will be understood, this invention also contemplates reading of data using IrDA ports.
  • Referring to FIG. 3A and 3B, the onboard diagnostic port memory module 10 of this invention is illustrated as being plugged into OBD II port 1. In the plugged-in disposition, a firmware operated indicator light 2 can be used for indicating any number of selected functions including the presence of communication between the module 10 and the OBD II port.
  • Referring to FIG. 4, a schematic of onboard diagnostic port memory module 10 is illustrated. Three-volt battery 11 operates real-time clock 12 for the purpose of time stamping data. The time signal is given to CPU 13. When the module is connected to the OBD II port, signal conditioner 17 recognizes the particular language emitted by the vehicle and configures module 10 to receive data in the SAE J1850 (GM, Ford), ISO, ISO 9141 (Chrysler and most foreign cars) and KWP 2000 (many 2001 and later foreign cars) formats. Data is then channeled directly to memory 15.
  • Continuing with FIG. 4, programming and downloading of onboard diagnostic port memory module 10 occurs through PC serial port 20 connection and RS 232 driver 16. During programming, firmware within CPU 13 has parameters set for data recordation. During downloading, inquiry is made through the RS 232 driver for CPU 13 to download memory 15.
  • Having set forth in the general configuration of onboard diagnostic memory module 10, circuitry for use with this device can be understood with respect to FIGS. 5A through 5E.
  • There are five major sections to the design of the onboard diagnostic memory module 10 hardware. These are the Microcontroller Section shown in FIG. 5A, the PWM/VPW Physical Layer shown in FIG. 5B, the ISO Physical Layer shown in FIG. 5C, the Optional IrDA Interface shown in FIG. 5D, and the J1962 Interface shown in FIG. 5E.
  • As of this writing, the onboard diagnostic memory module design contains two printed circuit boards (PCBs), which are stacked on top of each other and connected via a single connector. The “top” board contains sections in FIGS. 5A, B, C, and D above, and the “bottom” board contains section in FIG. 5E.
  • At present, there are two variations of the onboard diagnostic memory module design: the “basic” version and the “advanced” version. The basic version runs on 5.0V and has a smaller serial flash memory while the advanced version runs on 3.3V and has a larger serial flash memory. Please refer to the schematics for each of the versions.
  • Bother versions (basic and advanced) support all four types of vehicle protocols using the same hardware: PWM, VPW, and the two variants of ISO. Each section will be described in the sections below.
  • The microcontroller section forms the heart of the design.
  • U8 is an ATMEL ATmega 16L microcontroller, with on board flash memory, SPI communications bus, and a UART. The microcontroller is supplied with an 8 MHz clock by crystal X2. The microcontroller is powered from 5.0V in the “basic” version of the product, and 3.3V in the “advanced” version.
  • U2 is an ATMEL serial flash memory chip where the trip log data is stored. The basic version of the onboard diagnostic memory module uses an AT45D011 1 mega-bit memory, while the advanced version uses an AT45DB041B 4 mega-bit part. The serial flash memory is powered from 5.0V in the basic version and 3.3V in the advanced version.
  • U5 is a Real Time Clock (RTC), which provides a non-volatile time source for the product. When no power is applied to the onboard diagnostic memory module, the RTC is powered from 3V battery BT1 (see J1962 Interface Section). When the onboard diagnostic memory module is powered, power to the RTC is supplied from either 5.0V (basic) or 3.3V (advanced). The clock communicates to the microcontroller (U8) via a two-wire communications bus.
  • U4 is a RS232 level shifter to provide communications with a PC. U4 has an integral charge pump to generate the proper voltage levels and operates from either 5.0V (basic) or 3.3V (advanced).
  • JP1 is a connector that provides the link to the PC when the onboard diagnostic memory module 10 is not plugged into the vehicle. There are three types of signals provided on this connector: a) external power, b) RS232 to PC, and c) SPI bus for development use. Note that diode D2 isolates the external power source from the vehicle power source if they are connected at the same time. The pin assignments are as follows:
    PIN SIGNAL
    1 External Power (7 to 15 V)
    2 RS232 Output (TXD)
    3 RS232 Input (RXD)
    4 SPI (MOSI)
    5 SPI (MISO)
    6 SPI (SCK)
    7 Microcontroller Reset
    8 Ground
  • The PWM/VPW Physical Layer (see FIG. 5B) provides the physical interface to the vehicle for the PWM and VPW protocols. Common parts are shared between the implementation of the two protocols in order to minimize cost and complexity.
  • U6A is an Operational Amplifier (Op Amp), which drives the J1850 Plus line for both the PWM and VPW modes. It is configured as a non-inverting amplifier with a gain of four (4) and the input on pin 3. Q1 is a NPN transistor and is used to provide a high current drive source.
  • The components R6, R8, C16, and R16 create a wave shaping network that drive the input of U6A (for the values of these components see the BOM for the basic and advanced models). The input of this network is the output of microcontroller U8 pin 14, PWM/VPW TXD. In the basic mode, this voltage is 5.0V when high and in the advanced model it is 3.3V when high. The output of the network (i.e. the input to U6 pin 3) is 2.0V in VPW mode and 1.25V in PWM mode, resulting in a signal on the J1850 Plus line of 8.0V in VPW mode and 5.0V in PWM mode.
  • Q2 is a NPN transistor that forms the drive for the J1850 Minus line. In PWM mode, Q2 is actively driven on and off in complement to Q1 thus creating a differential signal between the J1850 Plus and J1850 Minus lines. In VPW mode, Q2 is forced off, leaving the J1850 Minus line disconnected.
  • R7 and R14 form a bias network for PWM mode. If undriven or disconnected from the vehicle, the J1850 Plus line will be pulled low and the J1850 Minus line will be pulled high (5.0V).
  • R15, C17, and Q3 create a termination circuit for VPW mode. In VPW mode, Q3 is turned on thus enabling the termination. In PWM mode, Q3 is left off.
  • U6B and associated circuitry form a differential receiver for PWM mode. R18 provides approximately 10% hysteresis for noise immunity. Q4 provides a level shifter and inverter for the output signal that goes to the microcontroller U8 pin 16 (PWM/VPW RXD).
  • U6C and associated circuitry form a receiver for VPW mode. The reference value of 3.75V is used to compare against the VPW signal (which is nominally between 8V and 0V). R23 provides about 10% hysteresis for noise immunity, and Q5 creates a level shifter and inverter for the output signal, which is logically “OR'ed” with the signal from Q4 via an open collector configuration.
  • In PWM mode, Q5 is disabled (MODE3 forced low) and the signal to the microcontroller is derived from Q4. In VPW mode, Q4 is disabled (MODE2 forced low) and the signal to the microcontroller is derived from Q5.
  • The ISO Physical Layer (see FIG. 5C) provides the physical interface to the vehicle for the ISO mode.
  • Transistor Q6 (NPN) forms the drive for the ISO L line and Q7 forms the drive for the ISO K line.
  • U6D and associated circuitry form a receiver for ISO mode. The reference value of approximately 6.0V is used to compare against the ISO K signal (which is nominally between 12V and 0V). R36 provides about 10% hysteresis for noise immunity, and Q8 creates a level shifter and inverter for the output signal, which is connected to the microcontroller U8 pin 24.
  • JP2 is a socket (row of plated through holes), which provides the connection to the bottom board. The pin assignments are as follows:
    PIN SIGNAL
    1 5.0 V Logic Supply
    2  12 V (vehicle battery voltage)
    3 ISO K
    4 ISO L
    5 J1850 Plus
    6 J1850 Minus
    7 RTC backup battery BT1
    8 Ground
    9 Battery voltage analog input
    10 3.3 V Logic Supply
  • The Optional IrDA Interface (see FIG. 5D) allows the onboard diagnostic memory module to communicate with a Personal Digital Assistant (PDA) using the wireless IrDA industry standard.
  • U10 is an “ENDEC” (Encoder/Decoder) chip that converts the serial data from the microcontroller U8 into a pulse train suitable for IrDA communication. U10 is supplied with a clock source equal to 16 times the serial baud rate from U8 pin 16, XCLK.
  • U11 is an IrDA transceiver that interfaces directly to the IR transmitter (LED D5) and the IR receiver (PIN diode D6).
  • If populated, both U10 and U11 are supplied from 3.3V in the advanced model, and 5.0V in the basic model.
  • The J1962 Interface (see FIG. 5E) is the actual connection to the vehicle and is located entirely on the bottom board.
  • P1 is the OBDII connector that interfaces with the vehicle:
    PIN SIGNAL
    1 NC
    2 J1850 Plus
    3 NC
    4 NC
    5 Ground
    6 NC
    7 ISO K
    8 NC
    9 NC
    10 J1850 Minus
    11 NC
    12 NC
    13 NC
    14 NC
    15 ISO L
    16 Vehicle Power
  • Resistors R2 and R4 form a voltage divider network (18.0 Vin=2.56 Vout) that is used to sense the vehicle battery voltage by the microcontroller U8.
  • Diode D3 is used to isolate the vehicle power source from the external power source (if connected).
  • D4 is a Transient Voltage Suppressor (TVS) that is used to prevent voltage surges on the vehicle battery bus from damaging the onboard diagnostic memory module.
  • BT1 is a primary (non rechargeable) 3V battery cell that is used as the backup power for the RTC U5.
  • U1 is a 5V regulator used to power the onboard diagnostic memory module circuitry.
  • C38 is a 0.1F “supercap” that is used to provide adequate hold up time when the onboard diagnostic memory module is unplugged from the vehicle. This is required so that the microcontroller has enough time to program the flash memory and perform an orderly shutdown before power is lost.
  • U13 is a 3.3V regulator that is only used in the advanced model. If the unit is a basic mode, R45 is installed instead of U13.
  • JP3 is the connector the top board that provides the following signals:
    PIN SIGNAL
    1 5.0 V Logic Supply
    2  12 V (vehicle battery voltage)
    3 ISO K
    4 ISO L
    5 J1850 Plus
    6 J1850 Minus
    7 RTC backup battery BT1
    8 Ground
    9 Battery voltage analog input
    10 3.3 V Logic Supply
  • Referring to FIG. 6, a representative firmware logic diagram is illustrated. The reader will understand that the firmware can be upgraded from time to time by the expedient of having PC 14 Internet connected, downloading a program having a new firmware configuration from a web site, running the program in the PC to replacing the firmware in the unit. This type of protocol is preferred as inconsistencies in direct transfer of such a program from the web could interfere with the operation of the onboard diagnostic memory module. As of the writing of this application, the outlined firmware is preferred.
  • First, the onboard diagnostic port memory module is connected to the OBD II port of the host vehicle and detection of the connection made at 311. Sequentially, each protocol GM [VPW], Ford [PWM], ISO, and Advanced ISO [KWP] is tried at 312 from the onboard diagnostic port memory module to the automobile through the OBD II port 1. When the language of the vehicle is identified, both the pin array and the parameters necessary for reading data passing through the pin array are selected. Data is capable of being read and retained.
  • Second, onboard diagnostic port memory module 10 must determine the starting of the vehicle. In the protocol used here, where the engine has RPMs above 400, it is presumed that the vehicle is operating. Unfortunately, with at least some vehicles where constant interrogation is made for determining engine revolutions, battery failure can occur. Such battery failure results from the automobile computer being awakened, interrogating the engine for revolutions, and thereafter returning to the standby state. To avoid this effect, vehicle voltage is monitored. Where a starter motor is utilized, vehicle voltage change occurs. Only when vehicle voltage has changed by a predetermined amount, for example down two volts, is interrogation made of engine RPMs. The RPMs are chosen to be greater than those imposed by the starter motor but less than idling speed. Thus, vehicle voltage is detected at 314 and where voltage detection occurs, RPMs are measured at 315. This causes the storage of trip start data at 316.
  • Third, there is always the possibility of onboard diagnostic module 10 being disconnected from OBD II port 1, say where a driver chooses to have an unmonitored trip. In this case, tampered time 317 is recorded responsive to the drop in voltage caused by the disconnection. However, since engine revolutions will not be monitored in this instance, the data recorded will indicate onboard diagnostic module 10 disconnection from OBD II port 1.
  • Referring to FIG. 6, monitoring of vehicle speed occurs on a once-a-second basis at speed monitors 320. Thereafter, using previously recorded speeds, acceleration and deceleration is computed at 322. This data is temporarily stored at 324. Normal speed is recorded at 5-second intervals. Therefore, counter 325 asks each fifth speed count to be stored. Further, speed counts one through four are discarded during normal module operation at 326.
  • Returning to the calculation of acceleration and deceleration at 322, a probable accident log can be maintained. Specifically, and where deceleration has a threshold greater than certain preset limits, and the vehicle speed goes to zero, a log of these unusual events can be maintained. All vehicle events occurring within the previous 20 seconds are remembered in a stack. Data stored in this stack can be subsequently accessed.
  • It remains for the end of trip to be detected. Specifically, and at the end of each 5-second interval, engine speed is monitored at 327 to determine whether RPMs are above a certain preset limit, here shown as 400 RPMs. This speed is faster than that speed generated by the starter motor but less than the normal speed of the engine when it is idling. If engine speed in the preset amount (over 400 RPMs) is detected, the recordation cycle continues. If the speed is not detected, it is presumed that the trip is ended and the end-of-trip data is stored at 328.
  • Referring to FIG. 7, the software logic diagram is illustrated. The onboard diagnostic port memory module is schematically illustrated having data 410 and settings 411. A communication port 420 is shown communicating between onboard diagnostic module 10 and personal computer 14. Upon the initial connection to the PC, serial port identification 422 is determined. Thereafter, three discrete functions can be actuated with in onboard diagnostic module 10.
  • First, the onboard diagnostic module memory can be cleared at 425.
  • Second, the onboard diagnostic module memory can be downloaded at 426. This can include data viewing 427 of the trip log 428, activity log 429, the accident log 430, and the vehicle trouble log 431. Provision is made to store the accumulated data at 432 and to recover previously stored data at 433. Additionally, provision is made to label the onboard diagnostic module unit number, unit name, and particular vehicle utilized. For example, onboard diagnostic memory module 10 could be assigned to a particular driver, and that driver could have a choice of vehicles to operate. Each time the driver plugged onboard diagnostic memory module 10 into a vehicle to be operated, vehicle identity would be recorded at 440 along with the driver's identification.
  • Third, the onboard diagnostic port memory module can be configured at 450. Such configuration can include speed bands 451, deceleration or brake bands 452, acceleration bands 453, operational parameters 454, and finally the required time stamping clock setting at 455.
  • Referring to FIG. 8A, a plot of a car trip is presented. Elapsed time of the trip is plotted against vehicle speed. By way of example, deceleration or brake bands 452 and acceleration bands 453 can be chosen to be 0.28 gravity fields for hard braking and 0.48 gravity fields for extreme braking. Speed bands can likewise be selected. A typical selection could include 75 miles per hour and above [band I], 60 to 75 miles per hour [band II], 45 to 60 miles per hour [band III], and 0 to 45 miles per hour [band IV]. As can be seen in FIGS. 8A and 8B, such information can be graphically presented.
  • The particular utility of superimposing hard and extreme braking on the display data is apparent with respect to FIGS. 8B. Specifically, the data represented is commonly associated with the driving habit known as “following too close.” As can be seen in the plot, numerous braking incidents are recorded in the hard and extreme categories. Additionally, the drive is indicating abuse of the vehicle with rapid accelerations.
  • Referring to FIG. 8C, a data plot is shown listing elapsed time relative to speed, engine speed, cooling temperature, engine load, and battery voltage.
  • Referring to FIG. 8D, a plot of elapsed time vs. speed in miles per hour is illustrated. The reader will understand that from such data, both acceleration and deceleration as well as the distance traveled can be determined. In actual practice, speed traveled is frequently recorded. From the frequent recordings, accelerations and decelerations as well as distance traveled are computed, the former by differentiation and the latter by integration. Once this data is accumulated, intermediate velocity points can be discarded with the remaining velocity points being maintained in a table such as fat shown in FIG. 8D.
  • Referring to FIG. 8E, a plot of cooling temperature vs. time for a trip is illustrated. In this plot, possible malfunction of an automobile thermostat is illustrated.
  • Referring to FIG. 8F, a tabular plot of elapsed time, speed, engine speed, engine load, and cooling temperature is shown. It should be understood that through conventional manipulation of PC software, arrays of data can be presented in any desired format.
  • Referring to FIGS. 8G and 8H, and then triggering an “accident log” is respectively graphically and tabularly illustrated. It can be immediately seen that the event here is triggered by rapid deceleration. When such a profile is detected by the disclosed onboard diagnostic port memory module, all operating data is preserved in a dense format. Further, the operating data in its dense format is transferred to a first in, last out data stack having capacity in the usual case for between 30 and 32 such events. In this manner, the onboard diagnostic memory module can maintain for a substantial period of time operating vehicle profiles for accident situations. Thus, with the onboard diagnostic memory module of this invention, vehicle operating parameters that would be questions of controverted fact in the normal accident situations become unquestioned recorded data.
  • It is to be understood that the parameters for triggering an accident log recordation can be altered.

Claims (14)

1. An onboard diagnostic memory module for an onboard diagnostic port of a vehicle comprising:
a connection to an onboard diagnostic port output of a vehicle;
a memory for receiving and emitting recorded data from the connection to the onboard diagnostic port output of the vehicle;
a clock and clock power supply for time stamping the recorded data in the memory for receiving and emitting recorded data;
a microprocessor responsive to operational firmware for manipulating data to and from the memory through the connection to the onboard diagnostic port output of the vehicle;
memory operationally connected to the microprocessor for receiving the operational firmware;
the operational firmware including;
data receiving and recording parameters for the memory during the connection to the onboard diagnostic port output of the vehicle; and,
discharge parameters for discharging the recorded data responsive to intelligent interrogation of a PC having a connection to the onboard diagnostic memory module.
2. The onboard diagnostic memory module of claim 1 in wherein the connection to the onboard diagnostic port output of the vehicle includes:
a plugged connection to the onboard diagnostic port of the vehicle.
3. The onboard diagnostic memory module of claim 1 in wherein the connection to the onboard diagnostic port output of the vehicle includes:
a wired connection to the onboard diagnostic port of the vehicle.
4-10. (canceled)
11. The process of recording and analyzing data from the combination of an onboard diagnostic memory module, a vehicle having an onboard diagnostic port, and a PC having intelligent programming for the onboard diagnostic memory module comprising:
providing a vehicle having an onboard diagnostic port for emitting data;
providing an onboard diagnostic memory module including:
a connection to an onboard diagnostic port output of a vehicle;
a memory for receiving and emitting recorded data from the connection to the onboard diagnostic port output of the vehicle;
a clock and clock power supply for time correlation to the recorded data in the memory for receiving and emitting recorded data;
a microprocessor responsive to operational firmware for manipulating data to and from the memory through the connection to the onboard diagnostic port output of the vehicle;
memory operationally connected to the microprocessor for receiving the operational firmware;
the operational firmware including;
data receiving and recording parameters for the memory during the connection to the onboard diagnostic port output of the vehicle; and,
discharge parameters for discharging the recorded data responsive to intelligent interrogation of a PC having a connection to the onboard diagnostic memory module;
providing a PC having;
interrogation parameters for the onboard diagnostic memory module; and,
emitting data receiving and recording parameters to the onboard diagnostic port memory module;
connecting the onboard diagnostic memory module to the PC to receive the data receiving and recording parameters;
sending from the PC to the onboard diagnostic memory module the data receiving and recording parameters;
connecting the onboard diagnostic memory module to the vehicle at the onboard diagnostic port;
recording data during operation of the vehicle at the onboard diagnostic port;
connecting the onboard diagnostic memory module to the PC; and,
interrogating the onboard diagnostic memory module recover the recorded data sending at least some of the recorded data over the Internet for diagnosis.
12. The process of recording and analyzing data from the combination of an onboard diagnostic memory module, a vehicle having an onboard diagnostic port, and a PC having intelligent programming for the onboard diagnostic memory module comprising:
providing a vehicle having an onboard diagnostic port for emitting data;
providing an onboard diagnostic memory module including:
a connection to an onboard diagnostic port output of a vehicle;
a memory for receiving and emitting recorded data from the connection to the onboard diagnostic port output of the vehicle;
a clock and clock power supply for time correlation to the recorded data in the memory for receiving and emitting recorded data;
a microprocessor responsive to operational firmware for manipulating data to and from the memory through the connection to the onboard diagnostic port output of the vehicle;
memory operationally connected to the microprocessor for receiving the operational firmware;
the operational firmware including;
data receiving and recording parameters for the memory during the connection to the onboard diagnostic port output of the vehicle; and,
discharge parameters for discharging the recorded data responsive to intelligent interrogation of a PC having a connection to the onboard diagnostic memory module;
providing a PC having;
interrogation parameters for the onboard diagnostic memory module; and,
emitting data receiving and recording parameters to the onboard diagnostic port memory module;
connecting the onboard diagnostic memory module to the PC to receive the data receiving and recording parameters;
sending from the PC to the onboard diagnostic memory module the data receiving and recording parameters;
connecting the onboard diagnostic memory module to the vehicle at the onboard diagnostic port;
recording data during operation of the vehicle at the onboard diagnostic port;
connecting the onboard diagnostic memory module to the PC; and,
interrogating the onboard diagnostic memory module recover the recorded data recording speed data; and,
time stamping the recorded speed data with time from the clock.
13. The process of recording data from the onboard diagnostic port of an operating vehicle according to claim 12 and wherein:
downloading the onboard diagnostic port of the vehicle to a PC; and,
plotting the speed data versus time on a PC.
14. The process of recording data from the onboard diagnostic port of an operating vehicle according to claim 13 and wherein the step of plotting the speed data versus time on a PC includes:
displaying a graph of speed versus time from the PC.
15. (canceled)
16. The process of recording and analyzing data from the combination of an onboard diagnostic memory module, a vehicle having an onboard diagnostic port, and a PC having intelligent programming for the onboard diagnostic memory module comprising:
providing a vehicle having an onboard diagnostic port for emitting data;
providing an onboard diagnostic memory module including:
a connection to an onboard diagnostic port output of a vehicle;
a memory for receiving and emitting recorded data from the connection to the onboard diagnostic port output of the vehicle;
a clock and clock power supply for time correlation to the recorded data in the memory for receiving and emitting recorded data;
a microprocessor responsive to operational firmware for manipulating data to and from the memory through the connection to the onboard diagnostic port output of the vehicle;
memory operationally connected to the microprocessor for receiving the operational firmware;
the operational firmware including;
data receiving and recording parameters for the memory during the connection to the onboard diagnostic port output of the vehicle; and,
discharge parameters for discharging the recorded data responsive to intelligent interrogation of a PC having a connection to the onboard diagnostic memory module;
providing a PC having;
interrogation parameters for the onboard diagnostic memory module; and,
emitting data receiving and recording parameters to the onboard diagnostic port memory module;
connecting the onboard diagnostic memory module to the PC to receive the data receiving and recording parameters;
sending from the PC to the onboard diagnostic memory module the data receiving and recording parameters;
connecting the onboard diagnostic memory module to the vehicle at the onboard diagnostic port;
recording data during operation of the vehicle at the onboard diagnostic port;
connecting the onboard diagnostic memory module to the PC; and,
interrogating the onboard diagnostic memory module recover the recorded data sending of at least some of the recorded data over the Internet for diagnosis includes:
downloading the onboard diagnostic port of the vehicle to a PC; and,
sending the data to the Internet from a PC.
17. The process of recording data from the onboard diagnostic port of an operating vehicle according to claim 11 including the step of:
permanent attachment of the onboard diagnostic memory module to the vehicle.
18. The process of recording data from the onboard diagnostic port of an operating vehicle according to claim 11 including the step of:
permanent attachment of the onboard diagnostic memory module to the onboard diagnostic port of the vehicle.
19. The process of recording data from the onboard diagnostic port of an operating vehicle according to claim 11 and wherein designating operational parameters for the recordation of recorded data in the memory of the onboard diagnostic port memory module includes the steps of:
connecting the onboard diagnostic port memory module to a PC;
altering the operational firmware at the PC to impart data collection parameters to the onboard diagnostic port memory module; and,
connecting the onboard diagnostic port memory module to the operating vehicle.
20. A process for recording to an onboard diagnostic port memory module for an onboard diagnostic port of a vehicle, the process comprising:
providing an onboard diagnostic port memory module having
a connection to an onboard diagnostic port output of a vehicle;
a memory for receiving and emitting recorded data from the connection to the onboard diagnostic port output of the vehicle;
a clock and clock power supply for time stamping the recorded data in the memory for receiving and emitting recorded data;
a microprocessor responsive to operational firmware for manipulating data to and from the memory through the connection to the onboard diagnostic port output of the vehicle;
memory operationally connected to the microprocessor for receiving the operational firmware;
the operational firmware including;
data receiving and recording parameters for the memory during the connection to the onboard diagnostic port output of the vehicle; and,
discharge parameters for discharging the recorded data responsive to intelligent interrogation of a PC having a connection to the onboard diagnostic port memory module;
monitoring the engine for engine operation;
recording data for a trip upon starting of engine operation;
ceasing recording of data for a trip upon ceasing the engine operation;
maintaining vehicle operational parameters between the starting of the engine and the stopping of the engine as a block of data indicating a trip.
US10/979,346 2002-10-25 2004-11-01 Module for monitoring vehicle operation through onboard diagnostic port Abandoned US20050096809A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/979,346 US20050096809A1 (en) 2002-10-25 2004-11-01 Module for monitoring vehicle operation through onboard diagnostic port

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/281,330 US6832141B2 (en) 2002-10-25 2002-10-25 Module for monitoring vehicle operation through onboard diagnostic port
US10/979,346 US20050096809A1 (en) 2002-10-25 2004-11-01 Module for monitoring vehicle operation through onboard diagnostic port

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/281,330 Division US6832141B2 (en) 2002-10-25 2002-10-25 Module for monitoring vehicle operation through onboard diagnostic port

Publications (1)

Publication Number Publication Date
US20050096809A1 true US20050096809A1 (en) 2005-05-05

Family

ID=32107138

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/281,330 Expired - Lifetime US6832141B2 (en) 2002-10-25 2002-10-25 Module for monitoring vehicle operation through onboard diagnostic port
US10/979,346 Abandoned US20050096809A1 (en) 2002-10-25 2004-11-01 Module for monitoring vehicle operation through onboard diagnostic port

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/281,330 Expired - Lifetime US6832141B2 (en) 2002-10-25 2002-10-25 Module for monitoring vehicle operation through onboard diagnostic port

Country Status (4)

Country Link
US (2) US6832141B2 (en)
AU (1) AU2003282831A1 (en)
CA (1) CA2494350C (en)
WO (1) WO2004040405A2 (en)

Cited By (93)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040153362A1 (en) * 1996-01-29 2004-08-05 Progressive Casualty Insurance Company Monitoring system for determining and communicating a cost of insurance
US20060041347A1 (en) * 2004-08-19 2006-02-23 Spx Corporation Open-ended vehicle diagnostic device interface
US20060052929A1 (en) * 2003-03-28 2006-03-09 Dieter Bastian Method for controlling the speed of a motor vehicle in accordance with risk and system for carrying out the method
US20060106584A1 (en) * 2003-10-08 2006-05-18 Oesterling Christopher L Captured test fleet
US20060235580A1 (en) * 2002-06-10 2006-10-19 Cornelia Weiss Method and device for a vehicle-related telematics service
US20070156311A1 (en) * 2005-12-29 2007-07-05 Elcock Albert F Communication of automotive diagnostic data
US20070198147A1 (en) * 2005-08-19 2007-08-23 Keith William J On-board diagnostic system including automatic communications bus disconnect
US20080015748A1 (en) * 2006-07-14 2008-01-17 David Nagy System for monitoring, controlling, and reporting vehicle operation through onboard diagnostic port
US20080016504A1 (en) * 2006-07-14 2008-01-17 Wesley Homer Cheng Dynamically programmable electronic data collection system combining declarative programming and native coding
US20080016207A1 (en) * 2006-07-14 2008-01-17 Wesley Homer Cheng Electronic driver log application with bi-directional messaging to multiple backend systems
US20080082221A1 (en) * 2006-07-14 2008-04-03 David Nagy System for monitoring, controlling, and reporting vehicle operation through onboard diagnostic port
US20080221776A1 (en) * 2006-10-02 2008-09-11 Mcclellan Scott System and Method for Reconfiguring an Electronic Control Unit of a Motor Vehicle to Optimize Fuel Economy
US20080255718A1 (en) * 2007-04-10 2008-10-16 Maurice Tuff Vehicle monitor
US20080252487A1 (en) * 2006-05-22 2008-10-16 Mcclellan Scott System and method for monitoring and updating speed-by-street data
US20080258890A1 (en) * 2006-05-22 2008-10-23 Todd Follmer System and Method for Remotely Deactivating a Vehicle
US20080306996A1 (en) * 2007-06-05 2008-12-11 Mcclellan Scott System and Method for the Collection, Correlation and Use of Vehicle Collision Data
US20090049341A1 (en) * 2007-08-17 2009-02-19 Moises Cases Method for Performing Memory Diagnostics Using a Programmable Diagnostic Memory Module
US20090049339A1 (en) * 2007-08-17 2009-02-19 Moises Cases Programmable Diagnostic Memory Module
US20090051510A1 (en) * 2007-08-21 2009-02-26 Todd Follmer System and Method for Detecting and Reporting Vehicle Damage
US20100010705A1 (en) * 2005-10-20 2010-01-14 Airmax Group Plc Methods and apparatus for monitoring vehicle data
WO2010011840A1 (en) * 2008-07-24 2010-01-28 Hamilton Performance Electronics, Llc System and method for emulating vehicle ignition-switched power
US20110015822A1 (en) * 2004-08-19 2011-01-20 Troy Liebl Vehicle Diagnostic Device
US20110015815A1 (en) * 2007-07-17 2011-01-20 Bertness Kevin I Battery tester for electric vehicle
US7876205B2 (en) 2007-10-02 2011-01-25 Inthinc Technology Solutions, Inc. System and method for detecting use of a wireless device in a moving vehicle
US7999670B2 (en) 2007-07-02 2011-08-16 Inthinc Technology Solutions, Inc. System and method for defining areas of interest and modifying asset monitoring in relation thereto
US20110208454A1 (en) * 2000-03-27 2011-08-25 Bertness Kevin I Scan tool for electronic battery tester
US20110218747A1 (en) * 2010-03-03 2011-09-08 Bertness Kevin I Monitor for front terminal batteries
US20120035800A1 (en) * 2010-08-03 2012-02-09 Spx Corporation Vehicle Diagnostic, Communication and Signal Delivery System
US8140358B1 (en) 1996-01-29 2012-03-20 Progressive Casualty Insurance Company Vehicle monitoring system
US20120203441A1 (en) * 2011-02-03 2012-08-09 Raytheon Company Low-drain, self-contained monitoring device
US8340855B2 (en) 2008-04-22 2012-12-25 Spx Corporation USB isolation for vehicle communication interface
US20120330494A1 (en) * 2011-05-26 2012-12-27 Hendrix Walter M Electric vehicle fleet charging system
US20130104186A1 (en) * 2010-02-22 2013-04-25 Continental Automotive Gmbh System and method for preventing an attack on a networked vehicle
US8447464B2 (en) 2007-08-02 2013-05-21 North-Line Canada Ltd. System and method for interfacing between an on-board diagnostic output and a distance measuring instrument input
US8577703B2 (en) 2007-07-17 2013-11-05 Inthinc Technology Solutions, Inc. System and method for categorizing driving behavior using driver mentoring and/or monitoring equipment to determine an underwriting risk
US20140058802A1 (en) * 2011-06-30 2014-02-27 Xrs Corporation Fleet vehicle management systems and methods
US8666590B2 (en) 2007-06-22 2014-03-04 Inthinc Technology Solutions, Inc. System and method for naming, filtering, and recall of remotely monitored event data
US20140074353A1 (en) * 2012-09-12 2014-03-13 Anydata Corporation Vehicle telematics control via ignition detection
US8688180B2 (en) 2008-08-06 2014-04-01 Inthinc Technology Solutions, Inc. System and method for detecting use of a wireless device while driving
WO2014089171A1 (en) * 2012-12-04 2014-06-12 I.D. Systems, Inc. Remote vehicle rental systems and methods
US8818618B2 (en) 2007-07-17 2014-08-26 Inthinc Technology Solutions, Inc. System and method for providing a user interface for vehicle monitoring system users and insurers
US8924240B2 (en) 2011-05-25 2014-12-30 Shailendra Depura System for monitoring vehicle and operator behavior
US8958998B2 (en) 1997-11-03 2015-02-17 Midtronics, Inc. Electronic battery tester with network communication
US8963550B2 (en) 2004-08-20 2015-02-24 Midtronics, Inc. System for automatically gathering battery information
US8963702B2 (en) 2009-02-13 2015-02-24 Inthinc Technology Solutions, Inc. System and method for viewing and correcting data in a street mapping database
US9018958B2 (en) 2003-09-05 2015-04-28 Midtronics, Inc. Method and apparatus for measuring a parameter of a vehicle electrical system
US9067565B2 (en) 2006-05-22 2015-06-30 Inthinc Technology Solutions, Inc. System and method for evaluating driver behavior
US9117246B2 (en) 2007-07-17 2015-08-25 Inthinc Technology Solutions, Inc. System and method for providing a user interface for vehicle mentoring system users and insurers
US9129460B2 (en) 2007-06-25 2015-09-08 Inthinc Technology Solutions, Inc. System and method for monitoring and improving driver behavior
US9127946B1 (en) 2014-05-15 2015-09-08 State Farm Mutual Automobile Insurance Company System and method for identifying heading of a moving vehicle using accelerometer data
US9129336B2 (en) 2012-12-04 2015-09-08 I.D. Systems, Inc. Remote vehicle rental systems and methods
US9172477B2 (en) 2013-10-30 2015-10-27 Inthinc Technology Solutions, Inc. Wireless device detection using multiple antennas separated by an RF shield
US9201120B2 (en) 2010-08-12 2015-12-01 Midtronics, Inc. Electronic battery tester for testing storage battery
US9229062B2 (en) 2010-05-27 2016-01-05 Midtronics, Inc. Electronic storage battery diagnostic system
US9244100B2 (en) 2013-03-15 2016-01-26 Midtronics, Inc. Current clamp with jaw closure detection
US9255955B2 (en) 2003-09-05 2016-02-09 Midtronics, Inc. Method and apparatus for measuring a parameter of a vehicle electrical system
US9286265B2 (en) * 2010-10-28 2016-03-15 Innovation Gap Inc. Device and method for managing an electronic control unit of a vehicle
US9312575B2 (en) 2013-05-16 2016-04-12 Midtronics, Inc. Battery testing system and method
US9335362B2 (en) 2007-07-17 2016-05-10 Midtronics, Inc. Battery tester for electric vehicle
US9360322B2 (en) 2014-05-15 2016-06-07 State Farm Mutual Automobile Insurance Company System and method for separating ambient gravitational acceleration from a moving three-axis accelerometer data
US9418491B2 (en) * 2014-09-22 2016-08-16 Brian K. Phillips Method and system for automatically identifying a driver by creating a unique driver profile for a vehicle from driving habits
US9419311B2 (en) 2010-06-18 2016-08-16 Midtronics, Inc. Battery maintenance device with thermal buffer
US9496720B2 (en) 2004-08-20 2016-11-15 Midtronics, Inc. System for automatically gathering battery information
US9588185B2 (en) 2010-02-25 2017-03-07 Keith S. Champlin Method and apparatus for detecting cell deterioration in an electrochemical cell or battery
US9786103B2 (en) 2014-05-15 2017-10-10 State Farm Mutual Automobile Insurance Company System and method for determining driving patterns using telematics data
US9818151B2 (en) 2012-12-04 2017-11-14 I.D. Systems, Inc. Remote vehicle rental systems and methods
US9851411B2 (en) 2012-06-28 2017-12-26 Keith S. Champlin Suppressing HF cable oscillations during dynamic measurements of cells and batteries
US9923289B2 (en) 2014-01-16 2018-03-20 Midtronics, Inc. Battery clamp with endoskeleton design
US9966676B2 (en) 2015-09-28 2018-05-08 Midtronics, Inc. Kelvin connector adapter for storage battery
US10019762B2 (en) 2014-05-15 2018-07-10 State Farm Mutual Automobile Insurance Company System and method for identifying idling times of a vehicle using accelerometer data
US10046649B2 (en) 2012-06-28 2018-08-14 Midtronics, Inc. Hybrid and electric vehicle battery pack maintenance device
US20180268626A1 (en) * 2015-03-06 2018-09-20 Sony Corporation Recording device, recording method, and computer program
US20180345985A1 (en) * 2015-12-15 2018-12-06 Greater Than S.A. Method and system for assessing the trip performance of a driver
US10222397B2 (en) 2014-09-26 2019-03-05 Midtronics, Inc. Cable connector for electronic battery tester
US10275951B2 (en) * 2016-06-16 2019-04-30 Hyundai Motor Company Communication control device, vehicle having the communication control device, and method for controlling the vehicle
US10304138B2 (en) 2014-05-15 2019-05-28 State Farm Mutual Automobile Insurance Company System and method for identifying primary and secondary movement using spectral domain analysis
US10317468B2 (en) 2015-01-26 2019-06-11 Midtronics, Inc. Alternator tester
US10429449B2 (en) 2011-11-10 2019-10-01 Midtronics, Inc. Battery pack tester
US10473555B2 (en) 2014-07-14 2019-11-12 Midtronics, Inc. Automotive maintenance system
US10493996B2 (en) 2014-09-22 2019-12-03 Future Technology Partners, Llc Method and system for impaired driving detection, monitoring and accident prevention with driving habits
US10608353B2 (en) 2016-06-28 2020-03-31 Midtronics, Inc. Battery clamp
US10843574B2 (en) 2013-12-12 2020-11-24 Midtronics, Inc. Calibration and programming of in-vehicle battery sensors
US11030702B1 (en) 2012-02-02 2021-06-08 Progressive Casualty Insurance Company Mobile insurance platform system
US11054480B2 (en) 2016-10-25 2021-07-06 Midtronics, Inc. Electrical load for electronic battery tester and electronic battery tester including such electrical load
US11325479B2 (en) 2012-06-28 2022-05-10 Midtronics, Inc. Hybrid and electric vehicle battery maintenance device
US11474153B2 (en) 2019-11-12 2022-10-18 Midtronics, Inc. Battery pack maintenance system
US11486930B2 (en) 2020-01-23 2022-11-01 Midtronics, Inc. Electronic battery tester with battery clamp storage holsters
US11513160B2 (en) 2018-11-29 2022-11-29 Midtronics, Inc. Vehicle battery maintenance device
US11545839B2 (en) 2019-11-05 2023-01-03 Midtronics, Inc. System for charging a series of connected batteries
US11566972B2 (en) 2019-07-31 2023-01-31 Midtronics, Inc. Tire tread gauge using visual indicator
US11650259B2 (en) 2010-06-03 2023-05-16 Midtronics, Inc. Battery pack maintenance for electric vehicle
US11668779B2 (en) 2019-11-11 2023-06-06 Midtronics, Inc. Hybrid and electric vehicle battery pack maintenance device
US11740294B2 (en) 2010-06-03 2023-08-29 Midtronics, Inc. High use battery pack maintenance

Families Citing this family (192)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7955169B2 (en) 2003-02-13 2011-06-07 Igt Method and apparatus for offering a flat rate gaming session with time extension awards
US20030182033A1 (en) * 2002-03-25 2003-09-25 Underdahl Craig T Vehicle usage data tracking system
US20040215379A1 (en) * 2003-04-22 2004-10-28 Vericom Compters Inc. Vehicle performance analyzer
US6931309B2 (en) * 2003-05-06 2005-08-16 Innosurance, Inc. Motor vehicle operating data collection and analysis
US7610210B2 (en) * 2003-09-04 2009-10-27 Hartford Fire Insurance Company System for the acquisition of technology risk mitigation information associated with insurance
US7711584B2 (en) 2003-09-04 2010-05-04 Hartford Fire Insurance Company System for reducing the risk associated with an insured building structure through the incorporation of selected technologies
US9311676B2 (en) 2003-09-04 2016-04-12 Hartford Fire Insurance Company Systems and methods for analyzing sensor data
US6978198B2 (en) * 2003-10-23 2005-12-20 General Motors Corporation System and method to load vehicle operation software and calibration data in general assembly and service environment
US8090599B2 (en) 2003-12-30 2012-01-03 Hartford Fire Insurance Company Method and system for computerized insurance underwriting
US7783505B2 (en) 2003-12-30 2010-08-24 Hartford Fire Insurance Company System and method for computerized insurance rating
GB2414557A (en) * 2004-05-29 2005-11-30 Richard Hoptroff Automotive Data Recorder
US20050278079A1 (en) * 2004-06-14 2005-12-15 Maguire Joel M Apparatus and method for displaying graphical information relating to vehicle operation
US7877176B2 (en) * 2004-06-24 2011-01-25 General Motors Llc Method and system for remote telltale reset
US20060036355A1 (en) * 2004-08-10 2006-02-16 Schaar David L Connector with back-up power via data link connector
WO2006050380A2 (en) * 2004-11-01 2006-05-11 Heffington, Mark Programmable automotive computer system
US7643912B2 (en) * 2004-11-01 2010-01-05 Hypertech, Inc. Programmable automotive computer method and apparatus with accelerometer input
CA2609806A1 (en) * 2005-06-01 2006-12-07 Innosurance, Inc. Motor vehicle operating data collection and analysis
US8019503B2 (en) * 2007-06-28 2011-09-13 Innova Electronics Corp Automotive diagnostic and remedial process
US9117319B2 (en) 2005-06-30 2015-08-25 Innova Electronics, Inc. Handheld automotive diagnostic tool with VIN decoder and communication system
US9818120B2 (en) 2015-02-20 2017-11-14 Innovative Global Systems, Llc Automated at-the-pump system and method for managing vehicle fuel purchases
WO2007022426A2 (en) * 2005-08-18 2007-02-22 Environmental Systems Products Holdings Inc. System and method for testing the integrity of a vehicle testing/diagnostic system
US20080140306A1 (en) * 2005-11-30 2008-06-12 Snodgrass Ken L Voice recognition method and system for displaying charts and maps
US20070132773A1 (en) * 2005-12-08 2007-06-14 Smartdrive Systems Inc Multi-stage memory buffer and automatic transfers in vehicle event recording systems
US20070150138A1 (en) * 2005-12-08 2007-06-28 James Plante Memory management in event recording systems
US10878646B2 (en) 2005-12-08 2020-12-29 Smartdrive Systems, Inc. Vehicle event recorder systems
US20070135980A1 (en) * 2005-12-09 2007-06-14 Smartdrive Systems Inc Vehicle event recorder systems
US20070135979A1 (en) * 2005-12-09 2007-06-14 Smartdrive Systems Inc Vehicle event recorder systems
US8996240B2 (en) 2006-03-16 2015-03-31 Smartdrive Systems, Inc. Vehicle event recorders with integrated web server
US9201842B2 (en) 2006-03-16 2015-12-01 Smartdrive Systems, Inc. Vehicle event recorder systems and networks having integrated cellular wireless communications systems
CA2645896A1 (en) 2006-03-16 2007-09-27 Smartdrive Systems, Inc. Vehicle event recorded systems and networks having parallel communication links
US20070284164A1 (en) * 2006-05-19 2007-12-13 Net Gain Technologies Motor vehicle with electric boost motor
US20080033609A1 (en) * 2006-08-04 2008-02-07 Ramin Razavi Automotive diagnostic and tuning system
KR100826011B1 (en) * 2006-10-24 2008-04-29 엘지디스플레이 주식회사 Display device
GB2443655A (en) 2006-11-07 2008-05-14 Jan Trzcinski A taximeter using a signal from a vehicle diagnostic system
US8989959B2 (en) 2006-11-07 2015-03-24 Smartdrive Systems, Inc. Vehicle operator performance history recording, scoring and reporting systems
US8649933B2 (en) 2006-11-07 2014-02-11 Smartdrive Systems Inc. Power management systems for automotive video event recorders
US8868288B2 (en) 2006-11-09 2014-10-21 Smartdrive Systems, Inc. Vehicle exception event management systems
US20080114707A1 (en) * 2006-11-13 2008-05-15 Centrodyne Inc. Taximeter using digital speed or distance as input
US8139820B2 (en) 2006-12-13 2012-03-20 Smartdrive Systems Inc. Discretization facilities for vehicle event data recorders
US20080147267A1 (en) * 2006-12-13 2008-06-19 Smartdrive Systems Inc. Methods of Discretizing data captured at event data recorders
US8359209B2 (en) 2006-12-19 2013-01-22 Hartford Fire Insurance Company System and method for predicting and responding to likelihood of volatility
WO2008079325A1 (en) 2006-12-22 2008-07-03 Hartford Fire Insurance Company System and method for utilizing interrelated computerized predictive models
US8239092B2 (en) * 2007-05-08 2012-08-07 Smartdrive Systems Inc. Distributed vehicle event recorder systems having a portable memory data transfer system
FR2917825B1 (en) * 2007-06-20 2009-08-28 Renault Sas DEVICE AND METHOD FOR ASSISTING THE DEVELOPMENT OF VEHICLES.
US8370018B2 (en) * 2007-06-28 2013-02-05 Innova Electronics, Inc. Automotive diagnostic process
US9026400B2 (en) 2007-06-28 2015-05-05 Innova Electonics, Inc. Diagnostic process for home electronic devices
CN100468247C (en) * 2007-09-13 2009-03-11 浙江工业大学 Monitor system collecting end device
CN101175125B (en) * 2007-09-14 2010-05-26 浙江工业大学 Front end machine device of monitoring system
CN101231519B (en) * 2007-09-14 2010-12-01 浙江工业大学 Back-end machine apparatus for monitoring system
US9613467B2 (en) * 2007-10-30 2017-04-04 Bosch Automotive Service Solutions Inc. Method of updating and configuring a scan tool
US7771075B2 (en) * 2007-12-12 2010-08-10 Eastek International Corporation Electronic device for vehicles
US9665910B2 (en) 2008-02-20 2017-05-30 Hartford Fire Insurance Company System and method for providing customized safety feedback
US20090302999A1 (en) * 2008-06-05 2009-12-10 Anzen Electronics Llc Security and monitoring control system methods for vehicles
US8280601B2 (en) * 2008-07-24 2012-10-02 GM Global Technology Operations LLC Adaptive vehicle control system with integrated maneuver-based driving style recognition
US20100019880A1 (en) * 2008-07-24 2010-01-28 Gm Global Technology Operations, Inc. Adaptive vehicle control system with driving style recognition based on traffic sensing
US8280560B2 (en) * 2008-07-24 2012-10-02 GM Global Technology Operations LLC Adaptive vehicle control system with driving style recognition based on headway distance
US8060260B2 (en) * 2008-07-24 2011-11-15 GM Global Technology Operations LLC Adaptive vehicle control system with driving style recognition based on vehicle passing maneuvers
US8260515B2 (en) * 2008-07-24 2012-09-04 GM Global Technology Operations LLC Adaptive vehicle control system with driving style recognition
US8170740B2 (en) * 2008-07-24 2012-05-01 GM Global Technology Operations LLC Adaptive vehicle control system with driving style recognition based on vehicle launching
US8195341B2 (en) * 2008-07-24 2012-06-05 GM Global Technology Operations LLC Adaptive vehicle control system with driving style recognition based on maneuvers at highway on/off ramps
US20100023265A1 (en) * 2008-07-24 2010-01-28 Gm Global Technology Operations, Inc. Adaptive vehicle control system with integrated driving style recognition
US20100023180A1 (en) * 2008-07-24 2010-01-28 Gm Global Technology Operations, Inc. Adaptive vehicle control system with driving style recognition based on lane-change maneuvers
US20100023197A1 (en) * 2008-07-24 2010-01-28 Gm Global Technology Operations, Inc. Adaptive vehicle control system with driving style recognition based on behavioral diagnosis
US7831407B2 (en) * 2008-07-24 2010-11-09 Gm Global Technology Operations, Inc. Adaptive vehicle control system with driving style recognition based on vehicle U-turn maneuvers
US20100019964A1 (en) * 2008-07-24 2010-01-28 Gm Global Technology Operations, Inc. Adaptive vehicle control system with driving style recognition and road condition recognition
CN102203810A (en) 2008-09-09 2011-09-28 美国联合包裹服务公司 Systems and methods of utilizing telematics data to improve fleet management operations
US11482058B2 (en) 2008-09-09 2022-10-25 United Parcel Service Of America, Inc. Systems and methods for utilizing telematics data to improve fleet management operations
US20100152950A1 (en) * 2008-12-15 2010-06-17 Gm Global Technology Operations, Inc. Adaptive vehicle control system with driving style recognition based on vehicle stopping
US20100152951A1 (en) * 2008-12-15 2010-06-17 Gm Global Technology Operations, Inc. Adaptive vehicle control system with driving style recognition based on vehicle accelerating and decelerating
US8892341B2 (en) 2009-02-13 2014-11-18 Inthinc Technology Solutions, Inc. Driver mentoring to improve vehicle operation
US8188887B2 (en) 2009-02-13 2012-05-29 Inthinc Technology Solutions, Inc. System and method for alerting drivers to road conditions
US20100209891A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Driving skill recognition based on stop-and-go driving behavior
US20100209884A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Driving skill recognition based on vehicle left and right turns
US20100209887A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operation, Inc. Vehicle stability enhancement control adaptation to driving skill based on vehicle backup maneuver
US20100209881A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Driving skill recognition based on behavioral diagnosis
US20100209890A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Vehicle stability enhancement control adaptation to driving skill with integrated driving skill recognition
US20100209888A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Vehicle stability enhancement control adaptation to driving skill based on curve-handling maneuvers
US20100209885A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Vehicle stability enhancement control adaptation to driving skill based on lane change maneuver
US20100209889A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Vehicle stability enhancement control adaptation to driving skill based on multiple types of maneuvers
US20100209892A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Driving skill recognition based on manual transmission shift behavior
US20100209883A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Vehicle stability enhancement control adaptation to driving skill based on passing maneuver
US20100209882A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Driving skill recognition based on straight-line driving behavior
US20100209886A1 (en) * 2009-02-18 2010-08-19 Gm Global Technology Operations, Inc. Driving skill recognition based on u-turn performance
US8170725B2 (en) * 2009-02-18 2012-05-01 GM Global Technology Operations LLC Vehicle stability enhancement control adaptation to driving skill based on highway on/off ramp maneuver
US8306687B2 (en) 2009-11-10 2012-11-06 Innova Electronics, Inc. Method of diagnosing a vehicle having diagnostic data
TWI440571B (en) * 2009-12-04 2014-06-11 Kwang Yang Motor Co Communication interface conversion device
US8355934B2 (en) 2010-01-25 2013-01-15 Hartford Fire Insurance Company Systems and methods for prospecting business insurance customers
US9311616B2 (en) * 2010-06-14 2016-04-12 On-Board Communications, Inc. System and method for determining equipment utilization changes based on ignition and motion status
US9460471B2 (en) 2010-07-16 2016-10-04 Hartford Fire Insurance Company System and method for an automated validation system
GB2483868B (en) * 2010-09-21 2015-08-26 Lysanda Ltd Vehicle diagnostics port adaptor
US8565963B2 (en) 2010-09-23 2013-10-22 Xerox Corporation Method and system for remotely tracking vehicle-centric data and user-centric data
US8751777B2 (en) 2011-01-28 2014-06-10 Honeywell International Inc. Methods and reconfigurable systems to optimize the performance of a condition based health maintenance system
US10482475B2 (en) 2011-02-10 2019-11-19 Adp Dealer Services, Inc. Systems and methods for providing targeted advertising
DE102011004207A1 (en) * 2011-02-16 2012-08-16 Robert Bosch Gmbh Mobile communication interface, system with mobile communication interface and method for identifying, diagnosing, maintaining and repairing a vehicle
US9208626B2 (en) 2011-03-31 2015-12-08 United Parcel Service Of America, Inc. Systems and methods for segmenting operational data
US9953468B2 (en) 2011-03-31 2018-04-24 United Parcel Service Of America, Inc. Segmenting operational data
US8615773B2 (en) 2011-03-31 2013-12-24 Honeywell International Inc. Systems and methods for coordinating computing functions to accomplish a task using a configuration file and standardized executable application modules
US8990770B2 (en) 2011-05-25 2015-03-24 Honeywell International Inc. Systems and methods to configure condition based health maintenance systems
US10977601B2 (en) 2011-06-29 2021-04-13 State Farm Mutual Automobile Insurance Company Systems and methods for controlling the collection of vehicle use data using a mobile device
US20130006674A1 (en) 2011-06-29 2013-01-03 State Farm Insurance Systems and Methods Using a Mobile Device to Collect Data for Insurance Premiums
US9439240B1 (en) 2011-08-26 2016-09-06 Sprint Communications Company L.P. Mobile communication system identity pairing
US8726084B2 (en) 2011-10-14 2014-05-13 Honeywell International Inc. Methods and systems for distributed diagnostic reasoning
WO2013116665A1 (en) 2012-02-03 2013-08-08 Federal-Mogul Corporation Electrical diagnostic tool
US20130268156A1 (en) * 2012-04-07 2013-10-10 Robert Wilhelm Schumann Data Privacy Mechanism
US9398454B1 (en) 2012-04-24 2016-07-19 Sprint Communications Company L.P. In-car head unit wireless communication service subscription initialization
CA2805439C (en) 2012-05-22 2020-10-06 State Farm Mutual Automobile Insurance Company Systems and methods using a mobile device to collect data for insurance premiums
US8832649B2 (en) 2012-05-22 2014-09-09 Honeywell International Inc. Systems and methods for augmenting the functionality of a monitoring node without recompiling
US8832716B2 (en) 2012-08-10 2014-09-09 Honeywell International Inc. Systems and methods for limiting user customization of task workflow in a condition based health maintenance system
US9728228B2 (en) 2012-08-10 2017-08-08 Smartdrive Systems, Inc. Vehicle event playback apparatus and methods
US20140086242A1 (en) * 2012-09-05 2014-03-27 Drew Technologies, Inc. Device for transmitting signals from a vehicle
US9280859B2 (en) * 2012-10-08 2016-03-08 Toyota Motor Engineering & Manufacturing North America, Inc. Enhanced vehicle onboard diagnostic system and method
EP2725556A3 (en) 2012-10-24 2016-11-30 State Farm Insurance Systems and methods for controlling the collection of vehicle use data using a mobile device
US9026306B2 (en) 2012-10-30 2015-05-05 Wistron Neweb Corporation Data acquisition device for a vehicle
US20140149145A1 (en) 2012-11-29 2014-05-29 State Farm Insurance System and Method for Auto-Calibration and Auto-Correction of Primary and Secondary Motion for Telematics Applications via Wireless Mobile Devices
US9173238B1 (en) 2013-02-15 2015-10-27 Sprint Communications Company L.P. Dual path in-vehicle communication
US9208525B2 (en) 2013-03-10 2015-12-08 State Farm Mutual Automobile Insurance Company System and method for determining and monitoring auto insurance incentives
US20140278572A1 (en) * 2013-03-15 2014-09-18 State Farm Mutual Automobile Insurance Company System and method for routing a vehicle damaged in a crash
US11080734B2 (en) 2013-03-15 2021-08-03 Cdk Global, Llc Pricing system for identifying prices for vehicles offered by vehicle dealerships and other entities
US9996885B1 (en) 2013-03-15 2018-06-12 State Farm Mutual Automobile Insurance Company System and method for facilitating vehicle insurance services
US9858622B1 (en) 2013-03-15 2018-01-02 State Farm Mutual Automobile Insurance Company System and method for facilitating vehicle insurance services
US9508200B1 (en) 2013-03-15 2016-11-29 State Farm Mutual Automobile Insurance Company System and method for using a specialty vehicle data identifier to facilitate treatment of a vehicle damaged in a crash
GB201309716D0 (en) 2013-05-31 2013-07-17 Tom Tom Dev Germany Gmbh Wireless communication devices
GB2515024A (en) * 2013-06-10 2014-12-17 Wunelli Ltd Driving behaviour monitoring systems
US10489132B1 (en) * 2013-09-23 2019-11-26 Sprint Communications Company L.P. Authenticating mobile device for on board diagnostic system access
US9501878B2 (en) 2013-10-16 2016-11-22 Smartdrive Systems, Inc. Vehicle event playback apparatus and methods
US9892567B2 (en) 2013-10-18 2018-02-13 State Farm Mutual Automobile Insurance Company Vehicle sensor collection of other vehicle information
US8954226B1 (en) 2013-10-18 2015-02-10 State Farm Mutual Automobile Insurance Company Systems and methods for visualizing an accident involving a vehicle
US9262787B2 (en) * 2013-10-18 2016-02-16 State Farm Mutual Automobile Insurance Company Assessing risk using vehicle environment information
US9361650B2 (en) 2013-10-18 2016-06-07 State Farm Mutual Automobile Insurance Company Synchronization of vehicle sensor information
US10127742B2 (en) 2013-11-04 2018-11-13 Seibert Williams Glass, LLC Portable device and method for querying a vehicle network
US9417078B1 (en) 2015-05-15 2016-08-16 Seibert Williams Glass, LLC Portable device and method for querying a vehicle network
US9610955B2 (en) 2013-11-11 2017-04-04 Smartdrive Systems, Inc. Vehicle fuel consumption monitor and feedback systems
US9401056B2 (en) 2013-11-19 2016-07-26 At&T Intellectual Property I, L.P. Vehicular simulation
US9805521B1 (en) 2013-12-03 2017-10-31 United Parcel Service Of America, Inc. Systems and methods for assessing turns made by a vehicle
US8892310B1 (en) 2014-02-21 2014-11-18 Smartdrive Systems, Inc. System and method to detect execution of driving maneuvers
US10656280B2 (en) 2014-05-13 2020-05-19 Key Control Holding, Inc. Vehicle monitoring systems and methods
US10319039B1 (en) 2014-05-20 2019-06-11 State Farm Mutual Automobile Insurance Company Accident fault determination for autonomous vehicles
US10373259B1 (en) 2014-05-20 2019-08-06 State Farm Mutual Automobile Insurance Company Fully autonomous vehicle insurance pricing
US10599155B1 (en) 2014-05-20 2020-03-24 State Farm Mutual Automobile Insurance Company Autonomous vehicle operation feature monitoring and evaluation of effectiveness
US9972054B1 (en) 2014-05-20 2018-05-15 State Farm Mutual Automobile Insurance Company Accident fault determination for autonomous vehicles
US10185997B1 (en) 2014-05-20 2019-01-22 State Farm Mutual Automobile Insurance Company Accident fault determination for autonomous vehicles
US10185999B1 (en) 2014-05-20 2019-01-22 State Farm Mutual Automobile Insurance Company Autonomous feature use monitoring and telematics
US11669090B2 (en) 2014-05-20 2023-06-06 State Farm Mutual Automobile Insurance Company Autonomous vehicle operation feature monitoring and evaluation of effectiveness
US9252951B1 (en) 2014-06-13 2016-02-02 Sprint Communications Company L.P. Vehicle key function control from a mobile phone based on radio frequency link from phone to vehicle
US10475127B1 (en) 2014-07-21 2019-11-12 State Farm Mutual Automobile Insurance Company Methods of providing insurance savings based upon telematics and insurance incentives
IL234130A (en) * 2014-08-14 2017-11-30 Orpak Systems Ltd Device for reading vehicular data
GB201414566D0 (en) * 2014-08-15 2014-10-01 Tom Tom Int Bv Engine State Detection Device
US9412208B2 (en) * 2014-10-09 2016-08-09 Wrap Media, LLC Generating and delivering a wrap package of cards including custom content and/or services in response to a vehicle diagnostic system triggered event
US9424608B2 (en) 2014-10-09 2016-08-23 Wrap Media, LLC Generating and delivering a wrap package of cards including custom content and/or services in response to a vehicle diagnostic system triggered event
US9460228B2 (en) 2014-10-09 2016-10-04 Wrap Media, LLC Generating and delivering a wrap package of cards including custom content and/or services in response to a triggered event
US20160124924A1 (en) * 2014-10-09 2016-05-05 Wrap Media, LLC Displaying a wrap package of cards within an overlay window embedded in an application or web page
US9663127B2 (en) 2014-10-28 2017-05-30 Smartdrive Systems, Inc. Rail vehicle event detection and recording system
US9591482B1 (en) 2014-10-31 2017-03-07 Sprint Communications Company L.P. Method for authenticating driver for registration of in-vehicle telematics unit
US10915965B1 (en) 2014-11-13 2021-02-09 State Farm Mutual Automobile Insurance Company Autonomous vehicle insurance based upon usage
US11069257B2 (en) 2014-11-13 2021-07-20 Smartdrive Systems, Inc. System and method for detecting a vehicle event and generating review criteria
US9679420B2 (en) 2015-04-01 2017-06-13 Smartdrive Systems, Inc. Vehicle event recording system and method
US9649999B1 (en) 2015-04-28 2017-05-16 Sprint Communications Company L.P. Vehicle remote operations control
US9444892B1 (en) 2015-05-05 2016-09-13 Sprint Communications Company L.P. Network event management support for vehicle wireless communication
US10309788B2 (en) 2015-05-11 2019-06-04 United Parcel Service Of America, Inc. Determining street segment headings
USD771573S1 (en) * 2015-06-17 2016-11-15 Phahol Lowchareonkul Diagnostic port plug
GB201511602D0 (en) * 2015-06-24 2015-08-19 Tomtom Telematics Bv Wireless communication device
US20160378632A1 (en) * 2015-06-26 2016-12-29 Intel Corporation Port selection at a computing device
US9604651B1 (en) 2015-08-05 2017-03-28 Sprint Communications Company L.P. Vehicle telematics unit communication authorization and authentication and communication service provisioning
US20210272207A1 (en) 2015-08-28 2021-09-02 State Farm Mutual Automobile Insurance Company Vehicular driver profiles and discounts
CN105159346A (en) * 2015-08-28 2015-12-16 西安大唐电信有限公司 OBD vehicle-mounted terminal intelligent diagnostic device and diagnostic method thereof
US11119477B1 (en) 2016-01-22 2021-09-14 State Farm Mutual Automobile Insurance Company Anomalous condition detection and response for autonomous vehicles
US10395332B1 (en) 2016-01-22 2019-08-27 State Farm Mutual Automobile Insurance Company Coordinated autonomous vehicle automatic area scanning
US11441916B1 (en) 2016-01-22 2022-09-13 State Farm Mutual Automobile Insurance Company Autonomous vehicle trip routing
US10134278B1 (en) 2016-01-22 2018-11-20 State Farm Mutual Automobile Insurance Company Autonomous vehicle application
US11719545B2 (en) 2016-01-22 2023-08-08 Hyundai Motor Company Autonomous vehicle component damage and salvage assessment
US11242051B1 (en) 2016-01-22 2022-02-08 State Farm Mutual Automobile Insurance Company Autonomous vehicle action communications
US10324463B1 (en) 2016-01-22 2019-06-18 State Farm Mutual Automobile Insurance Company Autonomous vehicle operation adjustment based upon route
US9940834B1 (en) 2016-01-22 2018-04-10 State Farm Mutual Automobile Insurance Company Autonomous vehicle application
US10853769B2 (en) * 2016-04-21 2020-12-01 Cdk Global Llc Scheduling an automobile service appointment in a dealer service bay based on diagnostic trouble codes and service bay attributes
US10867285B2 (en) 2016-04-21 2020-12-15 Cdk Global, Llc Automatic automobile repair service scheduling based on diagnostic trouble codes and service center attributes
WO2017202947A2 (en) 2016-05-25 2017-11-30 Phoenix Ip Bv I.O. Method and system for determining the fuel consumptions actually resulting from the everyday operation of road vehicles, energy inputs and emissions
GB2551511B (en) * 2016-06-20 2019-06-19 Trakm8 Ltd Detection of tailgating situations
ITUA20164800A1 (en) * 2016-06-30 2017-12-30 Octo Telematics Spa Procedure for estimating the duration of a vehicle journey based on the determination of the vehicle status.
US10394871B2 (en) 2016-10-18 2019-08-27 Hartford Fire Insurance Company System to predict future performance characteristic for an electronic record
US11037177B1 (en) 2016-10-28 2021-06-15 State Farm Mutual Automobile Insurance Company Vehicle component identification using driver profiles
US11501351B2 (en) 2018-03-21 2022-11-15 Cdk Global, Llc Servers, systems, and methods for single sign-on of an automotive commerce exchange
US11190608B2 (en) 2018-03-21 2021-11-30 Cdk Global Llc Systems and methods for an automotive commerce exchange
DE102018130759A1 (en) * 2018-12-04 2020-06-04 Bayerische Motoren Werke Aktiengesellschaft Process for reproducing an error occurring while a vehicle is in motion
US11574510B2 (en) 2020-03-30 2023-02-07 Innova Electronics Corporation Multi-functional automotive diagnostic tablet with interchangeable function-specific cartridges
US11651628B2 (en) 2020-04-20 2023-05-16 Innova Electronics Corporation Router for vehicle diagnostic system
USD951948S1 (en) * 2020-09-04 2022-05-17 Shenzhen Chebotong Technology Co., Ltd Car data scanner
USD951951S1 (en) * 2020-09-04 2022-05-17 Shenzhen Chebotong Technology Co., Ltd Car data scanner
USD951950S1 (en) * 2020-09-04 2022-05-17 Shenzhen Chebotong Technology Co., Ltd Car data scanner
US11080105B1 (en) 2020-11-18 2021-08-03 Cdk Global, Llc Systems, methods, and apparatuses for routing API calls
US11514021B2 (en) 2021-01-22 2022-11-29 Cdk Global, Llc Systems, methods, and apparatuses for scanning a legacy database
US11803535B2 (en) 2021-05-24 2023-10-31 Cdk Global, Llc Systems, methods, and apparatuses for simultaneously running parallel databases
WO2023123278A1 (en) * 2021-12-30 2023-07-06 深圳市元征科技股份有限公司 Vehicle diagnosis method, diagnosis connector and diagnosis device

Citations (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4939652A (en) * 1988-03-14 1990-07-03 Centrodyne Inc. Trip recorder
US5278759A (en) * 1991-05-07 1994-01-11 Chrysler Corporation System and method for reprogramming vehicle computers
US5459660A (en) * 1993-12-22 1995-10-17 Chrysler Corporation Circuit and method for interfacing with vehicle computer
US5797134A (en) * 1996-01-29 1998-08-18 Progressive Casualty Insurance Company Motor vehicle monitoring system for determining a cost of insurance
US5862500A (en) * 1996-04-16 1999-01-19 Tera Tech Incorporated Apparatus and method for recording motor vehicle travel information
US5936315A (en) * 1995-04-13 1999-08-10 Vdo Adolf Schindling Ag Driving data recording device for motor vehicle mounted directly on or in the drive gear housing shell
US6073063A (en) * 1997-02-06 2000-06-06 Ford Global Technologies, Inc. Automotive data recording device
US6141609A (en) * 1993-11-08 2000-10-31 Mannesmann Aktiengesellschaft Device for recording information on a vehicle's itinerary
US6226577B1 (en) * 1999-07-08 2001-05-01 Hyundai Motor Company Method for searching trip log of vehicle
US6263268B1 (en) * 1997-08-26 2001-07-17 Transcontech Corporation System and method for providing mobile automotive telemetry
US20020016655A1 (en) * 2000-08-01 2002-02-07 Joao Raymond Anthony Apparatus and method for processing and/or for providing vehicle information and/or vehicle maintenance information
US6366207B1 (en) * 2000-02-04 2002-04-02 Michael Murphy Device for modifying vehicle operator driving behavior
US6611740B2 (en) * 2001-03-14 2003-08-26 Networkcar Internet-based vehicle-diagnostic system
US6629029B1 (en) * 2000-03-28 2003-09-30 Jacqueline A Giles Multi-purpose plug-in monitor for vehicles
US6807469B2 (en) * 2001-06-15 2004-10-19 Carcheckup, Llc Auto diagnostic method and device
US6810362B2 (en) * 2000-03-31 2004-10-26 Hitachi Construction Machinery Co., Ltd. Construction machine managing method and system, and arithmetic processing device
US20040217852A1 (en) * 2000-04-24 2004-11-04 Kolls H. Brock Method for characterizing a vehicle's fuel efficiency
US6819986B2 (en) * 2001-08-10 2004-11-16 Tellsyn Co., Ltd System and method for collecting vehicle data and diagnosing the vehicle, and method for automatically setting the vehicle convenience apparatus using smartcard
US6850823B2 (en) * 2001-12-08 2005-02-01 Electronics And Telecommunications Research Institute System and method for executing diagnosis of vehicle performance

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE3839221A1 (en) * 1988-08-01 1990-02-08 Morche Dirk W Dipl Ing Travel data memory

Patent Citations (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4939652A (en) * 1988-03-14 1990-07-03 Centrodyne Inc. Trip recorder
US5278759A (en) * 1991-05-07 1994-01-11 Chrysler Corporation System and method for reprogramming vehicle computers
US6141609A (en) * 1993-11-08 2000-10-31 Mannesmann Aktiengesellschaft Device for recording information on a vehicle's itinerary
US5459660A (en) * 1993-12-22 1995-10-17 Chrysler Corporation Circuit and method for interfacing with vehicle computer
US5936315A (en) * 1995-04-13 1999-08-10 Vdo Adolf Schindling Ag Driving data recording device for motor vehicle mounted directly on or in the drive gear housing shell
US5797134A (en) * 1996-01-29 1998-08-18 Progressive Casualty Insurance Company Motor vehicle monitoring system for determining a cost of insurance
US6064970A (en) * 1996-01-29 2000-05-16 Progressive Casualty Insurance Company Motor vehicle monitoring system for determining a cost of insurance
US5862500A (en) * 1996-04-16 1999-01-19 Tera Tech Incorporated Apparatus and method for recording motor vehicle travel information
US6073063A (en) * 1997-02-06 2000-06-06 Ford Global Technologies, Inc. Automotive data recording device
US6263268B1 (en) * 1997-08-26 2001-07-17 Transcontech Corporation System and method for providing mobile automotive telemetry
US6226577B1 (en) * 1999-07-08 2001-05-01 Hyundai Motor Company Method for searching trip log of vehicle
US6366207B1 (en) * 2000-02-04 2002-04-02 Michael Murphy Device for modifying vehicle operator driving behavior
US6629029B1 (en) * 2000-03-28 2003-09-30 Jacqueline A Giles Multi-purpose plug-in monitor for vehicles
US6810362B2 (en) * 2000-03-31 2004-10-26 Hitachi Construction Machinery Co., Ltd. Construction machine managing method and system, and arithmetic processing device
US20040217852A1 (en) * 2000-04-24 2004-11-04 Kolls H. Brock Method for characterizing a vehicle's fuel efficiency
US20020016655A1 (en) * 2000-08-01 2002-02-07 Joao Raymond Anthony Apparatus and method for processing and/or for providing vehicle information and/or vehicle maintenance information
US6611740B2 (en) * 2001-03-14 2003-08-26 Networkcar Internet-based vehicle-diagnostic system
US6807469B2 (en) * 2001-06-15 2004-10-19 Carcheckup, Llc Auto diagnostic method and device
US6819986B2 (en) * 2001-08-10 2004-11-16 Tellsyn Co., Ltd System and method for collecting vehicle data and diagnosing the vehicle, and method for automatically setting the vehicle convenience apparatus using smartcard
US6850823B2 (en) * 2001-12-08 2005-02-01 Electronics And Telecommunications Research Institute System and method for executing diagnosis of vehicle performance

Cited By (150)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9754424B2 (en) 1996-01-29 2017-09-05 Progressive Casualty Insurance Company Vehicle monitoring system
US8311858B2 (en) 1996-01-29 2012-11-13 Progressive Casualty Insurance Company Vehicle monitoring system
US8595034B2 (en) 1996-01-29 2013-11-26 Progressive Casualty Insurance Company Monitoring system for determining and communicating a cost of insurance
US8090598B2 (en) 1996-01-29 2012-01-03 Progressive Casualty Insurance Company Monitoring system for determining and communicating a cost of insurance
US8140358B1 (en) 1996-01-29 2012-03-20 Progressive Casualty Insurance Company Vehicle monitoring system
US8892451B2 (en) 1996-01-29 2014-11-18 Progressive Casualty Insurance Company Vehicle monitoring system
US20040153362A1 (en) * 1996-01-29 2004-08-05 Progressive Casualty Insurance Company Monitoring system for determining and communicating a cost of insurance
US8958998B2 (en) 1997-11-03 2015-02-17 Midtronics, Inc. Electronic battery tester with network communication
US20110208454A1 (en) * 2000-03-27 2011-08-25 Bertness Kevin I Scan tool for electronic battery tester
US8872516B2 (en) 2000-03-27 2014-10-28 Midtronics, Inc. Electronic battery tester mounted in a vehicle
US7519455B2 (en) * 2002-06-10 2009-04-14 Robert Bosch Gmbh Method and device for a vehicle-related telematics service
US20060235580A1 (en) * 2002-06-10 2006-10-19 Cornelia Weiss Method and device for a vehicle-related telematics service
US7167787B2 (en) * 2003-03-28 2007-01-23 Dieter Bastian Method for controlling the speed of a motor vehicle in accordance with risk and system for carrying out the method
US20060052929A1 (en) * 2003-03-28 2006-03-09 Dieter Bastian Method for controlling the speed of a motor vehicle in accordance with risk and system for carrying out the method
US9255955B2 (en) 2003-09-05 2016-02-09 Midtronics, Inc. Method and apparatus for measuring a parameter of a vehicle electrical system
US9018958B2 (en) 2003-09-05 2015-04-28 Midtronics, Inc. Method and apparatus for measuring a parameter of a vehicle electrical system
US7302371B2 (en) * 2003-10-08 2007-11-27 General Motors Corporation Captured test fleet
US20060106584A1 (en) * 2003-10-08 2006-05-18 Oesterling Christopher L Captured test fleet
US8010249B2 (en) 2004-08-19 2011-08-30 Spx Corporation Vehicle diagnostic device
US7885739B2 (en) * 2004-08-19 2011-02-08 Spx Corporation Open-ended vehicle diagnostic device interface
US20110015822A1 (en) * 2004-08-19 2011-01-20 Troy Liebl Vehicle Diagnostic Device
US20060041347A1 (en) * 2004-08-19 2006-02-23 Spx Corporation Open-ended vehicle diagnostic device interface
US9496720B2 (en) 2004-08-20 2016-11-15 Midtronics, Inc. System for automatically gathering battery information
US8963550B2 (en) 2004-08-20 2015-02-24 Midtronics, Inc. System for automatically gathering battery information
US20070198147A1 (en) * 2005-08-19 2007-08-23 Keith William J On-board diagnostic system including automatic communications bus disconnect
US20100010705A1 (en) * 2005-10-20 2010-01-14 Airmax Group Plc Methods and apparatus for monitoring vehicle data
US20070156311A1 (en) * 2005-12-29 2007-07-05 Elcock Albert F Communication of automotive diagnostic data
US20080252487A1 (en) * 2006-05-22 2008-10-16 Mcclellan Scott System and method for monitoring and updating speed-by-street data
US8630768B2 (en) 2006-05-22 2014-01-14 Inthinc Technology Solutions, Inc. System and method for monitoring vehicle parameters and driver behavior
US7859392B2 (en) 2006-05-22 2010-12-28 Iwi, Inc. System and method for monitoring and updating speed-by-street data
US8890717B2 (en) 2006-05-22 2014-11-18 Inthinc Technology Solutions, Inc. System and method for monitoring and updating speed-by-street data
US9847021B2 (en) 2006-05-22 2017-12-19 Inthinc LLC System and method for monitoring and updating speed-by-street data
US9067565B2 (en) 2006-05-22 2015-06-30 Inthinc Technology Solutions, Inc. System and method for evaluating driver behavior
US20080258890A1 (en) * 2006-05-22 2008-10-23 Todd Follmer System and Method for Remotely Deactivating a Vehicle
US10522033B2 (en) 2006-05-22 2019-12-31 Inthinc LLC Vehicle monitoring devices and methods for managing man down signals
US20080016504A1 (en) * 2006-07-14 2008-01-17 Wesley Homer Cheng Dynamically programmable electronic data collection system combining declarative programming and native coding
US20080016207A1 (en) * 2006-07-14 2008-01-17 Wesley Homer Cheng Electronic driver log application with bi-directional messaging to multiple backend systems
US20080082221A1 (en) * 2006-07-14 2008-04-03 David Nagy System for monitoring, controlling, and reporting vehicle operation through onboard diagnostic port
US20080015748A1 (en) * 2006-07-14 2008-01-17 David Nagy System for monitoring, controlling, and reporting vehicle operation through onboard diagnostic port
US20080221776A1 (en) * 2006-10-02 2008-09-11 Mcclellan Scott System and Method for Reconfiguring an Electronic Control Unit of a Motor Vehicle to Optimize Fuel Economy
US7899610B2 (en) 2006-10-02 2011-03-01 Inthinc Technology Solutions, Inc. System and method for reconfiguring an electronic control unit of a motor vehicle to optimize fuel economy
US20080255718A1 (en) * 2007-04-10 2008-10-16 Maurice Tuff Vehicle monitor
US8180522B2 (en) 2007-04-10 2012-05-15 Maurice Tuff Vehicle monitor
US7853375B2 (en) 2007-04-10 2010-12-14 Maurice Tuff Vehicle monitor
US20090259361A1 (en) * 2007-04-10 2009-10-15 Maurice Tuff Vehicle monitor
US8825277B2 (en) 2007-06-05 2014-09-02 Inthinc Technology Solutions, Inc. System and method for the collection, correlation and use of vehicle collision data
US20080306996A1 (en) * 2007-06-05 2008-12-11 Mcclellan Scott System and Method for the Collection, Correlation and Use of Vehicle Collision Data
US8666590B2 (en) 2007-06-22 2014-03-04 Inthinc Technology Solutions, Inc. System and method for naming, filtering, and recall of remotely monitored event data
US9129460B2 (en) 2007-06-25 2015-09-08 Inthinc Technology Solutions, Inc. System and method for monitoring and improving driver behavior
US7999670B2 (en) 2007-07-02 2011-08-16 Inthinc Technology Solutions, Inc. System and method for defining areas of interest and modifying asset monitoring in relation thereto
US20110015815A1 (en) * 2007-07-17 2011-01-20 Bertness Kevin I Battery tester for electric vehicle
US8818618B2 (en) 2007-07-17 2014-08-26 Inthinc Technology Solutions, Inc. System and method for providing a user interface for vehicle monitoring system users and insurers
US9274157B2 (en) * 2007-07-17 2016-03-01 Midtronics, Inc. Battery tester for electric vehicle
US8577703B2 (en) 2007-07-17 2013-11-05 Inthinc Technology Solutions, Inc. System and method for categorizing driving behavior using driver mentoring and/or monitoring equipment to determine an underwriting risk
US9335362B2 (en) 2007-07-17 2016-05-10 Midtronics, Inc. Battery tester for electric vehicle
US20160171799A1 (en) * 2007-07-17 2016-06-16 Midtronics, Inc. Battery tester for electric vehicle
US20160253852A1 (en) * 2007-07-17 2016-09-01 Midtronics, Inc. Battery tester for electric vehicle
US9117246B2 (en) 2007-07-17 2015-08-25 Inthinc Technology Solutions, Inc. System and method for providing a user interface for vehicle mentoring system users and insurers
US8447464B2 (en) 2007-08-02 2013-05-21 North-Line Canada Ltd. System and method for interfacing between an on-board diagnostic output and a distance measuring instrument input
US7739562B2 (en) * 2007-08-17 2010-06-15 International Business Machines Corporation Programmable diagnostic memory module
US7730369B2 (en) 2007-08-17 2010-06-01 International Business Machines Corporation Method for performing memory diagnostics using a programmable diagnostic memory module
US20090049339A1 (en) * 2007-08-17 2009-02-19 Moises Cases Programmable Diagnostic Memory Module
US20090049341A1 (en) * 2007-08-17 2009-02-19 Moises Cases Method for Performing Memory Diagnostics Using a Programmable Diagnostic Memory Module
US20090051510A1 (en) * 2007-08-21 2009-02-26 Todd Follmer System and Method for Detecting and Reporting Vehicle Damage
US7876205B2 (en) 2007-10-02 2011-01-25 Inthinc Technology Solutions, Inc. System and method for detecting use of a wireless device in a moving vehicle
US8890673B2 (en) 2007-10-02 2014-11-18 Inthinc Technology Solutions, Inc. System and method for detecting use of a wireless device in a moving vehicle
US8340855B2 (en) 2008-04-22 2012-12-25 Spx Corporation USB isolation for vehicle communication interface
WO2010011840A1 (en) * 2008-07-24 2010-01-28 Hamilton Performance Electronics, Llc System and method for emulating vehicle ignition-switched power
US20100023198A1 (en) * 2008-07-24 2010-01-28 Brennan Todd Hamilton System and method for emulating vehicle ignition-switched power
US8688180B2 (en) 2008-08-06 2014-04-01 Inthinc Technology Solutions, Inc. System and method for detecting use of a wireless device while driving
US8963702B2 (en) 2009-02-13 2015-02-24 Inthinc Technology Solutions, Inc. System and method for viewing and correcting data in a street mapping database
US9843926B2 (en) * 2010-02-22 2017-12-12 Continental Automotive Gmbh System and method for preventing an attack on a networked vehicle
US20130104186A1 (en) * 2010-02-22 2013-04-25 Continental Automotive Gmbh System and method for preventing an attack on a networked vehicle
US9588185B2 (en) 2010-02-25 2017-03-07 Keith S. Champlin Method and apparatus for detecting cell deterioration in an electrochemical cell or battery
US20110218747A1 (en) * 2010-03-03 2011-09-08 Bertness Kevin I Monitor for front terminal batteries
US9425487B2 (en) 2010-03-03 2016-08-23 Midtronics, Inc. Monitor for front terminal batteries
US9229062B2 (en) 2010-05-27 2016-01-05 Midtronics, Inc. Electronic storage battery diagnostic system
US11650259B2 (en) 2010-06-03 2023-05-16 Midtronics, Inc. Battery pack maintenance for electric vehicle
US11740294B2 (en) 2010-06-03 2023-08-29 Midtronics, Inc. High use battery pack maintenance
US9419311B2 (en) 2010-06-18 2016-08-16 Midtronics, Inc. Battery maintenance device with thermal buffer
US8747148B2 (en) 2010-08-03 2014-06-10 Bosch Automotive Service Solutions Llc Diagnostic tool with recessed connector
US20120035800A1 (en) * 2010-08-03 2012-02-09 Spx Corporation Vehicle Diagnostic, Communication and Signal Delivery System
US9201120B2 (en) 2010-08-12 2015-12-01 Midtronics, Inc. Electronic battery tester for testing storage battery
US9286265B2 (en) * 2010-10-28 2016-03-15 Innovation Gap Inc. Device and method for managing an electronic control unit of a vehicle
US8838362B2 (en) * 2011-02-03 2014-09-16 Raytheon Company Low-drain, self-contained monitoring device
US20120203441A1 (en) * 2011-02-03 2012-08-09 Raytheon Company Low-drain, self-contained monitoring device
US8924240B2 (en) 2011-05-25 2014-12-30 Shailendra Depura System for monitoring vehicle and operator behavior
US10173544B2 (en) * 2011-05-26 2019-01-08 Sierra Smart Systems, Llc Electric vehicle fleet charging system
US9505318B2 (en) * 2011-05-26 2016-11-29 Sierra Smart Systems, Llc Electric vehicle fleet charging system
US20120330494A1 (en) * 2011-05-26 2012-12-27 Hendrix Walter M Electric vehicle fleet charging system
US10255575B2 (en) * 2011-06-30 2019-04-09 Xrs Corporation Fleet vehicle management systems and methods
US20140122187A1 (en) * 2011-06-30 2014-05-01 Xrs Corporation Fleet Vehicle Management Systems and Methods
US11367033B2 (en) * 2011-06-30 2022-06-21 Xrs Corporation Fleet vehicle management systems and methods
US20140058802A1 (en) * 2011-06-30 2014-02-27 Xrs Corporation Fleet vehicle management systems and methods
US10134000B2 (en) * 2011-06-30 2018-11-20 Xrs Corporation Fleet vehicle management systems and methods
US10429449B2 (en) 2011-11-10 2019-10-01 Midtronics, Inc. Battery pack tester
US11030702B1 (en) 2012-02-02 2021-06-08 Progressive Casualty Insurance Company Mobile insurance platform system
US11325479B2 (en) 2012-06-28 2022-05-10 Midtronics, Inc. Hybrid and electric vehicle battery maintenance device
US11926224B2 (en) 2012-06-28 2024-03-12 Midtronics, Inc. Hybrid and electric vehicle battery pack maintenance device
US11548404B2 (en) 2012-06-28 2023-01-10 Midtronics, Inc. Hybrid and electric vehicle battery pack maintenance device
US10046649B2 (en) 2012-06-28 2018-08-14 Midtronics, Inc. Hybrid and electric vehicle battery pack maintenance device
US9851411B2 (en) 2012-06-28 2017-12-26 Keith S. Champlin Suppressing HF cable oscillations during dynamic measurements of cells and batteries
US20140074353A1 (en) * 2012-09-12 2014-03-13 Anydata Corporation Vehicle telematics control via ignition detection
US9129336B2 (en) 2012-12-04 2015-09-08 I.D. Systems, Inc. Remote vehicle rental systems and methods
US9818151B2 (en) 2012-12-04 2017-11-14 I.D. Systems, Inc. Remote vehicle rental systems and methods
WO2014089171A1 (en) * 2012-12-04 2014-06-12 I.D. Systems, Inc. Remote vehicle rental systems and methods
US9244100B2 (en) 2013-03-15 2016-01-26 Midtronics, Inc. Current clamp with jaw closure detection
US9312575B2 (en) 2013-05-16 2016-04-12 Midtronics, Inc. Battery testing system and method
US9172477B2 (en) 2013-10-30 2015-10-27 Inthinc Technology Solutions, Inc. Wireless device detection using multiple antennas separated by an RF shield
US10843574B2 (en) 2013-12-12 2020-11-24 Midtronics, Inc. Calibration and programming of in-vehicle battery sensors
US9923289B2 (en) 2014-01-16 2018-03-20 Midtronics, Inc. Battery clamp with endoskeleton design
US9285223B1 (en) 2014-05-15 2016-03-15 State Farm Mutual Automobile Insurance Company System and method for identifying heading of a moving vehicle using accelerometer data
US10832346B1 (en) 2014-05-15 2020-11-10 State Farm Mutual Automobile Insurance Company System and method for identifying primary and secondary movement using spectral domain analysis
US9786103B2 (en) 2014-05-15 2017-10-10 State Farm Mutual Automobile Insurance Company System and method for determining driving patterns using telematics data
US9360322B2 (en) 2014-05-15 2016-06-07 State Farm Mutual Automobile Insurance Company System and method for separating ambient gravitational acceleration from a moving three-axis accelerometer data
US10223845B1 (en) 2014-05-15 2019-03-05 State Farm Mutual Automobile Insurance Company System and method for separating ambient gravitational acceleration from a moving three-axis accelerometer data
US9726497B1 (en) 2014-05-15 2017-08-08 State Farm Mutual Automobile Insurance Company System and method for identifying heading of a moving vehicle using accelerometer data
US10997666B1 (en) 2014-05-15 2021-05-04 State Farm Mutual Automobile Insurance Company System and method for identifying idling times of a vehicle using accelerometer data
US10032320B1 (en) 2014-05-15 2018-07-24 State Farm Mutual Automobile Insurance Company System and method for determining driving patterns using telematics data
US10304138B2 (en) 2014-05-15 2019-05-28 State Farm Mutual Automobile Insurance Company System and method for identifying primary and secondary movement using spectral domain analysis
US10309785B1 (en) 2014-05-15 2019-06-04 State Farm Mutual Automobile Insurance Company System and method for identifying heading of a moving vehicle using accelerometer data
US9127946B1 (en) 2014-05-15 2015-09-08 State Farm Mutual Automobile Insurance Company System and method for identifying heading of a moving vehicle using accelerometer data
US10319159B1 (en) 2014-05-15 2019-06-11 State Farm Mutual Automobile Insurance Company System and method for determining driving patterns using telematics data
US10019762B2 (en) 2014-05-15 2018-07-10 State Farm Mutual Automobile Insurance Company System and method for identifying idling times of a vehicle using accelerometer data
US9513128B1 (en) 2014-05-15 2016-12-06 State Farm Mutual Automobile Insurance Company System and method for identifying heading of a moving vehicle using accelerometer data
US11416946B1 (en) 2014-05-15 2022-08-16 State Farm Mutual Automobile Insurance Company System and method for identifying primary and secondary movement using spectral domain analysis
US10473555B2 (en) 2014-07-14 2019-11-12 Midtronics, Inc. Automotive maintenance system
US9988058B2 (en) * 2014-09-22 2018-06-05 Brian K. Phillips Method and system for automatically identifying a driver by creating a unique driver profile for a vehicle from driving habits
US9418491B2 (en) * 2014-09-22 2016-08-16 Brian K. Phillips Method and system for automatically identifying a driver by creating a unique driver profile for a vehicle from driving habits
US10493996B2 (en) 2014-09-22 2019-12-03 Future Technology Partners, Llc Method and system for impaired driving detection, monitoring and accident prevention with driving habits
US10300924B2 (en) 2014-09-22 2019-05-28 Brian K. Phillips Method and system for automatically identifying a driver by creating a unique driver profile for a vehicle from driving habits
US10065653B1 (en) * 2014-09-22 2018-09-04 Brian K. Phillips Method and system for automatically identifying a driver by creating a unique driver profile for a vehicle from driving habits
US11161519B2 (en) 2014-09-22 2021-11-02 Future Technology Partners, Llc Method and system for impaired driving detection, monitoring and accident prevention with driving habits
US10222397B2 (en) 2014-09-26 2019-03-05 Midtronics, Inc. Cable connector for electronic battery tester
US10317468B2 (en) 2015-01-26 2019-06-11 Midtronics, Inc. Alternator tester
US20180268626A1 (en) * 2015-03-06 2018-09-20 Sony Corporation Recording device, recording method, and computer program
US10825271B2 (en) * 2015-03-06 2020-11-03 Sony Corporation Recording device and recording method
US11823507B2 (en) 2015-03-06 2023-11-21 Sony Corporation Recording device, recording method, and computer program
US9966676B2 (en) 2015-09-28 2018-05-08 Midtronics, Inc. Kelvin connector adapter for storage battery
US10384688B2 (en) * 2015-12-15 2019-08-20 Greater Than Ab Method and system for assessing the trip performance of a driver
US20180345985A1 (en) * 2015-12-15 2018-12-06 Greater Than S.A. Method and system for assessing the trip performance of a driver
US10275951B2 (en) * 2016-06-16 2019-04-30 Hyundai Motor Company Communication control device, vehicle having the communication control device, and method for controlling the vehicle
US10608353B2 (en) 2016-06-28 2020-03-31 Midtronics, Inc. Battery clamp
US11054480B2 (en) 2016-10-25 2021-07-06 Midtronics, Inc. Electrical load for electronic battery tester and electronic battery tester including such electrical load
US11513160B2 (en) 2018-11-29 2022-11-29 Midtronics, Inc. Vehicle battery maintenance device
US11566972B2 (en) 2019-07-31 2023-01-31 Midtronics, Inc. Tire tread gauge using visual indicator
US11545839B2 (en) 2019-11-05 2023-01-03 Midtronics, Inc. System for charging a series of connected batteries
US11668779B2 (en) 2019-11-11 2023-06-06 Midtronics, Inc. Hybrid and electric vehicle battery pack maintenance device
US11474153B2 (en) 2019-11-12 2022-10-18 Midtronics, Inc. Battery pack maintenance system
US11486930B2 (en) 2020-01-23 2022-11-01 Midtronics, Inc. Electronic battery tester with battery clamp storage holsters

Also Published As

Publication number Publication date
WO2004040405A2 (en) 2004-05-13
AU2003282831A1 (en) 2004-05-25
CA2494350A1 (en) 2004-05-13
US20040083041A1 (en) 2004-04-29
WO2004040405A3 (en) 2004-06-03
US6832141B2 (en) 2004-12-14
CA2494350C (en) 2011-02-08
AU2003282831A8 (en) 2004-05-25

Similar Documents

Publication Publication Date Title
US6832141B2 (en) Module for monitoring vehicle operation through onboard diagnostic port
US5499182A (en) Vehicle driver performance monitoring system
US5313388A (en) Method and apparatus for diagnosing engine and/or vehicle system faults based on vehicle operating or drive symptoms
US4926331A (en) Truck operation monitoring system
US8954227B2 (en) User configurable scan tool
JP3758356B2 (en) Electronic control device for vehicle, electronic control unit and recording medium
US7987028B2 (en) Method and apparatus for reading and erasing diagnostic trouble codes from a vehicle
US7809482B2 (en) Diagnostic tool with advanced diagnostic capabilities
US6445985B1 (en) Motor vehicle data processing apparatus
US20060155439A1 (en) System and method for using a vehicle's key to collect vehicle data and diagnose mechanical problems, to store and compare security data to allow only authorized use of vehicles and a method to automatically set vehicle features usng the key
US8571750B2 (en) Diagnostic tool with advanced diagnostic capabilities
CA2518024C (en) User adaptive automated pre-trip inspection system
US20090216401A1 (en) Feedback loop on diagnostic procedure
US20090216584A1 (en) Repair diagnostics based on replacement parts inventory
US8027763B2 (en) OBD II readiness monitor tool apparatus and method
US20150081163A1 (en) Obd illuminator cable apparatus and method
KR200305901Y1 (en) System for collecting vehicle data and diagnosticating the vehicle using usb hard drive
US7424351B2 (en) Control unit and data transmitting method
US7129827B2 (en) Resettable motor vehicle maintenance interval monitor by operating time
KR20190096842A (en) Networking system for efficient management of vehicle using data mining
KR100240561B1 (en) Self-diagnosis system for a vehicle
US20180130267A1 (en) Onboard diagnostic system and method
JP3223230B2 (en) Fault diagnosis device
KR100561604B1 (en) Method of recording a running state of a vehicle and computer for controlling an engine
Menig et al. Transportation recorders on commercial vehicles

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION