US20060041349A1

US20060041349A1 - Vehicle diagnostic device

Info

Publication number: US20060041349A1
Application number: US11/000,008
Authority: US
Inventors: Manokar Chinnadurai; Michael Banar
Original assignee: SPX Corp
Current assignee: SPX Technologies Inc
Priority date: 2004-08-19
Filing date: 2004-12-01
Publication date: 2006-02-23
Also published as: CA2516361C; US7805228B2; US20110015822A1; US20060041348A1; CA2516361A1; US8010249B2

Abstract

An apparatus and method is provided that allows a user to record events in a vehicle via a vehicle data recorder in the latest communication protocols, such as Controller Area Network. The vehicle data recorder can record data from the event when a trigger button is actuated by the user and the CAN communication can be controlled by the CAN controller. The data can transferred to a host workstation, where the user can analyze the data from the event and diagnose the problem causing the event.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and is a continuation-in-part of U.S. patent application entitled, Vehicle Diagnostic Device, filed, Aug. 19, 2004, having a Ser. No. 10/921,190, pending the disclosure of which is hereby incorporated by reference in its entirety.

FIELD OF THE INVENTION

The present invention relates generally to an apparatus and method for diagnosing events in a vehicle. More particularly, the present invention relates to an apparatus, such a Vehicle Data Recorder (VDR) and method that record events in a vehicle that can communicate with a Controller Area Network (CAN).

BACKGROUND OF THE INVENTION

When a problem arises in a vehicle, such as an automobile, the owner takes the automobile to a service station or a garage for a mechanic to diagnose the problem. If the problem occurs frequently or occurs at the service station, then the mechanic can diagnose the problem with the diagnostic tools on site. However, the problem can be intermittent and may not occur when the vehicle is at the service station, thus the mechanic may not be able to diagnose the problem. If the mechanic cannot diagnose the problem while the vehicle is at the service station, the owner can become frustrated because the problem still exists and he has taken time off from work in order to bring the vehicle for service. Further, the owner will have to take additional time off to bring the vehicle back for servicing when the intermittent problem occurs again. This scenario can be repeated many times before the problem is properly diagnosed.
An intermittent problem or event may be a spark plug in one of the vehicle's cylinder that does not fire properly when the vehicle hits a bump in the road at certain speeds causing the vehicle to lose power. The event does not occur every time the vehicle hits a bump, but does occur enough that the owner is frustrated. Further, should the intermittent problem occur when the vehicle is in the middle of an intersection, the driver may cause an accident due to loss of power during acceleration across a crowded intersection. However, since the event may not be recreated at the service station or when the mechanic takes the vehicle for a test drive, it will be difficult for the mechanic to diagnose the problem.
A vehicle data recorder (VDR) has been available to record such events when they occur. The VDR is a self-contained modular unit that easily connected to a vehicle. It will monitor and record diagnostic data from the vehicle's computer (Electronic Control Unit or ECU) so that when the event occurs, the data from the event can be recorded and later viewed by the user. Once the data from the event is recorded by the VDR, the mechanic can download the data into a host workstation and diagnose the problem.
The current VDR, however, has not kept up with new communication protocols that exist in new vehicles, such as CAN. Thus, a mechanic could not use a standard VDR in a vehicle that communicates via CAN.
In some instances, it may be useful to be able to view the data recorded by the VDR while the VDR is obtaining the data. For example, while the vehicle is taken for a test drive.
Accordingly, it is desirable to provide an apparatus and method that can diagnose events in a vehicle, such as VDR that can communicate with all communication protocols including CAN.

SUMMARY OF THE INVENTION

