US 7,447,574 B1Grant
In-vehicle wiring harness with multiple adaptors for an on-board diagnostic connector
Issue Date:2008-11-04
•6 Claims
•10 Drawing Sheets
Abstract
An embodiment provides a wiring harness that connects a telematics device to a host vehicle. One embodiment of the wiring harness may include: 1) a cable featuring a plurality of wires; 2) a first connector featuring a snap-on adaptor that attaches to a connector core with a pin configuration that mates with a diagnostic scan tool; 3) a second connector that connects to an in-vehicle diagnostic system; and 4) a third connector that connects to the telematics device. A wiring kit embodiment and method embodiments for coupling a telematics device to a host vehicle are also disclosed.
Metadata
Assignee
- HTI IP, LLC
Inventors
- Paul L. Washicko
- Robert Hunt
Application Information
Application Number:US 11/799,848
Filing Date:2007-05-03
Priority Date:2004-04-26
Art Unit:3661
Classifications
IPC:
G01M17/00G01M15/00G06F7/00
Patent Drawings (10 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a divisional of U.S. application Ser. No. 10/831,952 filed on Apr. 26, 2004 now U.S. Pat. No. 7,225,065.
Background
[0002] 1. Field
[0003] The present invention relates to vehicle wiring systems and components.
[0004] 2. Description of the Invention Background
[0005] Vehicles, such as light-duty cars and trucks and heavy-duty tractor/trailers, can include ‘telematics’ systems that monitor the vehicle's location and diagnostic data. Such telematics systems typically include an in-vehicle telematics device that includes a conventional global positioning system (‘GPS’) that receives signals from orbiting satellites, and a processor that analyzes these signals to calculate a GPS ‘fix’. The fix features location-based data such as a vehicle's latitude, longitude, altitude, heading, and velocity, and typically describes the vehicle's location with an accuracy of about 10 meters or better.
[0006] In addition to the GPS, telematics devices typically include a wireless transmitter that sends location-based data through a wireless network, and an Internet-accessible website that displays the data.
[0007] Telematics devices can also monitor the host vehicle's diagnostic system. As an example of a diagnostic system, most light-duty automobiles and trucks beginning with model year 1996 include an on-board diagnostic (OBD) system as mandated by the Environmental Protection Agency (EPA). OBD systems feature a network of in-vehicle sensors that monitor the vehicle's electrical, mechanical, and emissions systems, and in response generate data that are processed by the vehicle's engine control unit (ECU). The data are used, for example, to detect malfunctions or deterioration in the vehicle's performance. They are accessed from the ECU according to the following serial communication protocols: J1850 VPW (Ford); J1850 VPWM (General Motors); ISO 9141-2 (most Japanese and European vehicles); Keyword 2000 (some Mercedes and Hyundai vehicles); and CAN (a newer protocol used by many vehicles manufactured after 2004). Parameters within the data include vehicle speed (VSS), engine speed (RPM), engine load (LOAD), and mass air flow (MAF). The ECU can also generate diagnostic trouble codes (DTCs), which are 5-digit codes (e.g., ‘P0001’) indicating emissions-related problems with the vehicle.
[0008] Most vehicles manufactured after 1996 include a standardized, serial, sixteen-cavity connector, referred to herein as an ‘OBD connector’, that provides access to the above-mentioned data. The OBD connector serially communicates with the vehicle's ECU, and additionally provides power (approximately 12 volts) and ground. The OBD connector typically lies underneath the vehicle's dashboard. A conventional scan tool can be plugged into this OBD connector to retrieve diagnostic data from the vehicle's ECU.
[0009] While the core and pin-out of each OBD connector is universal and mandated by the EPA, the form factor, and particularly the plastic configuration around the connector's perimeter, typically varies by vehicle make. And even within a given make, the connector's form factor may vary for a given model.
[0010] Heavy-duty trucks typically include a diagnostic system, referred to herein as a ‘truck diagnostic system’, which is analogous to the OBD systems present in light-duty vehicles. Truck diagnostic systems typically operate a communication protocol called J1708/J1587 or CAN that collects diagnostic data from sensors distributed in the truck. As in light-duty vehicles, the truck's ECU processes these data, and then makes them available through a six or nine-pin connector, referred to herein as ‘the truck diagnostic connector’, typically located in the truck's interior. Again, a technician can obtain the data from the truck's ECU by plugging a conventional scan tool into the truck diagnostic connector.
[0011] In the past, a telematics device connected to the host vehicle's diagnostic connector was typically mounted within the vehicle. Unfortunately, such mounting arrangements make it convenient for thieves to simply remove or unplug the telematics device to thwart its vehicle tracking abilities.
[0012] In addition, during a repair process, the technician must unplug the telematics device from the vehicle's diagnostic connector so that a conventional scan can be plugged into that connector and retrieve diagnostic data from the vehicle's ECU. After the diagnostic material has been retrieved and the scan tool has been unplugged from the diagnostic connector, the technician must remember to reconnect the telematics device to the connector. The telematics device is rendered inoperative if the technician forgets to reconnect it to the OBD connector.
[0013] These are just a few of the problems associated with prior telematics and diagnostic monitoring systems employed in vehicles for monitoring the vehicle's location and diagnostic data.
Summary
[0014] One embodiment of the present invention is directed to a wiring harness for connecting a telematics device to a host vehicle. In one embodiment, the wiring harness includes a plurality of electrical conductors and a first connector electrically coupled to at least some of the electrical conductors. The first connector is configured to be coupled to a diagnostic scan tool. A second connector is electrically coupled to at least some of the electrical conductors and is configured to be coupled to an in-vehicle diagnostic system. A third connector is coupled to at least some of the electrical conductors and is configured to be coupled to the telematics device.
[0015] Another embodiment of the present invention is directed to a wiring kit for connecting a telematics device to a host vehicle. In one embodiment, the wiring kit includes a wiring harness. The wiring harness may comprise an electrically conductive cable and a first connector which is in electrical contact with the cable and has a connector core. A second connector is also in electrical contact with the electrically conductive cable and is configured to connect to an in-vehicle diagnostic system. A third connector is in electrical contact with the cable and is configured for attachment to a telematics device. A plurality of adaptors are also included wherein each adaptor is configured to be selectively attached to the connector core.
[0016] Yet another embodiment of the present invention is directed to a wiring kit for electrically connecting a telematics device to an ECU of a vehicle. One embodiment includes an electrical cable and a first connector in electrical contact with the electrical cable. A plurality of adaptors may also be provided wherein each adaptor is selectively attachable to the first connector and wherein at least one adaptor is configured to facilitate electrically coupling the first connector to a core connector that corresponds to the diagnostic connector of the selected vehicle. A second connector is also mounted in electrical contact with the engine control unit of the selected vehicle control unit. A third connector is en electrical contact with the cable and is configured to be connected to the telematics device within the selected vehicle.
[0017] Another embodiment of the present invention is directed to a method for coupling a telematics device to a host vehicle. In one embodiment, the method includes coupling an electrical cable to an engine control unit of the vehicle. The electrical cable is coupled to the telematics device. A diagnostic connector is coupled to the electrical cable wherein the diagnostic connector is configured to interface with a diagnostic scan tool that corresponds to the vehicle.
[0018] Still another embodiment of the present invention includes a method for mounting a telematics device within a vehicle that has an on-board diagnostic unit for collecting diagnostic data. The on-board diagnostic unit is coupled to an original on-board diagnostic connector mounted in an accessible location within the vehicle to enable a diagnostic scan tool that has a connector which is unique to the type of vehicle to be coupled thereto to retrieve the diagnostic data. In one embodiment, the method includes mounting the telematics unit within the vehicle such that it is hidden from view within the vehicle. An electrical cable is coupled to the telematics unit. The electrical cable may be coupled to the telematics unit prior to or after the telematics unit has been mounted. The original on-board diagnostic connector is removed from the accessible location in which it was mounted. The electrical cable is coupled to the original on-board diagnostic connector. Another diagnostic connector capable of mating with the scan tool is coupled to the electrical cable. The another diagnostic connector is mounted or otherwise supported in the accessible location.
Brief Description of Drawings
[0019] The features and advantages of various embodiments of the present invention can be understood by reference to the following detailed description taken with the drawings.
[0020] FIG. 1 is a three-dimensional side view of the wiring harness according to an embodiment of the invention, featuring an ‘effective’ OBD connector, that connects a telematics device to a host vehicle.
[0021] FIG. 2 is a three-dimensional, exploded side view of the effective OBD connector of the wiring harness of FIG. 1 .
[0022] FIG. 3 is three-dimensional side view of the wiring harness of FIG. 1 featuring a first connector portion that connects to one of multiple adaptors, each matched to a different host vehicle's on-board diagnostic connector.
[0023] FIG. 4 is a front view of an effective OBD connector of FIG. 2 used for light-duty vehicles.
[0024] FIGS. 5A and 5B are front views of effective connectors used, respectively, for heavy-duty vehicles supporting six-pin connectors, and heavy-duty vehicles supporting nine-pin connectors.
[0025] FIG. 6 is a schematic drawing of a telematics system for collecting and transmitting diagnostic and location information from a vehicle that uses the wiring harness of FIG. 1 .
[0026] FIG. 7 is a schematic drawing of an alternate embodiment of the wiring harness of FIG. 1 .
[0027] FIG. 8 is a schematic drawing of an alternate embodiment of the wiring harness of FIG. 1 featuring a “vampire tap” for making an electrical connection between the host vehicle's OBD system and the telematics device.
[0028] FIG. 9 is a schematic drawing of an alternate embodiment of the wiring harness of FIG. 1 featuring a wireless interface between the host vehicle's OBD system and the telematics device.
Detailed Description
[0029] The following description refers to the accompanying drawings that illustrate certain embodiments of the present invention. Other embodiments are possible and modifications may be made to the embodiments without departing from the spirit and scope of the invention. Therefore, the following detailed description is not meant to limit the present invention. Rather, the scope of the present invention is defined by the appended claims.
[0030] Various embodiments of the present invention provide a modular wiring harness that may be used to connect an in-vehicle telematics device to a host vehicle and the diagnostic system therein. In one embodiment, the wiring harness comprises a snap-on, configurable adaptor that snaps or is otherwise coupled onto a connector core. Once attached, the pieces form an ‘effective OBD connector’. The wiring harness may be arranged to enable the telematics device to be effectively hidden under the dashboard while at the same time providing easy access to an OBD connector to obtain diagnostic information from the vehicle's ECU. It may be advantageous for the wiring harness to include a snap-on adaptor because, while the core and pin-out of each OBD connector is universal and mandated by the EPA, the form factors of these connectors typically vary by vehicle make and model.
[0031] As will be discussed in further detail below, to install one of the wiring harness embodiments of the invention, a technician removes the vehicle's original OBD connector from its location under the dash and connects it to a second connector portion of the harness. The technician then snaps or otherwise couples an effective OBD connector adaptor with the same form factor as the original OBD connector onto a first connector portion of the harness, and inserts the adaptor into the now-vacated original location of the original OBD connector. The technician may then secure the telematics device in a location within the vehicle that is not easily accessible or noticeable, and also connects the telematics device to a third connector portion of the harness. The technician may then deploy the antennae for the GPS and wireless transmitter of the telematics device. Data from the ECU can then be accessed through the original OBD connector, at the second connector portion, through the harness from the effective OBD connector adaptor at the first connector portion, or through the harness by the telematics device from the third connector portion.
[0032] In this configuration, both the effective OBD connector (now located under the dash in the original location of the original OBD connector) and the original OBD connector (now communicating with the telematics device through the harness) communicate serially with the host vehicle's ECU. The reader will appreciate that this configuration provides several advantages. First, it allows the vehicle's telematics device to both communicate with the vehicle's ECU and be hidden from view. This means the device is not visible to passengers within the vehicle, making it unobtrusive and effective for applications such as recovery of stolen vehicles. Second, the effective OBD connector adaptor, which is visible from within the vehicle, looks like the original OBD connector and therefore does not indicate that any telematics device is installed. This too aids recovery of stolen vehicles. Third, during a repair process, a technician can access the vehicle's diagnostic computer using an automotive scan tool without having to unplug the telematics device from the vehicle's original OBD connector. The technician simply plugs a scan tool into the effective OBD connector, which is easily accessed underneath the vehicle's dash, and then downloads diagnostic data from the vehicle's ECU.
[0033] By selecting the proper adaptor from a set of multiple adaptors, a technician can use the present invention as a universal wiring harness to install the telematics device in virtually any vehicle. This means it is not necessary to manufacture custom wiring harnesses for each type of vehicle. Companies installing the telematics device (e.g., automotive dealerships) can stock a single ‘base’ wiring harness (which can be relatively expensive) and multiple adaptors (which are relatively inexpensive). This is efficient for control of inventory. Alternatively, through a retail channel, a customer can purchase the telematics device, the base wiring harness, and multiple adaptors. In both cases, to install the telematics device, the installer simply selects an adaptor that matches the host vehicle's OBD connector, and snaps it or otherwise fastens it to the connector core to form the effective OBD connector. The installer then attaches the effective OBD connector to the wiring harness, installs the telematics device, and may choose to discard the un-used adaptors.
[0034] One or more of these features of the wiring harness complement basic advantages provided by the telematics system, described in detail below. For example, various embodiments of this system provide wireless, real-time transmission and analysis of diagnostic and location-based data, followed by analysis and display of these data by an Internet-accessible website. This makes it possible to characterize the vehicle's performance and determine its location in real-time from virtually any location that has Internet access. Diagnostic and location-based data may be complementary and, when analyzed together, can improve conventional services such as roadside assistance, vehicle-theft notification and recovery, and remote diagnostics. For example, the information can indicate a vehicle's location, its fuel level and battery voltage, and/or whether or not it has any active DTCs. Using this information, a call center can dispatch a tow truck with the appropriate materials (e.g., extra gasoline or tools required to repair a specific problem) to repair the vehicle accordingly. More applications of conventional telematics systems are found within the following U.S. patents, the disclosures of which are herein incorporated by reference: 1) U.S. Pat. No. 6,594,579; 2) U.S. Pat. No. 6,604,033; 3) U.S. Pat. No. 6,611,740; and 4) U.S. Pat. No. 6,636,790.
[0035] More specifically, one embodiment of the invention provides a wiring harness that connects a telematics device to a host vehicle. The wiring harness may include: 1) a cable featuring a plurality of wires; 2) a first connector featuring a snap-on adaptor that attaches to a connector core with a pin configuration that mates with a diagnostic scan tool; 3) a second connector that connects to an in-vehicle diagnostic system; and 4) a third connector that connects to the telematics device.
[0036] In at least some of the embodiments, the cable includes a first connector portion that mates to the first connector, and a second connector portion that mates with the second connector. The first and second connector portions, for example, can be IDC connectors. In other embodiments, the first connector further includes a first set of metal contacts that mate with a diagnostic scan tool, and a second set of metal contacts that mate with the first connector portion.
[0037] In one embodiment, the connector core includes sixteen metallized cavities and may be configured to mate with an OBD-II male connector. Similarly, the second connector may include sixteen metallized pins and be configured to mate with an OBD-II female connector. However, other cavity and pin arrangements could conceivably be employed depending upon the specific application.
[0038] Various embodiments of the present invention may be useful in a wide range of vehicles. Examples of such vehicles include, but are not limited to, automobiles, commercial equipment, light, medium and heavy-duty trucks, construction vehicles (e.g., front-end loaders, bulldozers, forklifts), powered sport vehicles (e.g., motorboats, motorcycles, all-terrain vehicles, snowmobiles, jet skis, and other powered sport vehicles), collision repair vehicles, marine vehicles, and recreational vehicles.
[0039] FIG. 1 shows a wiring harness 10 according to one embodiment of the invention that features a snap-on adaptor 25a chosen to match a form factor of the OBD connector present in a host vehicle. During an installation process, the snap-on adaptor 25a connects to an outer perimeter of an OBD-compliant connector core 26 to form an ‘effective’ OBD connector 27 that looks virtually identical to the OBD connector 36 present in the vehicle. In this embodiment, the effective OBD connector 27 is two-sided: one side includes a core 26 with sixteen OBD-compliant metallized cavities and a configuration that matches a standard OBD connector, while the second side features twenty pins (not shown in the figure) in a configuration that matches a standard IDC connector. A printed circuit board (not shown in the figure, but described in more detail with reference to FIG. 2 ) connects each cavity of the connector core 26 to a mating pin in the IDC connector. This may be accomplished during manufacturing. During installation of the wiring harness, the effective OBD connector 27 connects to a first connector portion 18 attached to the wiring harness 10. In this embodiment, the first connector portion 18 is a female, twenty-cavity IDC connector. A first clip 23 may be used to secure the effective OBD connector 27 to the first connector portion 18. In one embodiment, the clip 23 is fabricated from metal material. Other materials and arrangements could also be employed for the clip. In addition, if appropriate, the OBD connector 27 could conceivably be attached to the first connector portion 18 by other suitable fasteners and fastening arrangements such as screws or the like.
[0040] The wiring harness 10 is also attached to a second connector portion 17, which, in this embodiment, is identical in configuration to the first connector portion 18. The second connector portion 17 in this embodiment features a female twenty-cavity IDC connector. It mates with an OBD connector 28 that, in this embodiment, includes twenty male pins in an IDC pin-out on one side, and sixteen male pins in an OBD pin-out on the other side. A third connector portion 16, which, in this embodiment, is identical to the above-described first 18 and second 17 connector portions, connects to the in-vehicle telematics device 20 through twenty male pins in an IDC pin-out 24. Second and third clips (22, 21), respectively, secure the second and third connector portions (17, 16) to the male OBD connector 28 and telematics device 20. As described above, clips 21 and 22 may be fabricated from metal, although other clip materials and/or fastener arrangements could also be successfully employed. Also in this embodiment, a twenty-wire ribbon cable 15, which may include first 15A and second 15B portions, connects individual pins and provides electrical communication between the first 18, second 17, and third 16 connector portions.
[0041] Once all the above-mentioned connections are made, the wiring harness is fully operational and ready to install in the host vehicle. To do this, the vehicle's original female OBD connector 36 is removed from its location and connected to the male OBD connector 28. See FIG. 6 herein. Once secured, this connection facilitates transmission of power, ground, and the vehicle's diagnostic data, through a serial connection to the host vehicle's ECU and to the telematics device 20. The installer may then insert the effective OBD connector 27 into the vacated slot or mounting area that previously housed or otherwise supported the vehicle's original OBD connector 36. With this in place, a conventional automotive scan tool 70, once plugged into the effective OBD connector 27, can also download diagnostic information from the vehicle's ECU. To complete the installation, the third connector portion 16 is coupled to the telematics device 20 and the telematics device 20 and cable are secured underneath the vehicle's dash and hidden from view. If the telematics device 20 includes external antennae (e.g. for a wireless transmitter and GPS), these too are secured within the vehicle.
[0042] In this configuration, the telematics device 20 is not visible to passengers within the vehicle 12, making it unobtrusive and effective for applications such as recovery of stolen vehicles. Also, the effective OBD connector 27 looks like the original OBD connector 36, and is in the original location of the original OBD connector 36, so it is not obvious that any telematics device 20 has been installed. This further aids in recovering stolen vehicles. In addition, during a repair process, a technician can access the vehicle's diagnostic computer with an automotive scan tool 70, communicating through the effective OBD connector 27, without having to unplug the telematics device 20 from the original OBD connector 36. The technician simply plugs a scan tool 70 into the effective OBD connector 27, which is easily accessed underneath the vehicle's dash, and then downloads diagnostic data from the vehicle's ECU 35.
[0043] In one embodiment, at any given time, diagnostic data generated by the vehicle's ECU can only pass through the effective OBD connector or to the in-vehicle telematics device 20. It cannot be accessed simultaneously from both components. The in-vehicle telematics device 20, therefore, typically includes firmware that detects when a scan tool 70 is connected to the effective OBD connector 27. It then ‘backs off’ from the ECU so that it receives no data until the scan tool 70 is disconnected. In this way, the technician can download the vehicle's diagnostic data during a repair without having to disconnect the in-vehicle telematics device.
[0044] FIG. 2 shows a detailed, exploded view of an embodiment of an effective OBD connector 27, and provides one example of how this component may be connected to the first connector portion 18 of the cable 15. The effective OBD connector 27 in this embodiment features a snap-on adaptor 25e that replicates a configuration of the host vehicle's OBD connector 36; the adaptor in FIG. 2 , for example, is common for many Toyota, Honda, and Chrysler vehicles. However, other adaptor configurations could be employed. In this embodiment, the adaptor 25e attaches to an outer perimeter of the connector core 26. A plastic core 29 located within the connector core 26 may have sixteen cavities 34, each filled with a single hollow metal pin 31a, 31b. The metal pins 31a, 31b extend through individual cavities 34 in the plastic core 29 and into a set of corresponding holes 37 formed through a printed circuit board 30. Once inserted, the ends of the hollow metal pins 31a, 31b define a plurality of metallized cavities for accepting a corresponding number and arrangement of metal pins.
[0045] In this embodiment, metal traces 32′ etched on the printed circuit board 30 connect the set of holes 37 to a set of metal leads 38 on the board's opposite side. The set of metal leads 38 align with a set of pins 39 within an IDC connector 33. The set of pins 39 extend through the IDC connector and are exposed on its opposite side 40. During manufacturing, the metal pins 31a, 31b within the plastic core 29 are soldered to the corresponding holes 37 on one side of the printed circuit board 30. Metal leads 38 on the other side are then press-fit onto the set of pins 39 protruding from the IDC connector 33. This forms the core connector 26, which features a set of pins 40 extending from the IDC connector 33 that are in electrical contact with the cavities 34 within the plastic core 29. Other pin and connector arrangements could conceivably be employed without departing from the spirit and scope of the present invention.
[0046] Also in this embodiment, each adaptor 25e features an opening 41 that matches the geometry of the plastic core's perimeter. Similarly, each adaptor 25e includes a circular opening 43 on each side that matches a plastic boss 42 present on each side of the plastic core 26. Once the appropriate adaptor 25e is chosen, an installer inserts its opening 41 around the connector core 26, and snaps each circular opening 43 into the corresponding plastic boss 42. This firmly secures the adaptor 25e and the connector core 26, and results in an effective OBD connector 27 that matches that present in the vehicle. Other means of fastening the adapter to the core could be employed.
[0047] The installer then inserts the set of pins 40 extending from the opposite side of the connector core 26 into a set of cavities 44 within the first connector portion 18 connected to the cable 15 of the wiring harness. The cable 15 in this embodiment includes twenty wires. However, other types of cables may also be employed. After this, each cavity 34 in the plastic core 26 is in electrical contact with a corresponding wire within the cable 15. Upon completion of the installation, corresponding wires within the cable 15 are subsequently in electrical contact with: 1) a unique cavity on the effective OBD connector 27 (present underneath the vehicle's dash); 2) a corresponding cavity in the vehicle's original OBD connector (connected to the male OBD connector 28 of the wiring harness 10); and 3) to a corresponding pin on the telematics device (described in more detail below). In this configuration, the telematics device 20 can receive power and diagnostic data from basically any host vehicle 12, and then transmit this information through a wireless network to an Internet-accessible website as will be discussed in further detail below.
[0048] In addition, in this embodiment, the printed circuit board 30 includes a set of three metallized holes 32 that are insulated from any pins in the plastic core 29, but, following installation, are in electrical contact with a microprocessor in the telematics device 20. During operation, the microprocessor generates data indicating the status of the telematics device 20. The microprocessor can also accept new firmware. During maintenance, a special diagnostic tool plugs into the set of three metallized holes 32 and serially communicates with the microprocessor to either collect data or download new firmware into the device.
[0049] FIG. 3 illustrates in more detail the different configurations of snap-on adaptors 25 that can be used with the wiring harness 10 and telematics device 20 according to one embodiment of the invention. Other means of affixing the adapters 25 to the cores 26 could conceivably be employed. In this embodiment, each adaptor includes a common opening (41 in FIG. 2 ) and circular opening (43 in FIG. 3 ), but otherwise has a unique form factor. As is clear from the figure, the form factors may vary considerably; each is chosen to match that of an OBD connector present in a given vehicle. During installation, a single snap-on adaptor 25i selected from the set of different adaptors 25 connects to the connector core 26 as described above to complete the wiring harness 10. The wiring harness 10 then connects the telematics device 20 to the vehicle as described above. By the way of example, Table 1, below, correlates individual adaptors 25a-h within the set of snap-on adaptors 25 to their corresponding vehicle.
[0050]
| TABLE 1 | |
|---|---|
| snap-on adaptors and their corresponding host vehicles | |
| Adaptor | Host Vehicle |
| 25a | Ford |
| 25b | Toyota, Honda, Chrysler |
| 25c | Toyota, Chrysler |
| 25d | Saturn, General Motors |
| 25e | Mercedes, BMW |
| 25f | Porsche, Audi, Volkswagen |
| 25g | Volvo |
| 25h | Saab |
[0051] FIG. 4 illustrates each of the sixteen cavities 27a-p within the effective OBD connector 27 of this embodiment. As shown in Table 2, below, the cavities may supply power (˜12V), ground, and a serial interface to one of five serial vehicle-communication protocols currently supported by the host vehicle and described above. Through these protocols the connector 27 receives data from the vehicle's ECU that characterize the on-board electrical, mechanical, and emissions systems.
[0052]
| TABLE 2 | |
|---|---|
| cavities within the effective OBD connector and their function | |
| Cavity | Function |
| 27b | J1850+ |
| 27d | Chassis Ground |
| 27e | Signal Ground |
| 27f | CAN High |
| 27g | ISO 9141-2 K Line |
| 27j | J1850− |
| 27n | CAN Low |
| 27o | ISO 9141-2 L Line |
| 27p | Battery Power (~12 V) |
[0053] A version of the wiring harness described above can also be used for heavy-duty trucks. These vehicles are typically not OBD-compliant, and support serial communication protocols (referred to herein as J1708/J1587 and CAN) that are different than those described above for light-duty vehicles. Like light-duty vehicles, however, these serial communication protocols collect diagnostic data, generated from a in-vehicle network of sensors, from the host vehicle's ECU. These data are typically made available through a circular six or nine-pin connector typically located in the truck's interior. Unlike light-duty vehicles, the form factors of these connectors typically do not vary in a vehicle-by-vehicle manner.
[0054] The wiring harness heavy-duty trucks is similar to that described above with reference to FIGS. 1-3 . In this case, however, different core connectors, each having a circular cross section, are required for the six and nine-pin configurations. FIGS. 5A and 5B show, respectively, cross-sections of the nine-pin 50 and six-pin 42 connectors, and the cavities 42a-e, 50a-i within these connectors. Examples of typical pin-outs for the effective connectors for these configurations are described in more detail in Tables 3 and 4, below:
[0055]
| TABLE 3 | |
|---|---|
| cavities and their function for the effective connector for a heavy-duty | |
| truck featuring a nine-pin connector | |
| Cavity | Function |
| 50a | Chassis Ground |
| 50b | Battery Power (~12 V) |
| 50c | CAN High |
| 50d | CAN Low |
| 50e | CAN Shield |
| 50f | J1708+ |
| 50g | J1708− |
| 50h | Proprietary |
| 50i | Proprietary |
[0056]
| TABLE 4 | |
|---|---|
| cavities and their function for the effective connector for a heavy-duty | |
| truck featuring a six-pin connector | |
| Cavity | Function |
| 42a | J1708+ |
| 42b | J1708− |
| 42c | Battery Power (~12 V) |
| 42d | No Standard Function |
| 42e | Chassis Ground |
| 42f | No Standard Function |
[0057] FIG. 6 shows a schematic drawing of a telematics system 52 that uses embodiments of the above-described telematics device 20 and wiring harness 10 to monitor diagnostic and location-based information from a host vehicle 12. The telematics device 20 connects to the wiring harness 10 through a third connector portion 16, and the resulting system is installed in a host vehicle 12 as described above. Specifically, the wiring harness 10 includes a cable 15 that, on one end, features an effective OBD connector 27 that is located under the vehicle's dash 14. This effective OBD connector 27 may populate a slot or other mounting arrangement left behind by the vehicle's original OBD connector 36, which is removed from its original location during installation and connected to a male sixteen-pin connector 28 attached to the wiring harness 10. The vehicle's original connector 36 provides a serial interface to the vehicle's ECU 35.
[0058] During operation, the telematics device 20 retrieves diagnostic data collected from the host vehicle 12, and location-based data from a GPS that collects signals from a constellation 60 of overlying satellites through an airlink 62. The device 20 formats these data in separate packets and transmits them over an airlink 59 to a base station 61 included in a wireless network 54. The packets propagate through the wireless network 54 to a gateway software piece 55 running on a host computer system 57. The host computer system 57 processes and stores information from the packets in a database 63 using the gateway software piece 55. The host computer system 57 additionally hosts a web site 66 that, once accessed, displays the information. A user (e.g. an individual working for a call center) accesses the web site 66 with a secondary computer system 69 through the Internet 67. The host computer system 57 includes a data-processing component 68 that analyzes the location and diagnostic information as described above.
[0059] Other embodiments are also within the scope of the invention. In particular, cables, connectors, and mechanical configurations other than those described above can be used for the wiring harness. For example, the harness can have a ‘Y’ configuration where the effective OBD connector, male OBD connector, and third connector portion are, respectively, at different ends of the ‘Y’. In another configuration, the telematics device can include a pass-through connector so that the device can receive diagnostic data while making the vehicle's OBD connector available to a scan tool during, for example, repairs. When the scan tool 70 is plugged in, the telematics device ‘backs off’ the ECU (i.e., the telematics device temporarily stops accessing data from the ECU) using either firmware or hardware, so that the scan tool 70 can read the diagnostic data.
[0060] FIG. 7 , for example, shows an embodiment as a wiring harness arrangement for connecting a telematics device 704 to a host vehicle, comprising: a plurality of first electrical conductors 702; a first connector 701 electrically coupled to at least some of the first electrical conductors 702 and being configured to be connected to an in-vehicle diagnostic system; and a second connector 703 electrically coupled to at least one of the first electrical conductors 702 and configured to be coupled to the telematics device 704; a plurality of second electrical conductors 705, configured to be connected to the telematics device 704; and a third electrical connector 706 electrically coupled to at least some of the second electrical conductors 705 and being configured to be coupled to a diagnostic scan tool.
[0061] In other embodiments, the wiring harness can include ‘vampire taps’ that connect directly to wires within the vehicle's OBD system. In this case, the original OBD connector within the vehicle is not removed, and the wiring harness therefore lacks an effective OBD connector. Instead, the appropriate wires from the OBD system (e.g., wires providing high and low serial communication) are located and connected to corresponding wires within the wiring harness using the taps. These wires connect directly to the telematics device, and supply diagnostic data that is processed as described above. This embodiment, shown in FIG. 8 , includes a wiring harness arrangement for connecting a telematics device 804 to a host vehicle, comprising: a plurality of conductors 801; a set of vampire taps 802 electrically coupled to at least some of the electrical conductors 801 and being configured to be connected to an in-vehicle diagnostic system; and a first connector 803 electrically coupled to at least one of the electrical conductors 801 and configured to be coupled to the telematics device 804.
[0062] In other embodiments, short-range wireless devices, such as Bluetooth™ or 802.11-based devices, can be used in place of cables to transmit diagnostic and location data to the in-vehicle device. For example, a Bluetooth™ transmitter can be connected to the vehicle's OBD system, and wirelessly transmit diagnostic data to a corresponding Bluetooth™ receiver in the telematics device. The telematics device then transmits these data over a nation-wide wireless network using a conventional wireless transmitter. This embodiment shown in FIG. 9 , features a system for connecting a telematics device 904 to a host vehicle, comprising: a short-range wireless transmitter 901 connected to an in-vehicle diagnostic system 902; and a short-range wireless receiver 903 connected to the telematics device 904 installed in the host vehicle; wherein the transmitter 901 is configured to wirelessly transmit 905 diagnostic data to the receiver 903.
[0063] In still other embodiments, the snap-on adaptors, connector portions, cabling, and pins can have different configurations than those shown above. The telematics system shown in FIG. 6 in vehicle 12 may also be implemented in communication with other hardware and software systems different than or in addition to those shown 61, 54, 55, 57, 63, 66, 67, 52, 69, 60 in that figure. Such other hardware and software systems are described, for example, in the following references, the disclosures of which have been previously incorporated herein by reference: 1) U.S. Pat. No. 6,594,579; 2) U.S. Pat. No. 6,604,033; 3) U.S. Pat. No. 6,611,740; and 4) U.S. Pat. No. 6,636,790.
[0064] In general, it will be apparent to one of ordinary skill in the art that some of the embodiments as described hereinabove may be implemented in many different embodiments of software, firmware, and hardware in the entities illustrated in the figures. The actual software code or specialized control hardware used to implement some of the present embodiments is not limiting of the present invention. Thus, the operation and behavior of the embodiments are described without specific reference to the actual software code or conventional hardware components. The absence of such specific references is feasible because it is clearly understood that artisans of ordinary skill would be able to design software and control hardware to implement the embodiments of the present invention based on the description herein with only a reasonable effort and without undue experimentation.
[0065] It is to be understood that the figures and descriptions of the present invention have been simplified to illustrate elements that are relevant for a clear understanding of the present invention, while eliminating, for purposes of clarity, other elements. Those of ordinary skill in the art will recognize that these and other elements may be desirable. However, because such elements are well known in the art, and because they do not facilitate a better understanding of the present invention, a discussion of such elements is not provided herein.
[0066] In some embodiments of the present invention disclosed herein, a single component can be replaced by multiple components, and multiple components replaced by a single component, to perform a given function or functions. Except where such substitution would not be operative to practice embodiments of the present invention, such substitution is within the scope of the present invention.
Claims
What is claimed is:
1. A method for collecting data relating to a vehicle having a telematics unit which receives at least a portion of the data from an engine control unit, the method comprising:
detecting downloading of the data, wherein the data is downloaded through an on-board diagnostic connector; and
discontinuing receipt of the data by the telematics unit when the downloading is detected.
2. The method of claim 1 wherein the vehicle has an onboard diagnostic connector communicating with the engine control unit and wherein said downloading comprises coupling a scan tool to the onboard diagnostic connector.
3. The method of claim 2 further comprising:
decoupling the scan tool from the onboard diagnostic connector after a desired amount of data has been downloaded to the scan tool; and
enabling the telematics unit to receive data from the engine control unit.
4. A telematics unit having instructions stored thereon which when executed:
receive data from an engine control unit communicating therewith;
detect downloading of data to a scan tool communicating with the engine control unit; and
discontinue receipt of the data upon the detecting the downloading of diagnostic data to the scan tool.
5. A telematics unit comprising:
means for receiving data transmitted by an engine control unit;
means for detecting downloading of data from the engine control unit to a scan tool; and
means for discontinuing receipt of the engine control unit transmitted data by the means for receiving during the downloading of the data to the scan tool.
6. A computer readable medium having instructions stored thereon which when executed by a processor, cause the processor to:
enable a telematics unit to receive data from an engine control unit;
detect when the engine control unit is downloading data to a scan tool; and
discontinue receipt of the engine control unit transmitted data by the telematics unit during the downloading of data from the engine control unit to the scan tool.
Patent Citations (203)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3748894(A) | 1973-07-01 | White et al. | Applicant |
| US4258421(A) | 1981-03-01 | Juhasz et al. | Applicant |
| US4602127(A) | 1986-07-01 | Neely et al. | Applicant |
| US4690475(A) | 1987-09-01 | McElroy | Applicant |
| US4694408(A) | 1987-09-01 | Zaleski | Applicant |
| US4926330(A) | 1990-05-01 | Abe et al. | Applicant |
| US4956777(A) | 1990-09-01 | Cearley et al. | Applicant |
| US5003317(A) | 1991-03-01 | Gray et al. | Applicant |
| US5026293(A) | 1991-06-01 | Wilson | Applicant |
| US5050080(A) | 1991-09-01 | Abe | Applicant |
| US5157610(A) | 1992-10-01 | Asano et al. | Applicant |
| US5223844(A) | 1993-06-01 | Mansell et al. | Applicant |
| US5289378(A) | 1994-02-01 | Miller et al. | Applicant |
| US5343906(A) | 1994-09-01 | Tibbals, III | Applicant |
| US5442553(A) | 1995-08-01 | Parrillo | Applicant |
| US5450321(A) | 1995-09-01 | Crane | Applicant |
| US5463567(A) | 1995-10-01 | Boen et al. | Applicant |
| US5473540(A) | 1995-12-01 | Schmitz | Applicant |
| US5479479(A) | 1995-12-01 | Braitberg et al. | Applicant |
| US5491486(A) | 1996-02-01 | Welles, II et al. | Applicant |
| US5519621(A) | 1996-05-01 | Wortham | Applicant |
| US5532927(A) | 1996-07-01 | Pink et al. | Applicant |
| US5537336(A) | 1996-07-01 | Joyce | Applicant |
| US5550551(A) | 1996-08-01 | Alesio | Applicant |
| US5555498(A) | 1996-09-01 | Berra et al. | Applicant |
| US5574427(A) | 1996-11-01 | Cavallaro | Applicant |
| US5586130(A) | 1996-12-01 | Doyle | Applicant |
| US5619412(A) | 1997-04-01 | Hapka | Applicant |
| US5633645(A) | 1997-05-01 | Day | Applicant |
| US5636122(A) | 1997-06-01 | Shah et al. | Applicant |
| US5671141(A) | 1997-09-01 | Smith et al. | Applicant |
| US5673305(A) | 1997-09-01 | Ross | Applicant |
| US5680328(A) | 1997-10-01 | Skorupski et al. | Applicant |
| US5732074(A) | 1998-03-01 | Spaur et al. | Applicant |
| US5737215(A) | 1998-04-01 | Schricker et al. | Applicant |
| US5739761(A) | 1998-04-01 | Kobayashi | Examiner |
| US5750886(A) | 1998-05-01 | Lambert et al. | Examiner |
| US5754965(A) | 1998-05-01 | Hagenbuch | Applicant |
| US5758300(A) | 1998-05-01 | Abe | Applicant |
| US5774828(A) | 1998-06-01 | Brunts et al. | Applicant |
| US5781101(A) | 1998-07-01 | Stephen et al. | Applicant |
| US5781871(A) | 1998-07-01 | Mezger et al. | Applicant |
| US5797134(A) | 1998-08-01 | McMillan et al. | Applicant |
| US5798647(A) | 1998-08-01 | Martin et al. | Applicant |
| US5808907(A) | 1998-09-01 | Shetty et al. | Applicant |
| US5815071(A) | 1998-09-01 | Doyle | Applicant |
| US5828585(A) | 1998-10-01 | Welk et al. | Applicant |
| US5844473(A) | 1998-12-01 | Kaman | Applicant |
| US5850209(A) | 1998-12-01 | Lemke et al. | Applicant |
| US5884202(A) | 1999-03-01 | Arjomand | Applicant |
| US5928292(A) | 1999-07-01 | Miller et al. | Applicant |
| US5941918(A) | 1999-08-01 | Blosser | Applicant |
| US5964821(A) | 1999-10-01 | Brunts et al. | Applicant |
| US5987377(A) | 1999-11-01 | Westerlage et al. | Applicant |
| US6020654(A) | 2000-02-01 | Chutorash | Applicant |
| US6064970(A) | 2000-05-01 | McMillan et al. | Applicant |
| US6088648(A) | 2000-07-01 | Shah et al. | Applicant |
| US6104988(A) | 2000-08-01 | Klarer | Applicant |
| US6140969(A) | 2000-10-01 | Lindenmeier et al. | Applicant |
| US6141611(A) | 2000-10-01 | Mackey et al. | Applicant |
| US6141710(A) | 2000-10-01 | Miesterfeld | Applicant |
| US6144916(A) | 2000-11-01 | Wood, Jr. et al. | Applicant |
| US6154658(A) | 2000-11-01 | Caci | Applicant |
| US6167426(A) | 2000-12-01 | Payne et al. | Applicant |
| US6202008(B1) | 2001-03-01 | Beckert et al. | Applicant |
| US6208948(B1) | 2001-03-01 | Klingler et al. | Applicant |
| US6225898(B1) | 2001-05-01 | Kamiya et al. | Applicant |
| US6236933(B1) | 2001-05-01 | Lang | Applicant |
| US6240295(B1) | 2001-05-01 | Kennedy, III et al. | Applicant |
| US6240365(B1) | 2001-05-01 | Bunn | Applicant |
| US6246935(B1) | 2001-06-01 | Buckley | Applicant |
| US6263268(B1) | 2001-07-01 | Nathanson | Applicant |
| US6278921(B1) | 2001-08-01 | Harrison et al. | Applicant |
| US6285953(B1) | 2001-09-01 | Harrison et al. | Applicant |
| US6292718(B2) | 2001-09-01 | Staiger | Applicant |
| US6295492(B1) | 2001-09-01 | Lang et al. | Applicant |
| US6338152(B1) | 2002-01-01 | Fera et al. | Applicant |
| US6339736(B1) | 2002-01-01 | Moskowitz et al. | Applicant |
| US6339745(B1) | 2002-01-01 | Novik | Applicant |
| US6346876(B1) | 2002-02-01 | Flick | Applicant |
| US6354868(B1) | 2002-03-01 | Korczynski et al. | Applicant |
| US6356205(B1) | 2002-03-01 | Salvo et al. | Applicant |
| US6356823(B1) | 2002-03-01 | Iannotti et al. | Applicant |
| US6362730(B2) | 2002-03-01 | Razavi et al. | Applicant |
| US6400701(B2) | 2002-06-01 | Lin et al. | Applicant |
| US6405106(B1) | 2002-06-01 | Sheth et al. | Applicant |
| US6408232(B1) | 2002-06-01 | Cannon et al. | Applicant |
| US6429773(B1) | 2002-08-01 | Schuyler | Applicant |
| US6442460(B1) | 2002-08-01 | Larson et al. | Applicant |
| US6459988(B1) | 2002-10-01 | Fan et al. | Applicant |
| US6477452(B2) | 2002-11-01 | Good | Applicant |
| US6480170(B1) | 2002-11-01 | Langley et al. | Applicant |
| US6487479(B1) | 2002-11-01 | Nelson | Applicant |
| US6487494(B2) | 2002-11-01 | Odinak et al. | Applicant |
| US6487717(B1) | 2002-11-01 | Brunemann et al. | Applicant |
| US6496777(B2) | 2002-12-01 | Tennison et al. | Applicant |
| US6502030(B2) | 2002-12-01 | Hilleary | Applicant |
| US6505106(B1) | 2003-01-01 | Lawrence et al. | Applicant |
| US6507786(B2) | 2003-01-01 | Flick | Applicant |
| US6512466(B2) | 2003-01-01 | Flick | Applicant |
| US6522267(B2) | 2003-02-01 | Flick | Applicant |
| US6526335(B1) | 2003-02-01 | Treyz et al. | Applicant |
| US6526460(B1) | 2003-02-01 | Dauner et al. | Applicant |
| US6529159(B1) | 2003-03-01 | Fan et al. | Applicant |
| US6552682(B1) | 2003-04-01 | Fan | Applicant |
| US6556889(B2) | 2003-04-01 | Rudick et al. | Applicant |
| US6556905(B1) | 2003-04-01 | Mittelsteadt et al. | Applicant |
| US6564127(B1) | 2003-05-01 | Bauerle et al. | Applicant |
| US6564128(B2) | 2003-05-01 | Baird et al. | Applicant |
| US6580916(B1) | 2003-06-01 | Weisshaar et al. | Applicant |
| US6594576(B2) | 2003-07-01 | Fan et al. | Applicant |
| US6594579(B1) | 2003-07-01 | Lowrey et al. | Applicant |
| US6604032(B1) | 2003-08-01 | Möller | Applicant |
| US6604033(B1) | 2003-08-01 | Banet et al. | Applicant |
| US6604038(B1) | 2003-08-01 | Lesesky et al. | Applicant |
| US6609051(B2) | 2003-08-01 | Fiechter et al. | Applicant |
| US6611686(B1) | 2003-08-01 | Smith et al. | Applicant |
| US6611739(B1) | 2003-08-01 | Harvey et al. | Applicant |
| US6611740(B2) | 2003-08-01 | Lowrey et al. | Applicant |
| US6611755(B1) | 2003-08-01 | Coffee et al. | Applicant |
| US6636790(B1) | 2003-10-01 | Lightner et al. | Applicant |
| US6662091(B2) | 2003-12-01 | Wilson et al. | Applicant |
| US6664922(B1) | 2003-12-01 | Fan | Applicant |
| US6671617(B2) | 2003-12-01 | Odinak et al. | Applicant |
| US6675081(B2) | 2004-01-01 | Shuman et al. | Applicant |
| US6678614(B2) | 2004-01-01 | McCarthy et al. | Applicant |
| US6687587(B2) | 2004-02-01 | Kacel | Applicant |
| US6694234(B2) | 2004-02-01 | Lockwood et al. | Applicant |
| US6701233(B2) | 2004-03-01 | Namaky et al. | Applicant |
| US6718425(B1) | 2004-04-01 | Pajakowski et al. | Applicant |
| US6732031(B1) | 2004-05-01 | Lowrey et al. | Applicant |
| US6732032(B1) | 2004-05-01 | Lowrey et al. | Applicant |
| US6738697(B2) | 2004-05-01 | Breed | Applicant |
| US6751452(B1) | 2004-06-01 | Kupczyk et al. | Applicant |
| US6751479(B1) | 2004-06-01 | Knight | Applicant |
| US6754485(B1) | 2004-06-01 | Obradovich et al. | Applicant |
| US6757262(B1) | 2004-06-01 | Weisshaar et al. | Applicant |
| US6766233(B2) | 2004-07-01 | Odinak et al. | Applicant |
| US6795017(B1) | 2004-09-01 | Puranik et al. | Applicant |
| US6801841(B2) | 2004-10-01 | Tabe | Applicant |
| US6809659(B2) | 2004-10-01 | Flick et al. | Applicant |
| US6812888(B2) | 2004-11-01 | Drury et al. | Applicant |
| US6832140(B2) | 2004-12-01 | Fan et al. | Applicant |
| US6832175(B2) | 2004-12-01 | Adachi et al. | Applicant |
| US6836708(B2) | 2004-12-01 | Tripathi | Applicant |
| US6845362(B2) | 2005-01-01 | Furuta et al. | Applicant |
| US6862524(B1) | 2005-03-01 | Nagda et al. | Applicant |
| US6867733(B2) | 2005-03-01 | Sandhu et al. | Applicant |
| US6879894(B1) | 2005-04-01 | Lightner et al. | Applicant |
| US6882313(B1) | 2005-04-01 | Fan et al. | Applicant |
| US6889064(B2) | 2005-05-01 | Baratono et al. | Applicant |
| US6889135(B2) | 2005-05-01 | Curatolo et al. | Applicant |
| US6892131(B2) | 2005-05-01 | Coffee et al. | Applicant |
| US6895444(B1) | 2005-05-01 | Weisshaar et al. | Applicant |
| US6907330(B2) | 2005-06-01 | Eisenmann et al. | Applicant |
| US6922566(B2) | 2005-07-01 | Puranik et al. | Applicant |
| US6928348(B1) | 2005-08-01 | Lightner et al. | Applicant |
| US6941202(B2) | 2005-09-01 | Wilson et al. | Applicant |
| US6944121(B1) | 2005-09-01 | Weste et al. | Applicant |
| US6947760(B2) | 2005-09-01 | Weisshaar et al. | Applicant |
| US6947816(B2) | 2005-09-01 | Chen | Applicant |
| US6956501(B2) | 2005-10-01 | Kitson | Applicant |
| US6957133(B1) | 2005-10-01 | Hunt et al. | Applicant |
| US6970703(B2) | 2005-11-01 | Fuchs et al. | Applicant |
| US6973324(B2) | 2005-12-01 | Weisshaar et al. | Applicant |
| US6988033(B1) | 2006-01-01 | Lowrey et al. | Applicant |
| US7016774(B2) | 2006-03-01 | Barber et al. | Applicant |
| US7034710(B2) | 2006-04-01 | Falada et al. | Applicant |
| US7062375(B2) | 2006-06-01 | Hatano | Applicant |
| US7072668(B2) | 2006-07-01 | Chou | Applicant |
| US7092803(B2) | 2006-08-01 | Kapolka et al. | Applicant |
| US7113127(B1) | 2006-09-01 | Banet et al. | Applicant |
| US7155321(B2) | 2006-12-01 | Bromley et al. | Applicant |
| US7174243(B1) | 2007-02-01 | Lightner et al. | Applicant |
| US7225065(B1) | 2007-05-01 | Hunt et al. | Applicant |
| US7228211(B1) | 2007-06-01 | Lowrey et al. | Applicant |
| US2001/0018628(A1) | 2001-08-01 | Jenkins et al. | Applicant |
| US2001/0034609(A1) | 2001-10-01 | Dovolis | Applicant |
| US2002/0016655(A1) | 2002-02-01 | Joao | Applicant |
| US2002/0065698(A1) | 2002-05-01 | Schick et al. | Applicant |
| US2002/0073170(A1) | 2002-06-01 | Hoffman et al. | Applicant |
| US2002/0078458(A1) | 2002-06-01 | Furon et al. | Applicant |
| US2002/0118222(A1) | 2002-08-01 | Fogarty | Applicant |
| US2002/0140545(A1) | 2002-10-01 | Nietupski et al. | Applicant |
| US2002/0150050(A1) | 2002-10-01 | Nathanson | Applicant |
| US2002/0171650(A1) | 2002-11-01 | Prabhakaran | Applicant |
| US2002/0173885(A1) | 2002-11-01 | Lowrey et al. | Applicant |
| US2003/0093199(A1) | 2003-05-01 | Mavreas | Applicant |
| US2003/0130005(A1) | 2003-07-01 | Weisshaar et al. | Applicant |
| US2003/0130774(A1) | 2003-07-01 | Tripathi et al. | Applicant |
| US2003/0147534(A1) | 2003-08-01 | Ablay et al. | Applicant |
| US2004/0023645(A1) | 2004-02-01 | Olsen et al. | Applicant |
| US2004/0044454(A1) | 2004-03-01 | Ross et al. | Applicant |
| US2004/0075539(A1) | 2004-04-01 | Savoie et al. | Applicant |
| US2004/0196182(A1) | 2004-10-01 | Unnold | Applicant |
| US2005/0131729(A1) | 2005-06-01 | Melby et al. | Applicant |
| US2005/0144318(A1) | 2005-06-01 | Chang | Applicant |
| US2007/0069947(A1) | 2007-03-01 | Banet et al. | Applicant |
| CA2133673(A1) | 1994-10-01 | Applicant | |
| CA2372900(A1) | 2003-05-01 | Applicant | |
| EP816820(A2) | 1998-01-01 | Applicant | |
| WO/40038(A2) | 2000-07-01 | Applicant | |
| WO/79727(A2) | 2000-12-01 | Applicant |
Non-Patent Literature (28)
- Disclosed Anonymously, Abstract, “Vehicle Diagnostic Performed via the Internet,” RD-42261; Research Disclosure, p. 815, Jun. 1999.Applicant
- Wilson et al., “Modular System for Multi-Parameter In-Line Machine Fluid Analysis,” Technology Showcase 2000, pp. 78-85, Apr. 3-6, 2000.Applicant
- Definition of “Chipset”, printed from http://en.wikipedia.org/wiki/Chipset, Internet site, website accessed on Feb. 23, 2006, 1 page.Applicant
- Di Genova et al., “Incorporation of Wireless Communications into Vehicle On-Board Diagnostic (OBD) Systems.” Report No. SR00-01-03, prepared for California Air Resources Board by Sierra Research, Inc., Jan. 18, 2000, 172 pages.Applicant
- 40 CFR 51, Ch. I (Jul. 1, 2001 Edition), pp. 130-481.Applicant
- 40 CFR 85, Ch. I (Jul. 1, 2001 Edition), 143 pages.Applicant
- Motorola, Inc., “Automotive ISO 9141 Serial Link Driver,” Document MC333199/D, 1996, 12 pages.Applicant
- D. John Oliver, Intel Corporation, “Implementing the J 1850 Protocol,” 15 pages.Applicant
- “I2C,” printed from http://www.nxp.com, Internet site, (associated with www.philipslogic.com), website accessed on Jun. 8, 2006, 3 pages.Applicant
- “Qualcomm Chipset Solutions,” printed from http://www.qualcomm.com, Internet site, website accessed on Jun. 8, 2006, 48 pages.Applicant
- U.S. Appl. No. 09/776,083, filed Feb. 1, 2001.Applicant
- U.S. Appl. No. 10/301,010, filed Nov. 21, 2002.Applicant
- U.S. Appl. No. 10/440,596, filed May 19, 2003.Applicant
- U.S. Appl. No. 10/614,665, filed Jul. 7, 2003.Applicant
- U.S. Appl. No. 10/626,779, filed Jul. 24, 2003.Applicant
- U.S. Appl. No. 10/626,810, filed Jul. 24, 2003.Applicant
- U.S. Appl. No. 10/632,033, filed Jul. 31, 2003.Applicant
- U.S. Appl. No. 10/823,478, filed Apr. 13, 2004.Applicant
- U.S. Appl. No. 11/654,213, filed Jan. 17, 2007.Applicant
- U.S. Appl. No. 11/784,053, filed Apr. 5, 2007.Applicant
- U.S. Appl. No. 11/788,930, filed Apr. 23, 2007.Applicant
- U.S. Appl. No. 11/796,372, filed Apr. 27, 2007.Applicant
- Definition of “Chipset” printed from Webopedia, Internet site, Oct. 31, 2002, 3 pages.Applicant
- Notice of Disclosure by HTI IP, LLC of Asserted Claims and Infringement Contentions and Document Production Accompanying Disclosure (Attachments: #1 Appendix Chart of Asserted Claims 6,636,790, #2 Appendix Chart of Asserted Claims 6,372,031, #3 Appendix Chart of Asserted Claims 6,611,740, 6:07-CV-00466-LED, entered Feb. 11, 2008, 76 pages.Applicant
- U.S. Appl. No. 11/948,473 and Preliminary Amendment, filed Nov. 30, 2007.Applicant
- U.S. Appl. No. 11/948,489 and Preliminary Amendment, filed Nov. 30, 2007.Applicant
- U.S. Appl. No. 11/948,496 and Preliminary Amendment, filed Nov. 30, 2007.Applicant
- U.S. Appl. No. 11/948,515 and Preliminary Amendment, filed Nov. 30, 2007.Applicant