Data processing: vehicles – navigation – and relative location – Vehicle control – guidance – operation – or indication – Vehicle diagnosis or maintenance indication
Reexamination Certificate
2002-10-25
2004-12-14
Zanelli, Michael J. (Department: 3661)
Data processing: vehicles, navigation, and relative location
Vehicle control, guidance, operation, or indication
Vehicle diagnosis or maintenance indication
C701S033000, C340S439000
Reexamination Certificate
active
06832141
ABSTRACT:
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 c
Mohr Paul
Skeen Michael
Wacknov Joel
Davis Instruments
Hynes William Michael
Townsend and Townsend / and Crew LLP
Zanelli Michael J.
LandOfFree
Module for monitoring vehicle operation through onboard... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Module for monitoring vehicle operation through onboard..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Module for monitoring vehicle operation through onboard... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3292998