The foregoing needs are met, to a great extent, by the present invention, wherein one aspect of an apparatus is provided that in some embodiments includes a VDR that communicates in CAN communication protocol with a vehicle's computer.
In accordance with one embodiment of the present invention, a vehicle data recorder to record data from a vehicle's computer is provided and can include a first connector that can communicate with the vehicle's computer and relay data to and from a vehicle, a processor that may control the vehicle data recorder functions, a memory in communication with the processor to store data, at least one communication protocol controller, wherein at least one communication protocol controller can include a CAN controller for CAN protocol communication with the vehicle's computer, and a second connector that can communicate with a host workstation to transfer the data from the vehicle data recorder to the host workstation. The VDR can further include a trigger button to initiate and/or terminate data recording by the vehicle data recorder, the trigger button can communicate with the processor, a field programmable gate array (FPGA) that can simulate circuits and communicate with the processor and memory, a power source connector for receiving an external power to power the vehicle data recorder, and a vehicle I/O that can communicate in different communication protocols. Additionally, the VDR can include a first board having a vehicle I/O, a real time clock and at least one interface connector, and a second board having the processor, the FPGA, the memory and the at least one communication protocol controller, wherein the first and second boards communicate with each other via a board to board connector. The first connector can be the J1962 male connector and the processor may control the vehicle data recorder function to at least one of recording data for a predetermined period of time, recording data when a trigger button is actuated by a user, recording data for a period of time before and after the trigger is actuated by the user and any other time period. Further, at least one communication controller may control communication hardware such as J1850, UART, ISO 9141, GMLAN, Vehicle SCI and other communication protocol hardware and the second connector may be a RJ-45 jack. The VDR can also include a trigger button having a LED incorporated therein and the host workstation can be a computing device that is one of personal computer, a personal digital assistant and a scan tool.
In accordance with another embodiment of the present invention, a method of communicating data from a vehicle is provided and can include connecting a first connector of a vehicle data recorder to a vehicle's computer, controlling CAN communication protocol with a CAN controller, communicating data via CAN protocol, recording the data of an event, and storing data of the event on a memory. The method can also include connecting a second connector to a host workstation and transferring the data from the event to the host workstation for analysis by a user. The method can further include actuating a trigger button a first time to start recording data from the event and/or actuating the trigger button a second time to stop recording data from the event. Controlling CAN communication is further done via GMLAN, the vehicle I/O, and a processor. Additionally, the method can include illuminating the trigger button with a LED and analyzing the data from the event to diagnose the problem in the vehicle.
In accordance with yet another embodiment of the present invention, a vehicle data recorder system is provided and can include means for connecting to a vehicle's computer and relaying data to and from a vehicle, means for processing that controls the vehicle data recorder functions, means for storing data that communicates with the means for processing and stores data, means for controlling communication protocol, wherein the means for controlling controls CAN communication protocol with the vehicle's computer, and means for connecting to a computing means that transfer data from the vehicle data recorder to a computing means. The vehicle data recorder system can further include means for actuating that initiates and terminates data recording by the vehicle data recorder, the means for actuating communicates with the means for processing, programmable logic means that simulate circuits and communicates with the means for processing and means for storing, means for power for receiving an external power to power the vehicle data recorder, and means for interfacing that communicates in different communication protocols. Additionally, the vehicle data recorder system can include a first means for connecting components having means for interfacing, a real time clock and at least one interface connector, and a second means for connecting having the means for processing, a programmable logic means, the means for storing data, and the means for controlling communication protocol, wherein the first and second means for connecting communicate with each other via a board to board connector. The means for connecting to a vehicle's computer can be a J1962 male connector and the means for processing can control the vehicle data recorder function to at least one of recording data for a predetermined period of time, recording data when a trigger button is actuated by a user, recording data for a period of time before and after the trigger is actuated by the user and any other time period. The means for controlling communication protocol can control communication hardware that includes J1850, UART, ISO 9141, GMLAN, Vehicle SCI and other communication protocol hardware. The means for connecting to the computing means can be a RJ-45 jack and the computing means can be one of a personal computer, a personal digital assistant and a scan tool. Additionally, the VDR can further include means for actuating having a LED incorporated therein.
In accordance with yet another embodiment of the present invention, a vehicle performance monitoring system is provided. The system provides: a vehicle data recorder configured to connect to a vehicle data outlet and configured to selectively record vehicle data, and pass vehicle data to a host workstation.
In accordance with yet another embodiment of the present invention, a vehicle performance monitoring system is provided. The system includes: means for recording vehicle data configured to connect to a vehicle data outlet and configured to selectively record vehicle data, and pass vehicle data to a host workstation; and a host workstation operatively connected to the recording means.
In accordance with yet another embodiment of the present invention, a method of monitoring vehicle performance is provided. The method includes: plugging in a vehicle data recorder into a vehicle data port; passing data through the vehicle data recorder to a host workstation; and wherein the data is passed through to the host workstation in real time.
There has thus been outlined, rather broadly, certain embodiments of the invention in order that the detailed description thereof herein may be better understood, and in order that the present contribution to the art may be better appreciated. There are, of course, additional embodiments of the invention that will be described below and which will form the subject matter of the claims appended hereto.
In this respect, before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details of construction and to the arrangements of the components set forth in the following description or illustrated in the drawings. The invention is capable of embodiments in addition to those described and of being practiced and carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein, as well as the abstract, are for the purpose of description and should not be regarded as limiting.
As such, those skilled in the art will appreciate that the conception upon which this disclosure is based may readily be utilized as a basis for the designing of other structures, methods and systems for carrying out the several purposes of the present invention. It is important, therefore, that the claims be regarded as including such equivalent constructions insofar as they do not depart from the spirit and scope of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of a VDR capable of CAN communication according to a preferred embodiment of the invention.
FIG. 2 is the exploded view of the VDR's external and internal components according to one embodiment of the present invention.
FIG. 3 is a functional block diagram of an embodiment of the VDR.
FIG. 4 is schematic diagram of a VDR plugged into a vehicle data port accessing the vehicles Electronic Control Unit (ECU) and a host unit connected to the VDR and accessing data from the ECU via the VDR.

