Patent Application
20060161390
The present invention relates generally to the field of electronic testing devices, and more specifically to “off-board tools,” such as inspection maintenance tools, scan tools, and code readers for retrieving information from vehicle diagnostic.
The Environmental Protection Agency (EPA) set forth guidelines for states to follow in designing and running vehicle inspection and maintenance (I/M) programs. The guidelines are designed to reduce pollutants in the air that are produced by vehicles having defective or improperly working emissions systems. The guidelines for automobile emissions testing programs set forth the minimum requirements to satisfy the Clean Air Act (CAA). Under the CAA, the states must periodically inspect vehicles that travel on the roadways. Included in the periodic inspection for newer vehicles is the checking of the on-board diagnostic system.
Vehicles emissions inspections programs have traditionally analyzed the vehicle exhaust under simulated driving conditions. One way to simulate driving conditions is by placing the vehicle on rollers and running the vehicle at various speeds. Placing the vehicle on rollers and running the vehicle at selected speeds is undesirable because it is inconvenient, time consuming, and potentially dangerous.
Another method of performing a vehicle emissions inspection is to analyze the data stored on the on-board diagnostic system that was gathered during actual driving conditions. All vehicles manufactured since 1996 are required to have an on-board vehicle diagnostic system. The on-board vehicle diagnostic system includes one or more computer modules that are used to control various components, such as the engine, transmission, anti-lock brake system etc. The on-board vehicle diagnostic systems monitor and store data indicative of emissions levels, such as, for example, data from the oxygen sensor, the catalytic converter, the EGR valve, etc., that are obtained during actual driving conditions over a period of time and during key “off” conditions. Once the vehicle has been driven for a sufficient period of time for the on-board diagnostic system to fully evaluate the emissions system, the on-board diagnostic system sets a status flag. The status flag, or readiness code, is used to verify that error codes have not been cleared immediately prior to having the vehicle inspected.
A typical I/M program for 1996 and later models includes a manual examination of the components and an electronic examination of the on-board diagnostic system. First, the inspector enters the vehicle identification number into a computer terminal, so that the vehicle identification number can be reported to the state along with the results of the emissions test. The vehicle identification number is either entered manually, or entered by scanning a bar code label that may be located on the vehicle door. After entering the VIN number, the vehicle is pulled forward and the inspector performs a visual check of the dashboard display, status indication, (or the malfunction indicator light “MIL”) and selected emissions control components. Finally, the inspector performs an inspection of the on-board vehicle diagnostic system. Typically, an “Off-Board Tool,” (OBT) such as a scan tool, code reader or similar hand-held instrument is used to extract data from the vehicle on-board diagnostic system in the form of Diagnostic Trouble Codes (DTCs), monitors, etc.
“Off-Board Tools,” such as, for example, scan tools, and code reader are testing devices that interface with vehicle diagnostic systems to access, display, and/or print vehicle diagnostic information. On-Board Diagnostics Version II Scan Tools are one commonly known type of scan tool and are governed by a number of standards, such as, for example, SAE J1978 Rev. APR 2002 and SAE J1979 Rev. APR 2002.
Optical scanners are known and include bar code scanners. Generally, there are two types of bar code scanners, less-expensive contact scanners, and more expensive non-contact scanners. The less-expensive contact scanners, also known as manual scanners, or one-pass scanners require close, or actual physical contact, between the scanner and the bar code. Manual scanners or one-pass scanners include, for example, light pen bar code readers. As the name implies, non-contact scanners do not require direct contact with the bar code. Non-contact scanners include, for example, scanners that use a CMOS camera sensor, and scanners that use lasers and osculating mirrors. The latter are often found in hand-held devices at checkout lines.
Typically, test centers that scan in VIN numbers utilize a scanner at one station and an OBT at a second station. Placing the vehicle at one location to enter the vehicle identification number and moving the vehicle to a second station to retrieve data from the vehicle diagnostic system increases the time and space required to perform an emissions test.
Exemplary embodiments of an improved OBT are provided. General concepts of the invention include an OBT combined with an optical scanner. In one embodiment, the OBT includes a housing that at least partially retains a processor, vehicle communication circuitry for linking to a vehicle diagnostic system, and an optical reader for optically obtaining additional information. Another exemplary embodiment includes an OBT used in conjunction with a barcode reader and/or a camera. In addition, a method of obtaining diagnostic data from the vehicle diagnostic system and optically obtaining information using an off-board device is provided.
In the accompanying drawings, which are incorporated in and constitute a part of this specification, embodiments of the invention are illustrated, which, together with a general description of the invention given above, and the detailed description given below, serve to example principles of this invention, wherein:
FIGS. 3 is a flowchart illustrating an exemplary methodology of obtaining optically data and electronically obtained data from a vehicle diagnostic system using an OBT having an optical scanner.
The following includes definitions of exemplary terms used throughout the disclosure. Both singular and plural forms of all terms fall within each meaning. Except where noted otherwise, capitalized and non-capitalized forms of all terms fall within each meaning:
“Circuit communication” as used herein indicates a communicative relationship between devices. Direct electrical, electromagnetic, optical connections and indirect electrical, electromagnetic, and optical connections are examples of circuit communication. Two devices are in circuit communication if a signal from one is designed to be received by the other, regardless of whether the signal is modified by some other device. For example, two devices separated by one or more of the following—amplifiers, filters, transformers, optoisolators, digital or analog buffers, analog integrators, other electronic circuitry, fiber optic transceivers, or even satellites—are in circuit communication if a signal from one is communicated to the other, even though the signal is modified by the intermediate device(s). As another example, an electromagnetic sensor is in circuit communication with a signal if it is designed to receive electromagnetic radiation from the signal. As a final example, two devices not directly connected to each other, but both capable of interfacing with a third device, e.g., a CPU, are in circuit communication. Also, as used herein, voltages and values representing digitized voltages are considered to be equivalent for the purposes of this application and thus the term “voltage” as used herein refers to either a signal, or a value in a processor representing a signal, or a value in a processor determined from a value representing a signal.
“Software”, as used herein includes, but is not limited to, one or more computer readable and/or executable instructions that cause a computer or other electronic device to perform functions, actions, and/or behave in a desired manner. The instructions may be embodied in various forms such as routines, algorithms, modules or programs including separate applications or code from dynamically linked libraries. Software may also be implemented in various forms such as a stand-alone program, a function call, a servlet, an applet, instructions stored in a memory, part of an operating system or other type of executable instructions. It will be appreciated by one of ordinary skill in the art that the form of software is dependent on, for example, requirements of a desired application, the environment it runs on, and/or the desires of a designer/programmer or the like.
“Logic” as used herein includes, but is not limited to hardware, firmware, software and/or combinations of each to perform a function(s) or an action(s). For example, based on a desired application or needs, logic may include a software controlled microprocessor, discrete logic such as an application specific integrated circuit (ASIC), or other programmed logic device. Logic may also be fully embodied as software.
Cable 122 includes a first connector 124, preferably a Data Link Connector (DLC), such as for example a J1692 connector, and a second connector 126. Connector 124 is connectable to vehicle on-board diagnostic connector 132. Second connector 126 can be any type of connector and is preferably releasably connectable to the OBT 100. Optionally, cable 122 can be replaced with wireless transmitters and receivers. In such a case, wireless communication circuitry is connected to the on-board diagnostic system. In that case, preferably, the wireless communication circuitry is removably connectable to the vehicle diagnostic connector 132. However, optionally, wireless communication circuitry may be permanently installed in the vehicle 130 and accessed remotely by OBT 100.
OBT 100 further includes a housing 102, an “up” arrow key 114, a “down” arrow key 116, a read key 106, an erase key 108, a back key 110, an enter key 112 and a display 104. The “up” arrow key 114 and “down” arrow key 116 may be used to scroll through displays. The read key 106 may be used to initiate a request to the vehicle diagnostic system 138. The erase key 108 may be used to erase diagnostic trouble codes (DTC's) from the vehicle on-board diagnostic system 138. The back key 110 is used to return to the previous screen and enter key 112 is used to select items or tasks highlighted on the display 104.
Optical interface circuitry 212 is in circuit communications with a light source 214 and optical reader 216. Light source 214 and optical reader 216 are preferably at least partially retained by the housing (not shown) of OBT 200. Optionally, the light source 214 and/or optical reader 216 are contained in a separate housing and are placed in circuit communication with optical interface circuitry via a cable or wireless medium. Light source 214 can be any light source, such as for example a laser light source, or one or more LEDs. In the case of a bar code scanner, the light from the light source 214 is projected across the bar code. The light reflects off of the lines and spaces between the lines in the bar code. More light may be reflected by the space between the lines for example, than is reflected by the lines. The optical reader 216 receives the reflected light and determines whether the light is reflected by the lines or the space. The bar code is decoded by the optical interface circuitry 212 and communicated to the processor 202.
OBT 200 also includes an input 208 and a display 210 in circuit communication with the processor 202. The input 208 can be any type of input, such as for example, a touch screen, push buttons, selector switches, etc. Preferably, however, input 208 includes one or more keys, such as, for example, the arrow keys and input keys described above. In addition, display 210 can be any type of display, such as, for example, a liquid crystal display (LCD), binary displays, such as LEDs, textual displays, such as n character by m line LCD, or plasma displays, etc.
The processor circuit 202, also referred to herein as just processor 202, may be one of virtually any number of processor systems and/or stand-alone processors, such as microprocessors, microcontrollers, and digital signal processors, and has associated therewith, either internally therein or externally in circuit communication therewith, associated RAM, ROM, EPROM, flash memory, clocks, decoders, memory controllers, and/or interrupt controllers, etc. (all not shown) known to those in the art to be needed to implement a processor circuit.
The processor 202 typically executes a computer program, code or logic, stored in its RAM, ROM, its EPROM and/or flash memory (all not shown), using data stored in any one or more of those memories. For example, the processor 202 may execute a computer program from a ROM (not shown) using data (e.g., codes) stored in flash memory. In general, the computer program executed by the processor 202 initializes the OBT 200 and generates a user interface, for example, using the input device(s) 208 through which a user causes the OBT 200 to communicate with the vehicle on-board diagnostic system to read certain data from the vehicle on-board diagnostic system, format such read data, and display the formatted data on the display 210 or communicate the data to a remote computer (not shown). Additionally, the computer program executed by the processor 202 causes the OBT 200 to optically scan additional information or data and to output the data to the display 210 the remote computer, or memory (not shown).
The vehicle communication circuitry 210 is used to facilitate generating one or more communications protocols with which the OBT 200 and the on-board diagnostic system communicate with one-another. Obviously, the vehicle communication circuitry 208 can be implemented either in hardware, or in software, or in a combination of hardware and software. Typical communications protocols generated by the vehicle communication circuitry 208 include, but are not limited to: SAE J1850 (VPW), SAE J1850 (PWM), ISO 9141-2, ISO 14230-4, and ISO 15765-4 The present invention is not intended to be limited to any specific protocol, however, or even to electrical communications protocols. Other present and future protocols, such as fiber optic and wireless communications protocols are also contemplated as being within the sprit and scope of various embodiments of the present invention.
When connected to the vehicle on-board diagnostic system, the OBT 200 establishes a communications link with the on-board diagnostic system in virtually any interface method, such as, for example, in Applicants U.S. Pat. No. 6,701,233, “Scan Tool with Dropped Communications Detection and Recovery and Improved Protocol Selection,” which is incorporated by reference herein in it's entirety.
Upon establishing a communications link, the OBT can retrieve data, such as, for example, information or DTCs from the vehicle diagnostic system and provide an output having optically scanned information, such as the VIN number provided along with the retrieved data. Data as used herein is used broadly and includes, but is not limited to, at least one bit of information. The output can be to the display 210, a printer (not shown), a remote computer (not shown) or stored in internal memory for later use. This information can be used, for example, to determine if the vehicle complies with the CAA requirements.
Remote unit 244 includes wireless communication circuitry 252 for communicating with the vehicle interface 243. Remote unit 244 also includes a processor 254, input 256 and display 258 that are substantially the same as those described with respect to
An exemplary methodology for communicating with a vehicle diagnostic system and optically scanning additional information using an OBT is described below. The blocks shown represent functions, actions or events performed therein. If embodied in software, each block may represent a module, segment or portion of code that comprises one or more executable instructions to implement the specified logical function(s). If embodied in hardware, each block may represent one or more circuits or other electronic devices to implement the specified logical function(s). It will be appreciated that computer software applications involve dynamic and flexible processes such that the functions, actions or events preformed by the software and/or the hardware can be performed in other sequences different than the one shown.
A communication circuit is established between the OBT and the vehicle diagnostic system at block 302. The communication circuit can be established by any method, including linking with the vehicle using a communications protocol, such as, for example SAE J1850 (VPW), SAE J1850 (PWM), ISO 9141-2, ISO 14230-4, or ISO 15765-4. Upon establishing circuit communication with the vehicle diagnostic system, the OBT requests data from the vehicle diagnostic system, such as, for example, a request for all DTCs at block 304. At block 306, the OBT receives the requested data from the vehicle and provides and output based, at least in part, on the requested data at block 308. The output is provided to the OBT display, or optionally communicated to a remote computer or printer. In addition, the OBT provides an output based on the optically scanned information at block 310. Again, the output is provided to the OBT display, or optionally communicated to the remote computer or printer. The output can be used to determine, for example, if the vehicle complies with the state emissions program.
While the present invention has been illustrated by the description of embodiments thereof, and while the embodiments have been described in some detail, it is not the intention of the applicant to restrict or in any way limit the scope of the appended claims to such detail. Additional advantages and modifications will readily appear to those skilled in the art, for example, adding modular components that connect to the OBT. Therefore, the invention in its broader aspects is not limited to the specific details, representative apparatus and methods, and illustrative examples shown and described. Accordingly, departures may be made from such details without departing from the spirit or scope of the applicant's general inventive concept.
