Patent Grant
RE39619
(Not Applicable)
(Not Applicable)
The present invention relates generally to methods and systems for diagnosing a vehicle, and more particularly to displaying diagnostic fault codes generated by automobile computer systems.
Modern motor vehicles include a computer control system. The main purpose of the vehicle computer control system is to provide maximum engine performance with the least amount of air pollution and the best fuel efficiency possible. The computer control system consists of the on-board computer and related electronic control devices (sensors, switches, and actuators). The control devices may control various systems and/or subsystems within the vehicle. These electronic control devices send information to the on-board computer about such parameters as the temperature and density of the outside air, the speed of the engine, the amount of the fuel delivered, etc. At the same time, the on-board computer scans for any problems from its sensors. If a problem is detected, the on-board computer restores the problem as a numeric code, referred to as a diagnostic trouble code or fault code, in its memory for later retrieval. In this regard, the diagnostic trouble codes (DTCs) are codes that identify a particular problem area and are intended as a guide to the proper collective servicing of the vehicle.
In response to governmental regulations and industry practices, vehicle manufacturers have begun to standardize diagnostic trouble codes. For example, the current generation standard for communications protocol is referred to as OBD II. Beginning in 1996, all vehicles built for sale in the United States were required to be OBD II—compliant.
Hand-held or portable code readers, also referred to as diagnostic code readers or scan tools, have been utilized to trouble shoot false or problems or associated with these electronic control units. Such code readers are configured to electronically communicate with a vehicle's on-board computer for accessing stored diagnostic trouble codes. The more sophisticated code readers may be configured to determine a particular standard for communications protocol being implemented by the subject vehicle. The code reader interfaces with the vehicle's on-board computer via a connection point which is usually located under the instrument panel (dash), on the driver's side of most vehicles. OBD II—compliant vehicles are configured to have an on-board computer equipped to receive a 16 pin data link connector cable from the code reader.
The code reader typically has a display for indicating received diagnostic trouble codes. Some code readers include problem description data correlated to the diagnostic trouble codes stored in memory. Other code readers are used in connection with a booklet containing problem description data correlated to the diagnostic trouble codes.
From the perspective of vehicle owners, personal use of code readers may be advantageous. Vehicle owners may choose to effect the repair themselves, possibly at a substantial cost savings in comparison to having service providers or technicians perform the same repairs. Alternatively, even if the services of a service technician are utilized, with the advanced knowledge as to the nature and scope of the vehicle problem, a vehicle owner may be able to mitigate unwarranted services and costs. Moreover, a vehicle owner may avoid a service fee to the service technician for performing the very same task of retrieving the diagnostic trouble codes and correlating them to the problem description data.
Notwithstanding the above advantages of code readers, contemporary code readers have not typically optimized simplicity of design and display to enhance ease of use. In particular, contemporary code readers typically require a manual setup, in advance of operation. The manual setup requires a user to scroll through a variety of information, e.g., make and model information, to set the code reader to receive and process codes appropriately.
Additionally, contemporary code readers typically display informational categories that may not apply to the particular vehicle under test. As such, the display becomes unduly complex and confusing to many users.
Accordingly, there is a need to provide an automotive code reader that requires no manually driven setup, displays only informational categories relevant to the vehicle being tested, and arrays the displayed information in a single display.
These and other objects and advantages are achieved by means of the present invention, as described in more detail below.
A method of displaying automotive diagnostic information is disclosed comprising connecting a code reader to a vehicle computer and communicating monitor status information and trouble codes to the code reader. Only those monitor functions that are supported by the vehicle are illuminated on the code reader, along with their status. Trouble codes communicated from the vehicle are also displayed, along with trouble code descriptors. All display functions are operative independent of any manual input to identify the type of vehicle being tested.
Trouble code descriptors and selective illumination of supported monitor functions is implemented independent of any user input identifying the type of vehicle being tested.
All supported monitors are displayed in a single display.
In one embodiment all diagnostic display functions are displayed in a single display.
The features of the present invention will become more apparent upon reference to the drawings wherein:
Erase button 15 functions to erase diagnostic trouble codes (DTCs) and freeze frame data and resets monitor status. Scroll button 17 functions to scroll the display 13 to view diagnostic trouble codes when more than one DTC is present.
Link button 19 functions to link the code reader with the vehicle's powertrain control module (PCM) to retrieve any DTCs that are present in memory and to view readiness monitor status. Power button 21 operates to turn the code reader on and off.
Referring to
I/M monitor status display illustrates various monitors that correlate to monitors in the vehicle being tested. The monitors include a variety of functions, not all of which may be supported by a particular vehicle. In accordance with the present invention, only those monitored functions that are supported by the present vehicle are lit. Where a monitor is supported, but not operative to provide test data, an indication of such may be provided, e.g., by blinking the appropriate indicator. Where a monitor is supported, but determined to be inoperative in relation to prescribed parameters, an indication is also provided, e.g., by altering the substance or color of the appropriate display.
The vehicle icon 25 indicates whether or not the code reader is being properly powered to the vehicle's data link connector. The link icon 27 indicates whether or not the code reader is communicating (linked) with the vehicle's on-board computer. The computer icon 29 provides an indication as to whether or not the monitor is optionally connected to a computer link. The battery icon 31 indicates the status of the code reader internal battery.
The display 33 displays the DTC number for any diagnostic trouble code identified by the code reader. Each particular fault is assigned a code number that is specific to that fault.
The translator display 35 displays the fault code that corresponds to the DTC illustrated at display 33. As such, the translator display avoids the need for a user to separately refer to a list of trouble codes that may correspond to a particular DTC. As such, the code reader allows for more complete information within a single display, for the convenience of the user. The translator display is implemented by means of a look-up table within the code reader that operates to produce the trouble code descriptor (translation).
The pending display 37 indicates if the display DTC is a pending code. A code icon 39 identifies the code number sequence display area. The MIL icon 41 indicates the status of the malfunction indicator lamp (MIL). The MIL icon is visible only when a DTC has commanded the MIL to illuminate on the vehicle's dash.
The code reader assigns a sequence number to each DTC that is present in the PCMs memory, in ascending order, starting with 01. The code number sequence 43 indicates which DTC is being displayed, and how many such codes are in memory, e.g., displaying code number 2 of 6 stored codes.
As illustrated in
Different types of vehicles generate different types of signals. By analysis of the signals received by the code reader, e.g., the monitor signals being generated, the vehicle type can be determined. Where only certain monitors are supported, the display is operative to illuminate only the supported monitors, and not others. As such, the display of monitor functions is limited to those functions supported by the particular vehicle being tested.
Trouble codes communicated from the vehicle computer are also displayed in the code reader. The code reader further operates to correlate the trouble codes to a vehicle condition description, which is also displayed in the code reader.
As such, information is collected, processed and displayed in a form that minimizes the need for any supplemental source to identify the vehicle in question and the monitors supported by that vehicle. Additionally, the invention avoids the need for additional references to correlate the display trouble codes to particular vehicle conditions. Accordingly, the invention provides significant ease of use and convenience useful to practical operation.
As will be recognized by one of ordinary skill in the art, various changes and modifications may be made to the invention without departing from the broader scope of the invention, as described herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2960654 | Nelson | Nov 1960 | A |
| 3646438 | Staff | Feb 1972 | A |
| 4176315 | Sunnarborg | Nov 1979 | A |
| 4207611 | Gordon | Jun 1980 | A |
| 4404639 | McGuire et al. | Sep 1983 | A |
| 4859932 | Whitley | Aug 1989 | A |
| 4884033 | McConchie, Sr. | Nov 1989 | A |
| 5003478 | Kobayashi et al. | Mar 1991 | A |
| 5005129 | Abe et al. | Apr 1991 | A |
| 5107428 | Bethencourt et al. | Apr 1992 | A |
| 5157708 | Garthwaite et al. | Oct 1992 | A |
| 5214582 | Gray | May 1993 | A |
| 5247245 | Nelson | Sep 1993 | A |
| 5278508 | Bowman | Jan 1994 | A |
| 5285163 | Liotta | Feb 1994 | A |
| 5359290 | Cervas | Oct 1994 | A |
| 5394093 | Cervas | Feb 1995 | A |
| 5400018 | Scholl et al. | Mar 1995 | A |
| 5481906 | Nagayoshi et al. | Jan 1996 | A |
| 5491418 | Alfaro et al. | Feb 1996 | A |
| 5506772 | Kobozono et al. | Apr 1996 | A |
| 5541840 | Gurne et al. | Jul 1996 | A |
| 5657233 | Cherrington et al. | Aug 1997 | A |
| 5758300 | Abe | May 1998 | A |
| 5916286 | Seashore et al. | Jun 1999 | A |
| 6225898 | Kamiya et al. | May 2001 | B1 |
| 6263265 | Fera | Jul 2001 | B1 |
| 6263322 | Kirkvold et al. | Jul 2001 | B1 |
| 6295492 | Lang et al. | Sep 2001 | B1 |
| 6330499 | Chou et al. | Dec 2001 | B1 |
| 6389337 | Kolls | May 2002 | B1 |
| 6535802 | Kramer | Mar 2003 | B1 |
| 6687584 | Andreasen | Feb 2004 | B2 |
| 6807469 | Funkhouser et al. | Oct 2004 | B2 |
| 6925368 | Funkhouser et al. | Aug 2005 | B2 |
| 6947816 | Chen | Sep 2005 | B2 |
| 7069125 | Namaky et al. | Jun 2006 | B2 |
| 20010053983 | Reichwein et al. | Dec 2001 | A1 |
| 20020156692 | Squeglia et al. | Oct 2002 | A1 |
| 20020193925 | Funkhouser et al. | Dec 2002 | A1 |
| 20030060953 | Chen | Mar 2003 | A1 |
| 20060027650 | Andreasen et al. | Feb 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10036601 | Dec 2001 | US |
| Child | 11294887 | US |