DETAILED DESCRIPTION

The invention will now be described with reference to the drawing figures, in which like reference numerals refer to like parts throughout. An embodiment in accordance with the present invention provides a VDR that can communicate in the latest communication protocols including CAN via their associated hardware in a vehicle.
CAN is a serial bus system, which was originally developed for automotive applications and is suited for networking devices such as sensors, and actuators. Protocols of CAN include Dual-Wire high (nominal transmission rate of 500 kilobits per second or kbps) and medium speed (nominal transmission rate of 95.24 kbps) and Single-Wire normal mode (nominal transmission rate at 33.33 kbps and high speed mode (nominal transmission rate at 83.33 kbps). CAN is used in applications, such as transmissions, power windows, lights, power steering and instrument panels. A CAN transmitter can send a packet or a message with an identifier to all CAN nodes in the vehicle and each node can determine, based on the identifier, whether it should process the packet. The identifier can also determine the priority the message receives while using the bus. If two messages are sent by two difference devices at the same time to the bus, the device with the lower priority identifier will yield to the higher priority identifier until the higher priority identifier message is completed. After the higher priority message is sent, then the lower priority message will have access to the bus. Thus, the message is not lost and is determinant. CAN advantages include a high degree of flexibility since CAN nodes can be added without change to software or hardware and all nodes can be simultaneously communicated with.
An embodiment of the present inventive apparatus and method is illustrated in FIG. 1, which is a perspective view of a VDR 10 capable of CAN communication. VDR 10 includes a housing 12, an integrated vehicle I/O cable 14 with a J1962 male connector 16 to communicate with the vehicle's computer (ECU), a power connector 18, a communication port (not shown), a cover 20 that covers an optional card connector and a trigger button 22 with LED illumination.
The housing 12 covers the internal components (described below) and can include a first 13 and second parts 15 for easy assembly. The housing 12 can be any shape but is preferably cylindrical in shape. The trigger button 22 is located on the top portion of the VDR and can be any shape, but preferably is cylindrical in shape. The trigger button 22 when depressed will cause the VDR to record the vehicle data information so that the data related to the event can be captured. The VDR can be programmed to record data for a period of time before and after the trigger button 22 is depressed, record data for a period of time without the user's intervention, record only when the trigger button is actuated and stops recording when the trigger button again actuated, record for any other time period desired by the user, and a combination thereof. The data can be uploaded later to the host workstation for the user to review the data from the event. The trigger button 22 can be illuminated by LED so that it can be used in dark environmental conditions. The LED can remain steady so that the user can easily locate the VDR in the dark and can be flashing when the event data is being recorded. It will be recognized by a person skilled in the art that the trigger button 22 can be located anywhere on the outside surface of the VDR including the sides and the bottom.
The cable 14 with the J1962 male connector 16 provide communication between the ECU and the VDR. The cable 14 can be any length so long as its length is long enough for the user to connect the VDR to the ECU. When not in use, the cable can be wrapped around the housing 12 for easy storage. The J1962 male connector 16 connects to its complementary female connector on the ECU. The J1962 male connector 16 allows the VDR to collect data from the ECU in various communication protocols, including CAN.
The power connector 18 is used when the VDR is not connected to the vehicle and the data contained therein is being downloaded to the host workstation. The host workstation can be any computing device, such as a computer, personal digital assistant (PDA) or a scan tool. The information from the VDR can be downloaded to the host workstation via the communication port, which can include a RJ45 jack.
The cover 20 covers the optional card connector (discussed below). The cover 20 is removably attached for easy access to the optional card connector. The optional card can update and add software, other information and hardware to the VDR.
FIG. 2 is the exploded view of the VDR's 10 external and internal components according to one embodiment of the present invention. The internal components are contained in the housing 12, which includes the first 13 and second 15 parts. The first part 13 includes an opening for the power connector 18 to connect to an external power source. When the VDR is used in the vehicle, it can be powered by the battery of the vehicle via the J1962 male connector 16 and when the data from the VDR is being downloaded to the host workstation, the external power source is utilized or when needed by the user. The second part 15 includes an opening for the communication port 24 so that the data from the VDR can be downloaded to the host workstation. The first 13 and second 15 parts have a top portion that receives the trigger button 22 and a bottom portion that receives the cover 20.
The cable 14 includes a first end 11 that is connected to a main board 28 and a second end 17 that is connected to the J1962 male connector 16. The J1962 male connector 16 connects to its complementary female connector on the vehicle's ECU. The J1962 male connector 16 includes various pins that can communicate with various communication protocols in a vehicle.
The main board 28 and a second board 26 are coupled together and communicate with each other via a high density board-to-board connector 30. The main board 28 and the second board 26 can also be coupled together by pins. The main board 28 includes a vehicle I/O, a real-time clock, the power connector 18, a trigger switch 23, and other interface connectors, such as the optional card connector 32, and the communication port 24. The optional card connector 32 connections with an option card (discussed below), which can be used to update the VDR with new communication protocols, pin assignments, software, hardware, and configurations for a Field Programmable Gate Array (FPGA), discussed below.
The trigger switch 23 is actuated by the user when he depresses the trigger button 22 and data from the vehicle is recorded. The second board 26 contains the processor, memory, and protocol controllers (discussed below). Although three cards (main and second boards and option card) are discussed herein, one skilled in the art will recognize that additional cards and components or less cards and components are possible depending on the needs of the user.
FIG. 3 is a functional block diagram 50 of an embodiment of the VDR. The J1962 male connector 16 can be connected to the ECU so that the VDR can collect diagnostic data from the vehicle. The J1962 male connector 16 includes various pins that mate with complementary pins in the ECU. The pins relay communication protocols that carry diagnostic data and instructions to and from the vehicle. The pins are assigned depending on the communication protocol of the vehicle and are known in the art.
The option card 54 provides flexibility to the VDR by allowing the VDR to support new communication protocols, pin assignments, software, information, hardware, and configure the FPGA. Additionally, the option card 54 can also act to simply pass through the communication protocols, if desired. All communication protocols hardware circuits 58, 60, 62, 64, 66, 68, 70 can communicate with the option card 54. The option card allows flexibility for pin swapping, pin reconfiguration or additional pins to adapt to various current and new communication protocols. A multiplexer can be added to provide additional circuits for signal communication.
The VDR and the option card 54 can be supplied with power via vehicle power 56 and this allows the option card 54 to have active components thereon. Active components include new protocol transceivers to communicate in the new communication protocols. Additional processor 84, FPGA 82, memories 92, 94, can be added to the VDR via the option card 54 to increase processing power and memory storage. Should additional power is needed for the VDR and its components, additional power supply and conditioners can also be added with the option card 54.
Wired data transfer ports (serial, parallel, USB (Universal Serial Bus), Fire Wire (IEEE 1394) and others) and wireless data transfer ports for wireless communication (Wi-Fi, BLUE TOOTH, Infrared, Radio Frequency and other wireless communication protocols) can also be added to the VDR via the option card 54. The option card 54 can include the appropriate wireless communication transmitters and receivers thereon so that wireless communication can occur.
Software updates can be added to the memories, the processor 84 and FPGA 82 such as new firmware, software to communicate with new communication protocols, software to run new hardware, software to reconfigure the FPGA, software to update mode programming or new procedures. It will be recognized by a person skilled in the art that additional hardware and software can be added in the future without departing from the scope of the option card 54. The option card 54 is inserted into the option card connector 32 and can be protected by the cover 30. To replace the option card 54 with a new option card, the cover 30 can be removed and the old option card can be removed and a new one inserted. Once completed, the cover 30 can be left off or reattached to the VDR.
When the VDR is being used in the vehicle, it can be powered by the vehicle power 56 that supplies power to a power supply 72. The vehicle power 56 can be provided through the J1962 male connector 16 when it's hooked up to the vehicle's computer. Alternatively, power coax 74 can be used to supply external power 76 to the power supply 72 when the VDR is outside of the vehicle, such as when it is downloading event data to the host workstation or as otherwise needed by the user.
The communication protocols and hardware include J1850 (58), ISO 9141 (60), Vehicle SCI 62 (Serial Communication Interface), Slow/Fast Codes 64, GMLAN Single Wire 66, GMLAN high speed 68, and GMLAN medium speed 70. The J1850 (58) is a multiplexed communication protocol that can be further divided into Variable Pulse Width (VPW) and Pulse Width Modulation (PWM). PWM typical communication speed is about 41.6 kbps and is a two wire balanced signal, while VPW typical communication speed is about 10.4 kbps and is a one signal wire. This protocol is used for diagnostic and data sharing purposes and can be found in engine, transmission, ABS, and instrumentation applications.
ISO 9141 (60) is either a single wire (K line only) or a two wire (K and L line). The K line is bi directional and conveys address information and data with the ECU. The L line is unidirectional and is only used during initialization with the ECU. This protocol is implemented on 1996 and newer vehicles.
GMLAN is a family of serial communication buses that allows ECUs to communicate with each other or with a diagnostic tester. There are three types of buses, a dual wire high speed bus (GMLAN high speed) 68, a dual wire medium speed bus (GMLAN medium speed) 70, and a single wire low speed bus (GMLAN single wire) 66. The GMLAN high speed 68 (500 kbps) is typically used for sharing real time data such as driver commanded torque, actual engine torque, steering angle, etc. The GMLAN medium speed 70 (up to 250 kbps) is typically used for applications (display, navigation, etc.) where the system's response time demands that a large amount of data be transmitted in a relatively short amount of time, such as updating a graphics display. The GMLAN single wire 66 (33.33 kbps) is typically used for operator controlled functions where the system's response time requirements are in the order of 100-200 msecs. This bus also supports high speed operation at 83.33 kbps used only during ECU reprogramming. The decision to use a particular bus in a given vehicle depends upon how the feature/functions are partitioned among the different ECUs in that vehicle. GMLAN buses use the CAN communications protocol for relaying information.
Slow/Fast Codes can be found in GM vehicles and is a serial communication protocol. Some examples include GM Dual Baud, GM10, GM30, Master, Normal, Unidirectional and others. The serial baud transmission rate can be about 160 kbps to about 9600 kbps for Fast Codes. Slow Codes are used by grounding a Slow Code diagnostic pin in the vehicle diagnostic connector of the ECU, which forces the vehicle to display error codes via the check engine light. The user counts the number of blinks of the check engine light to represent an error code and decipher the code with a code manual.
Vehicle SCI 62 allows communication of data in a one-wire serial method between the tool and the ECU. The transmission rate is about 62.5 kbps. GM vehicles through 1995 use the UART (Universal Asynchronous Receiver/Transmitter is responsible for performing the main task in serial communications with computers), which makes use of this Vehicle SCI 62.
Certain vehicle I/O pins support multiple protocols and signals and must be passed through a Vehicle I/O 80 for proper routing, which includes MUX/DEMUX. Because vehicle manufacturers can assign different communication protocol signals on the same pin, the Vehicle I/O 80 processes the signal and routes the signal to the proper communication protocol processors. The proper routing configurations can be controlled through a microprocessor 84 (see below). The Vehicle I/O 80 is capable of communicating in the various communication protocol.
CAN controller 78 controls the CAN communication protocols discussed above. There can be three separate CAN controllers 78 (High and Medium Speed and Single Wire) in the VDR. With three CAN controllers 78, the different CAN protocols can be better routed to proper CAN controller for faster information receiving and transmitting than with just one CAN controller 78. The CAN controller 78 communicates with the Vehicle I/O 80 and the processor 84. A person skilled in the art will recognize that there can be one, two or any amount of CAN controller 78 on the VDR as desired.
The processor 84 can be any processor that has enough processing power that is required by the VDR. Preferably, the processor 84 is the MOTOROLA MC68331. The processor 84 has the ability to provide mode programming 86, which can program the ECU by connecting different load resistors to a mode pin. The trigger button 22 is in communication with the processor 84 so that the processor can control the data gathering for the VDR. The trigger button 22 can be illuminated by the LED 96 and actuated by user 102.
Additionally, the processor 84 communicates with a real time clock 100, which retains time and date information without the need of external power. The real time clock 100 is part of the main board 28. It would be recognized by a person skilled in the art that the real time clock 100 can be integrated with the processor 84 or separate from it. Memory such as Flash 92 (boot, program, record) and SRAM 94 are provided to the processor 84 so that information can be loaded into the processor or FPGA 82 or the information can be stored for later retrieval.
The processor 84 also communicates with the FPGA 82. Although any FPGA can be used, an XILINX XC2S30 may be utilized. The FPGA 82 is a specially made digital semiconductor that can be used as a programmable logic device that can emulate new electrical circuits as needed by the user. By incorporating the FPGA 82, the VDR can be updated with new circuits without the need of providing the actual new circuits on the boards or replacing the current boards on the VDR. The FPGA 82 versatility can be used to provide new circuits for new communication protocols or other needs.
The FPGA 82 is also in communication with RJ-45 (88) with RS-232C, which provides serial communication with the host workstation 90. The host workstation 90 receives the information recorded by the VDR so that events can be analyzed.
In operation, the VDR is connected to the ECU via the J1962 male connector. The VDR is powered by the battery in the vehicle through the connection of the ECU with the J1962 male connector. Once connected, the VDR is ready to record events in the vehicle. Depending on how the VDR is programmed to operate, the VDR can to record data for a period of time before and after the trigger button is depressed, record data for a period of time without the user's intervention, record only when the trigger button is actuated and stops recording when the trigger button again actuated, record for any other time period desired by the user, and a combination thereof. By recording before and after the trigger button 22 is depressed, the user can have a better sense of what is occurring in the vehicle before and after the event. If the VDR is programmed to record automatically, the user can pay attention to other aspects of the vehicle when the event occurs that can not be recorded by the VDR and can pay attention to driving the vehicle. Additionally, because the VDR can be automatically recording, if the event occurs quickly it can be recorded without having the user actuating the trigger button. By having the user manually actuating the trigger button to record the event, multiple event data can be recorded from the ECU because more memory is available. If the vehicle is equipped with CAN, then data from the ECU can be transmitted through the option card (if present) to the proper communication hardware. In this case, the CAN is relayed through GMLAN 66, 68 and 70 depending on the CAN protocol. The vehicle I/O may be needed if the same pin is being used to convey different communication protocols. The CAN controller also controls the CAN communication. The data being gathered can be stored in flash memory or other memory chips in the VDR. The data can later be downloaded to the host station via RJ-45 serial connection to the host workstation and analyzed.
In some instances, it may be useful to display or make available to a system user the data that the VDR is obtaining from the ECU in real time, or in other words, while the data is input to the VDR. FIG. 4 shows one embodiment in accordance with the invention where a system 106 including a VDR 10 is configured to obtain data from the ECU and act as a pass through to send the data to a host workstation 90.
As shown in FIG. 4, the VDR 10 is operatively connected with a cable 14. The cable 14 may be an I/O cable and may be an integrated cable 14. Other types of cable may also be used in accordance with the invention. The cable 14 enables the VDR 10 to communicates with a vehicles ECU via a J1962 male connector 16. Other suitable connectors may also be used in accordance with the invention.
Data received by the VDR 10 is transmitted to a host workstation 90 via a connector 104. Any suitable data connector either a wire or wireless may be used in accordance with the invention. In some embodiments of the invention, the host workstation 90 is a processing based system such as a PC computer. The host workstation 90 may be a lap top computer, a notebook computer, or any other portable computer. In some embodiments of the invention, the host workstation, runs an operating system such as, for example, Windows 95, 98, 2000, or XP. Other suitable operating systems may be run by the host workstation 90 in accordance with the invention. In some embodiments of the invention, the host workstation 90 is portable and has its own power supply and display so the host workstation 90 may be taken along on a test drive and have power to operate and display data. An example of a display capability in accordance with the invention is a screen such as a computer screen.
In other embodiments of the invention, the host workstation 90 is a portable hardware device such as a scan tool.
Operation of some embodiments of the invention is as follows. The host workstation 90 runs a program to operate the VDR 10. The program is executable code run on the host workstation 90. A system operator operating the program on the host workstation 90 selects a pass through operating mode for the VDR 10. Selection of the pass through mode causes the host workstation 90 to send a signal to the VDR 10 to operate in a pass through mode which will cause the VDR 10 to send vehicle data to the VDR 10 receives to the host workstation 90. Optionally, the operator can select a mode that will case the VDR 10 to save the data as well as send the data to the host workstation 90.
Optionally, the VDR 10 can record data while it is acting as a pass through to the host workstation 90. The recording of the data on the VDR 10 functions as previously described by actuating the button 22 or by command of the host workstation 90.
The host workstation 90 can, in some embodiments, also record data passed to it by the VDR 10. In some embodiments of the invention, software or hardware associated with the VDR 10 and/or the host workstation 90 will allow a user to select a save function that will operate to save vehicle data onto the VDR 10 or to memory associated with the host workstation 90.
In some embodiments of the invention, the host workstation 90 is configured to store the incoming vehicle data on a database. The database may be stored on the host workstation 90 or at a remote location in communication with the host workstation 90 such as a network, the internet, an Ethernet, and the like. Optionally, the host workstation 90 can transmit data via a network, internet, Ethernet, and the like.
The many features and advantages of the invention are apparent from the detailed specification, and thus, it is intended by the appended claims to cover all such features and advantages of the invention which fall within the true spirit and scope of the invention. Further, since numerous modifications and variations will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation illustrated and described, and accordingly, all suitable modifications and equivalents may be resorted to, falling within the scope of the invention.

Claims

1. A vehicle performance monitoring system comprising:

a vehicle data recorder configured to connect to a vehicle data outlet and configured to selectively record vehicle data, and pass vehicle data to a host workstation.

2. The vehicle performance monitoring system of claim 1, wherein the vehicle data recorder is further configured to selectively record vehicle data and pass vehicle data to a host workstation.

3. The vehicle performance monitoring system of claim 1, wherein the vehicle data recorder is portable and fits inside a vehicle to permit vehicle data to be sent to the vehicle data recorder while the vehicle is operated.

4. The vehicle performance monitoring system of claim 3, further comprising a host workstation that is portable and fits inside a vehicle to permit vehicle data to be displayed while the vehicle is operated.

5. The vehicle performance monitoring system of claim 4, wherein the vehicle data displayed is real time data.

6. The vehicle performance monitoring system of claim 5, wherein the host workstation records the data while the data is displayed.

7. The vehicle performance monitoring system of claim 1, further comprising a host workstation wherein the host workstation is a scan tool.

8. The vehicle performance monitoring system of claim 1, further comprising a host workstation wherein the host workstation is a PC computer.

9. The vehicle performance monitoring system of claim 8, wherein the PC computer is a portable computer.

10. The vehicle performance monitoring system of claim 1, further comprising a connection operatively connecting the host workstation to least one of an internet, Ethernet, and a network.

11. The vehicle performance monitoring system of claim 1, further comprising a data base for storing the data.

12. A vehicle performance monitoring system comprising:

means for recording vehicle data configured to connect to a vehicle data outlet and configured to selectively record vehicle data, and pass vehicle data to a host workstation; and

a host workstation operatively connected to the recording means.

13. The vehicle performance monitoring system of claim 12, wherein the means for recording and the host workstation are portable.

14. The vehicle performance monitoring system of claim 12, wherein the host workstation has a data display and displays real time data.

15. A method of monitoring vehicle performance comprising:

plugging in a vehicle data recorder into a vehicle data port;

passing data through the vehicle data recorder to a host workstation; and

wherein the data is passed through to the host workstation in real time.

16. The method of claim 15, further comprising recording the data.

17. The method of claim 16, further comprising displaying the data.

18. The method of claim 17, further comprising displaying the date inside the vehicle.

19. The method of claim 15, further comprising analyzing the data.

20. The method of claim 15, further comprising making the data available over at least one of an internet, Ethernet, and a network.