US 7,532,962 B1Grant
Internet-based vehicle-diagnostic system
Issue Date:2009-05-12
•8 Claims
•12 Drawing Sheets
Abstract
The invention provides a system for monitoring a vehicle that includes a wireless appliance in electrical contact with an in-vehicle computer. The wireless appliance features: 1) a data-collection component that supports communication software that collects diagnostic data from the computer; and 2) a data-transmission component, in electrical communication with the data-collection electronics, configured to transmit an outgoing data packet comprising the diagnostic data over a network and receive over the same network an incoming data packet that modifies the communication software. The wireless appliance communicates with a host computer system that is configured to: 1) receive the outgoing data packet from the network; 2) process the outgoing data packet to generate a set of vehicle diagnostic data; 3) host a web site on the Internet that displays the vehicle diagnostic data; and 4) send out the incoming data packet over the same network to modify the communication software.
Metadata
Assignee
- HT IIP, LLC
Inventors
- Larkin Hill Lowrey
- Matthew J. Banet
- Bruce Lightner
- Diego Borrego
- Chuck Myers
- Wade Williams
Application Information
Application Number:US 11/948,489
Filing Date:2007-11-30
Priority Date:2001-03-14
Art Unit:3664
Classifications
IPC:
G06F17/00G06F19/00G01M17/00
Patent Drawings (12 sheets)
Description
Priority Claim
[0001] This application is a divisional of U.S. application Ser. No. 10/626,810 filed Jul. 24, 2003, which is incorporated herein by reference and is a continuation of U.S. application Ser. No. 09/808,690 filed Mar. 14, 2001, now issued as U.S. Pat. No. 6,611,740, and also incorporated herein by reference.
Technical Field
[0002] The present invention relates to use of an internet-based system for diagnosing a vehicle's performance.
Background
[0003] The Environmental Protection Agency (EPA) requires vehicle manufacturers to install on-board diagnostics (OBD-II) for monitoring light-duty automobiles and trucks beginning with model year 1996. OBD-II systems (e.g., microcontrollers and sensors) monitor the vehicle's electrical and mechanical systems and generate data that are processed by a vehicle's engine control unit (ECU) to detect any malfunction or deterioration in the vehicle's performance. Most ECUs transmit status and diagnostic information over a shared, standardized electronic buss in the vehicle. The buss effectively functions as an on-board computer network with many processors, each of which transmits and receives data. The primary computers in this network are the vehicle's electronic-control module (ECM) and power-control module (PCM). The ECM typically monitors engine functions (e.g., the cruise-control module, spark controller, exhaust/gas recirculator), while the PCM monitors the vehicle's power train (e.g., its engine, transmission, and braking systems). Data available from the ECM and PCM include vehicle speed, fuel level, engine temperature, and intake manifold pressure. In addition, in response to input data, the ECU also generates 5-digit ‘diagnostic trouble codes’ (DTCs) that indicate a specific problem with the vehicle. The presence of a DTC in the memory of a vehicle's ECU typically results in illumination of the ‘Service Engine Soon’ light present on the dashboard of most vehicles.
[0004] Data from the above-mentioned systems are made available through a standardized, serial 16-cavity connector referred to herein as an ‘OBD-II connector’. The OBD-II-connector typically lies underneath the vehicle's dashboard. When a vehicle is serviced, data from the vehicle's ECM and/or PCM is typically queried using an external engine-diagnostic tool (commonly called a ‘scan tool’) that plugs into the OBD-II connector. The vehicle's engine is turned on and data are transferred from the engine computer, through the OBD-II connector, and to the scan tool. The data are then displayed and analyzed to service the vehicle. Scan tools are typically only used to diagnose stationary vehicles or vehicles running on a dynamometer.
[0005] Some vehicle manufacturers also include complex electronic systems in their vehicles to access and analyze some of the above-described data. For example, General Motors includes a system called ‘On-Star’ in some of their high-end vehicles. On-Star collects and transmits data relating to these DTCs through a wireless network. On-Star systems are not connected through the OBD-II connector, but instead are wired directly to the vehicle's electronic system. This wiring process typically takes place when the vehicle is manufactured.
Summary
[0006] Embodiments of the invention can provide a wireless, interact-based system for monitoring a vehicle. For example, embodiments of the invention can access data from a vehicle, analyze it, and make it available to organizations (e.g. an automotive dealership or service center) over the internet so that the vehicle's performance can be analyzed accurately and in real-time. Data are accessed through the same OBD-II connector used by conventional scan tools. In this way, the invention collects data similar to those collected by scan tools; only they are collected in real-time while the vehicle is actually being driven. The invention also provides an Internet-based web site to view these data. The web site also includes functionality to modify the type of data being collected, e.g. the type of diagnostic data or the frequency at which it is collected. The data can be collected and viewed over the Internet without having to bring the vehicle in for service. The data include, for example, DTCs and mechanical and electrical data stored in the vehicle's engine computer.
[0007] In one aspect, the invention features a system for monitoring operational characteristics of a vehicle. The system includes a computer in the vehicle, and a wireless appliance in electrical contact with the computer. The wireless appliance includes a data transmission/receiving component, also known as a wireless communication component, configured to transmit data associated with the operational characteristics over a network to a host computer system, and to receive over the network data from the host computer system.
[0008] In another aspect, the invention features a device for monitoring operational characteristics of a vehicle. The device includes a wireless appliance including a data transmission/receiving component configured to communicate data associated with the operational characteristics over a network to a host computer.
[0009] In another aspect, the invention features a device for monitoring operational characteristics of a vehicle. The device includes a wireless appliance including a data transmission/receiving component configured to receive data associated with the operational characteristics over a network to a host computer.
[0010] In a further aspect, the invention features a system for monitoring operational characteristics of a vehicle. The system includes a host computer and a wireless appliance including a data transmission/receiving component configured to communicate data associated with the operational characteristics over a network to a host computer. In some embodiments, the wireless appliance is in the vehicle. In certain embodiments, the host computer is external to the vehicle.
[0011] In one aspect, the invention features a system for monitoring operational characteristics of a vehicle. The system includes a host computer and a wireless appliance including a data transmission/receiving component configured to receive data associated with the operational characteristics over a network to a host computer. In some embodiments, the wireless appliance is in the vehicle. In certain embodiments, the host computer is external to the vehicle.
[0012] Embodiments of the invention can include one or more of the following features and/or advantages.
[0013] The ‘wireless appliance’ used in the above-described invention features a data-transmitting component (e.g. a radio or cellular modem) that sends out the data packet over an existing wireless network (e.g., Cingular's Mobitex network). Such a wireless appliance is described in the application WIRELESS DIAGNOSTIC SYSTEM FOR VEHICLES, filed Feb. 1, 2001, the contents of which are incorporated herein by reference.
[0014] In embodiments, the communication software supported by the data-collection component features a schema component that identifies the diagnostic data to be collected from the vehicle's computer. The schema component features an address that describes a location of a diagnostic datum in the vehicle's computer memory. It can also describe a time or frequency that the data-collection component collects data from the vehicle's computer, or a time or frequency that the data-transmission component transmits an outgoing data packet. The schema component is typically an ASCII or binary data file that is configured to be processed by the communication software.
[0015] In the above-mentioned description, the term ‘supported’ means that an executable version of the communication software can run as a computer program on a microprocessor, microcontroller, or comparable, semiconductor-based device resident on the data-collection component.
[0016] The host computer system typically features at least one web-hosting computer that hosts the web site, and at least one, separate gateway computer that receives the outgoing data packet and sends the incoming data packet. In this embodiment the web site features a first web page that displays at least a single vehicle diagnostic datum. For example, the first web page can include data fields describing: i) a name of the diagnostic datum; ii) units corresponding to the diagnostic datum; and iii) a numerical value corresponding to the diagnostic datum. Multiple sets of diagnostic data, each received by the host computer system at a unique time and date, can also be displayed on the web page. The page can also include a graphical representation of the sets of diagnostic data, e.g. a time-dependent plot of the data.
[0017] In typical applications the set of diagnostic data includes at least one of the following: diagnostic trouble codes, vehicle speed, fuel level, fuel pressure, miles per gallon, engine RPM, mileage, oil pressure, oil temperature, tire pressure, tire temperature, engine coolant temperature, intake-manifold pressure, engine-performance tuning parameters, alarm status, accelerometer status, cruise-control status, fuel-injector performance, spark-plug timing, and a status of an anti-lock braking system.
[0018] In other embodiments the web site further includes a login web page, in communication with a database component, where a user enters a user name and password. The database component is configured to verify if the user is associated with multiple vehicles. If this is the case, the web site includes a second web page that displays vehicle diagnostic data corresponding to each vehicle.
[0019] In still other embodiments the web site includes a third web page that features a mechanism for sending the incoming data packet over the network. For example, the third web page can include a mechanism for selecting a new schema wherein a list of parameters is provided, each of which can be extracted from the vehicle's computer.
[0020] The gateway computer that receives the outgoing data packet and sends the incoming data packet is connected to the network, typically through an Internet-based connection or a digital communication line.
[0021] The system can also include a secondary computer system that connects to the host computer system through the Internet to display the web site. Alternatively, the system includes a hand-held device, e.g. a cellular telephone or personal digital assistant, which connects to the host computer system through the Internet. The host computer system can also be configured to send an electronic mail message that includes all or part of the vehicle diagnostic data.
[0022] In other embodiments, the wireless appliance is configured to send an outgoing data packet that indicates a location of a transmitting base station. In this case, the host computer system includes software that analyzes this location to determine an approximate location of the vehicle, which can then be displayed on a web page.
[0023] In the above-described method, the term “airlink” refers to a standard wireless connection (e.g., a connection used for wireless telephones or pagers) between a transmitter and a receiver. This term describes the connection between a data-transmission component and the wireless network that supports data transmitted by this component. Also in the above-described method, the ‘generating’ and ‘transmitting’ steps can be performed at any time and with any frequency, depending on the diagnoses being performed. For a ‘real-time’ diagnoses of a vehicle's engine performance, for example, the steps may be performed at rapid time or mileage intervals (e.g., several times each minute, or every few miles). Alternatively, other diagnoses (e.g. an emissions or ‘smog’ check) may require the steps to be performed only once each year or after a large number of miles are driven. Alternatively, the vehicle may be configured to automatically perform these steps at predetermined or random time intervals. As described in detail below, the transmission frequency can be changed in real time by downloading a new ‘schema’ to the wireless appliance through the wireless network.
[0024] The term ‘web page’ refers to a standard, single graphical user interface or ‘page’ that is hosted on the Internet or world-wide web. Web pages typically include: 1) a ‘graphical’ component for displaying a user interface (typically written in a computer language called ‘HTML’ or hypertext mark-up language); an ‘application’ component that produces functional applications, e.g. sorting and customer registration, for the graphical functions on the page (typically written in, e.g., C++ or java); and a database component that accesses a relational database (typically written in a database-specific language, e.g. SQL*Plus for Oracle databases). A ‘web site’ typically includes multiple web pages, many of which are ‘linked’ together, that are accessed through a series of ‘mouse clicks’.
[0025] The invention has many advantages. In particular, wireless transmission of data from a vehicle, followed by analysis and display of these data using a web site hosted on the internet, makes it possible to diagnose the performance of a vehicle in real-time from virtually any location that has interact access. This ultimately means the problems with the vehicle can be efficiently diagnosed, and in some cases predicted before they actually occur. Moreover, data from the vehicle can be queried and analyzed while the vehicle is actually in use to provide a relatively comprehensive diagnosis that is not possible using a conventional scan tool. An internet-based system for vehicle diagnoses can also be easily updated and made available to a large group of users simply by updating software on the web site. In contrast, a comparable updating process for a series of scan tools can only be accomplished by updating the software on each individual scan tool. This, of course, is time-consuming, inefficient, and expensive, and introduces the possibility that many scan tools within a particular product line will not have the very latest software.
[0026] The wireless appliance used to access and transmit the vehicle's data is small, low-cost, and can be easily installed in nearly every vehicle with an OBD-II connector in a matter of minutes. It can also be easily transferred from one vehicle to another, or easily replaced if it malfunctions.
[0027] The wireless appliance can also collect data that is not accessible using a scan tool. For example, data that indicates a vehicles performance can be collected while the vehicle is actually driven. For example, it may be required to collect data while a vehicle is driving up a hill or pulling a load. Scan tools, in contrast, can only collect data from a stationary vehicle in a service bay. Service technicians using the wireless appliance, for example, can analyze DTCs and diagnostic data while the vehicle is being driven. The system described herein also makes data available in real-time, thereby allowing the technicians to order parts and schedule resources for service appointments before the vehicle is actually brought into the dealership.
[0028] Moreover, software schemas that update the type or frequency of the vehicle's data can be directly downloaded to specific wireless appliances or groups of wireless appliances (corresponding, e.g., to a fleet of vehicles or a group of vehicles having the same year, make, or model). This makes it possible to collect data that specifically elucidates a problem with the vehicle that may occur only under certain driving-conditions.
[0029] The resulting data, of course, have many uses for automotive dealerships, vehicle-service organizations, vehicle-renting firms, insurance companies, vehicle owners, organizations that monitor emission performance (e.g., the EPA), manufacturers of vehicles and related parts, survey organizations (e.g., J. D. Power) and vehicle service centers. In general, these data yield information that benefits the consumer, vehicle and parts manufacturers, vehicle service centers, and the environment.
[0030] These and other advantages of the invention are described in the following detailed disclosure and in the claims.
Description of the Drawings
[0031] The features and advantages of the present invention can be understood by reference to the following detailed description taken with the drawings, in which:
[0032] FIG. 1 is a schematic drawing of system of the invention featuring a single vehicle transmitting data across an airlink to an Internet-accessible host computer system;
[0033] FIG. 2 is a flow chart describing a method used by the system of FIG. 1 to diagnose vehicles;
[0034] FIG. 3 is a schematic drawing of the system of the invention featuring multiple vehicles, each transmitting data across an airlink to an Internet-accessible host computer system;
[0035] FIG. 4 is a schematic drawing of a web site with a login process that renders a series of web pages associated with either a dealer or customer interface;
[0036] FIG. 5 is a screen capture of a web page from the web site of FIG. 4 that shows a list of customers corresponding to a single dealership;
[0037] FIG. 6 is a screen capture of a web page related to the web page of FIG. 5 that shows diagnostic data for a customer's vehicle; and
[0038] FIG. 7 is a screen capture of a web page from the web site of FIG. 1 that shows several time-dependent sets of diagnostic data from a customer's vehicle.
Detailed Description
[0039] FIG. 1 shows a schematic drawing of an Internet-based vehicle-diagnostic system 2 according to the invention. The system 2 measures diagnostic data from a vehicle 12 and transmits it over an airlink 9 to a web site 6 accessible through the Internet 7. The system 2 functions in a bi-directional manner, i.e. in addition to receiving data from a vehicle, a user logged onto the web site 6 can specifically select the diagnostic data to be measured and the frequency at which it is measured. These properties are sent through the airlink 9 to the wireless appliance 13 that re-measures the diagnostic data from the vehicle 12. In this way, the invention functions effectively as an Internet-based ‘scan tool’ that diagnoses any vehicle that includes a wireless appliance. The host vehicle can be diagnosed at any time it is being driven using an Internet-accessible web site.
[0040] The wireless appliance 13 disposed within the vehicle 12 collects diagnostic data from the vehicle's engine computer 15. The engine computer 15 retrieves data stored in its memory and sends it along a cable 16 to the wireless appliance 13. The appliance 13 typically connects to the OBD-II connector located under the dash in all vehicles manufactured after 1996. It includes a data-collection component (not shown in the figure) that formats the data in a packet and then passes the packet to a data-transmission/receiving component, also known as a wireless communication component, which sends it through a cable 17 to an antenna 14. To generate the data, the wireless appliance 13 queries the vehicle's computer 15 at a first time interval (e.g. every 20 seconds), and transmits a data set at a longer time interval (e.g. every 10 minutes). These time intervals are specified in a data-collection ‘schema’, described in more detail below.
[0041] The antenna typically rests in the vehicle's shade band, disposed just above the dashboard. The antenna 14 radiates the data packet over the airlink 9 to a base station 11 included in a wireless network 4. A host computer system 5 connects to the wireless network 4 and receives the data packets. The host computer system 5, for example, may include multiple computers, software pieces, and other signal-processing and switching equipment, such as routers and digital signal processors. Data are typically transferred from the wireless network 4 to host computer system 5 through a TCP/IP-based connection, or with a dedicated digital leased line (e.g., a frame-relay circuit or a digital line running an X.25 protocol). The host computer system 5 also hosts a web site 6 using conventional computer hardware (e.g. computer servers for a database and the web site) and software (e.g., web server and database software). A user accesses the web site 6 through the Internet 7 from a secondary computer system 8. The secondary computer system 8, for example, may be located in an automotive service center.
[0042] The wireless appliance that provides diagnostic data to the web site is described in more detail in WIRELESS DIAGNOSTIC SYSTEM FOR VEHICLES, filed Feb. 1, 2001, the contents of which have been previously incorporated by reference. The appliance transmits a data packet that contains information of its status, an address describing its destination, an address describing its origin, and a ‘payload’ that contains the above-described diagnostic data from the vehicle, or a schema from the web site. These data packets are transmitted over conventional wireless network, such as Cingular's Mobitex network.
[0043] FIG. 2 shows a method 21 describing how the system 2 in FIG. 1 typically operates. As described above, the wireless appliance includes a data-collection component that, in turn, includes a microcontroller that has software and a data-collection ‘schema’ loaded in the microcontroller's memory. The schema is essentially a ‘map’ that describes the data that the wireless appliance collects from the vehicle's engine computer, and its corresponding location in the computer's memory. A schema specific to a given type of vehicle is typically loaded onto the microcontroller before the wireless appliance is installed in the vehicle (step 22 in FIG. 2 ). During operation, the appliance communicates with the vehicle's engine computer as described above (step 23). The appliance collects diagnostic data defined by the schema, formats these data in a data packet, and then sends an outgoing packet over the airlink to a wireless network (step 24). The network transfers the data packet to the host computer system as described above (step 25). There, the host computer system analyzes the data packet using a ‘map’ that corresponds to the schema to generate a data set (step 26). Every schema has a corresponding map. The map includes, for example, a list of the collected data, an acronym and unit for each datum. The data set, acronym, and units are then displayed on the web site (step 28) where they can be viewed by any ‘registered’ user (i.e., a user with a username and corresponding password) with Internet connectivity.
[0044] In one mode of operation, a technician working at a vehicle-service center logs into the web site and analyzes the data set corresponding to a particular vehicle to diagnose a potential mechanical or electrical problem (step 30). Specific web pages that display the data set are shown in FIGS. 5-7 , below. Based on the analysis, the technician may decide that additional data are required, or that data need to be collected and transmitted at a higher or lower frequency. In this case the technician uses the web site to select a new schema (step 32) and then sends an incoming data packet that includes a new schema over the wireless network to the wireless appliance included in the vehicle being diagnosed (step 34). In typical applications, the vehicle is specifically addressed using a serial number that corresponds to the data-transmitting component. This serial number is typically an 8 or 10-digit number that functions effectively as a ‘phone number’ corresponding to the data-transmitting component. This number is included in the data packet, and is used by the wireless network to transfer the packet to the host vehicle (step 35). The host vehicle receives the packet and processes it to extract the new data-collection schema (step 36). The wireless appliance uses the updated schema to extract a revised set of data from the vehicle's engine computer, or send out data at a revised frequency (step 38). In other applications, the new schema can be used to query a set of data that is relevant to a DTC registered by the vehicle, or to ‘clear’ a DTC when it is deemed to no longer be problematic. Once these data are collected, the method 21 can then be repeated as described above to further diagnose the vehicle.
[0045] The above-described system is designed to work with multiple vehicles and multiple secondary computer systems, each connected to the web site through the Internet. FIG. 3 illustrates this point, showing a system 20, similar to the system 2 of FIG. 1 , used to diagnose a set of vehicles 12a-12c. The system 20 operates similarly as that described above: a wireless appliance 13a-13c disposed in each vehicle collects data from the vehicles' respective engine computers 15a-15c, formats these data into data packets, and then sends the data packets using antennae 14a-14c over a series of airlinks 9a-9c to a base stations 11a-11b featured in a wireless network 4. Each vehicle may include a unique schema. In this case, two vehicles 12a, 12b send their respective data packets to a single base station 11b, while a single vehicle 12c sends its data packet to a single base station 11a. The number and location of the base stations depends on the wireless network; in the Mobitex network there is typically one base station per zip code in most major cities. Once the data packets are received, the wireless network 4 routes them to the host computer system 5. They are then processed with a corresponding map and consequently formatted as a series of data sets and displayed on the web site 6. A series of secondary computer systems 8a-8c, 8n view the web site using separate connections over the Internet 7a-7c, 7n. Users of the secondary computer systems 8a-8c, 8n associated with organizations containing a series of vehicles (e.g., a vehicle dealership) can view data from all vehicles associated with the organization. In contrast, individual vehicle owners can only view data from their particular vehicle.
[0046] FIG. 4 illustrates this concept in more detail. The figure shows a schematic drawing of a login process 40 for a web site 42 that displays diagnostic data for a series of ‘customer’ vehicles associated with a vehicle ‘dealership’. Within each vehicle is a wireless appliance that retrieves data from the vehicle's engine computer, and then sends these data, formatted in a data packet, through a wireless network. The data eventually are transferred from the network, through a host computer system, to the web site 42 where they are formatted, displayed and processed as described below.
[0047] A user ‘logs’ into the web site 42 through a login interface 44 by entering a username and password that, once entered, are compared to a database associated with the web site. The comparison determines if the user is a dealer or a customer. If the user is determined to be a dealer, the web site renders a dealer interface 46 that contains, e.g., diagnostic information for each purchased vehicle. Users viewing the dealer interface 46 do hot have access to data corresponding to vehicles sold by other dealerships. If the user is determined to be a customer, the web site 42 renders a customer interface 48 that contains diagnostic information for one or more vehicles corresponding to the customer. Each customer using the web site 42 is associated with a unique customer interface.
[0048] FIG. 5 is a screen capture of a web page 50 included in the dealer interface indicated in FIG. 4 . The host computer system renders this page once the user is determined to be a dealer following the login process. The screen capture features a customer list 52 corresponding to a single dealership that includes: customer names 56 for each customer; a vehicle description 58 that includes the vehicle's year, make and model; a unique 17-digit vehicle identification number (‘VIN’) 60 that functions as the vehicle's serial number; and an ‘alert’ listing 62 that provides a number of alerts for each vehicle. The ‘alerts’ are described in more detail in the application entitled ‘INTERNET-BASED SYSTEM FOR MONITORING VEHICLES’, filed Mar. 15, 2001, the contents of which are incorporated herein by reference. In general, an alert is generated when data, sent from the vehicle's wireless appliance to the host computer system, indicates either 1) a mechanical/electrical problem with the vehicle; or 2) that a scheduled maintenance is recommended for the vehicle. For example, the customer list 52 includes a data field 54 that lists the user ‘Five, Loaner’ with an associated 2001. Toyota Corolla. The data field 54 also includes the number ‘1’ in the alert listing 62, indicating the presence of a single alert.
[0049] FIG. 6 shows a web page 120 that lists a detailed data set 122 transmitted from the vehicle-based wireless appliance to the host computer system. The host computer system receives the data set 122 at a time described by a time/date stamp 72 listed in the header 61. The data set 122 includes a data parameter name 125, a corresponding numerical value 127, and a description of the units 129 of the numerical value 127. As described above, these values are specified in the map corresponding to the data-collection schema used to extract the data from the vehicle. Some of the numerical values (e.g., the status of the ‘MIL light’ 131) are dimensionless, i.e. they do not have units. To generate the numerical values 127, the wireless appliance queries the vehicle's ECU at a set time interval (e.g. every 20 seconds), and transmits a data set 122 at a longer time interval (e.g. every 10 minutes). Thus, the numerical values in the data set can represent ‘instantaneous’ values that result from a single query to the ECU, or they can represent ‘average’ values that result from an average from multiple sequential queries.
[0050] The data parameters within the set 122 describe a variety of electrical, mechanical, and emissions-related functions in the vehicle. Several of the more significant parameters from the set are listed in Table 1, below:
[0051] Pending DTCs
-
- [0052] Ignition Timing Advance
- [0053] Calculated Load Value
- [0054] Air Flow Rate MAF Sensor
- [0055] Engine RPM
- [0056] Engine Coolant Temperature
- [0057] Intake Air Temperature
- [0058] Absolute Throttle Position Sensor
- [0059] Vehicle Speed
- [0060] Short-Term Fuel Trim
- [0061] Long-Term Fuel Trim
- [0062] MIL Light Status
- [0063] Oxygen Sensor Voltage
- [0064] Oxygen Sensor Location
- [0065] Delta Pressure Feedback EGR Pressure Sensor
- [0066] Evaporative Purge Solenoid Dutycycle
- [0067] Fuel Level Input Sensor
- [0068] Fuel Tank Pressure Voltage
- [0069] Engine Load at the Time of Misfire
- [0070] Engine RPM at the Time of Misfire
- [0071] Throttle Position at the Time of Misfire
- [0072] Vehicle Speed at the Time of Misfire
- [0073] Number of Misfires
- [0074] Transmission Fluid Temperature
- [0075] PRNDL position (1, 2, 3, 4, 5=neutral, 6=reverse)
- [0076] Number of Completed OBDII Trips
- [0077] Battery Voltage
[0078] Table 1—Parameters Monitored from Vehicle
[0079] The parameters listed in Table 1 were measured from a Ford Crown Victoria. Similar sets of data are available for nearly all vehicles manufactured after 1996 that have an OBD-II connector. In addition to these, hundreds of other vehicle-specific parameters are also available from the vehicle's computer.
[0080] The data set 122 shown in FIG. 6 represents the most recent data sent from the vehicle's wireless appliance to the host computer system. Data sets sent at earlier times can also be analyzed individually or in a group to determine the vehicle's performance. These ‘historical data’, for example, can by used to determine trends in the vehicle's performance. In some cases data analyzed in this manner can be used to predict potential problems with the vehicle before they actually occur.
[0081] Referring to FIG. 7 , a web page 130 includes a historical data set 132 containing data parameter names 125′, units 129′ and a series of data sets 127a-127c transmitted at earlier times from the in-vehicle wireless appliance. Each of these data sets is similar to the data set 122 shown in FIG. 6 , but is received by the host computer system at an earlier time as indicated by a time stamp 140a-140c. For example, the first two data sets 127c, 127b where transmitted with time stamps 140b, 140c of 11:42 and 11:52 on Feb. 12, 2001; the last data set 127a was transmitted the next morning with a time stamp 140a of 6:05.
[0082] Other embodiments are also within the scope of the invention. In particular, the web pages used to display the data can take many different forms, as can the manner in which the data are displayed. Web pages are typically written in a computer language such as ‘HTML’ (hypertext mark-up language), and may also contain computer code written in languages such as java for performing certain functions (e.g., sorting of names). The web pages are also associated with database software (provided by companies such as Oracle) that is used to store and access data. Equivalent versions of these computer languages and software can also be used.
[0083] Different web pages may be designed and accessed depending on the end-user. As described above, individual users have access to web pages that only show data for their particular vehicle, while organizations that support a large number of vehicles (e.g. dealerships or distributors) have access to web pages that contain data-from a collection of vehicles. These data, for example, can be sorted and analyzed depending on vehicle make, model, odometer reading, and geographic location. The graphical content and functionality of the web pages may vary substantially from what is shown in the above-described figures. In addition, web pages may also be formatted using standard wireless access protocols (WAP) so that they can be accessed using wireless devices such as cellular telephones, personal digital assistants (PDAs), and related devices.
[0084] The web pages also support a wide range of algorithms that can be used to analyze data once it is extracted from the data packets. For example, the above-mentioned alert messages are sent out in response to a DTC or when a vehicle approaches a pre-specified odometer reading. Alternatively, the message could be sent out when a data parameter (e.g. engine coolant temperature) exceeded a predetermined value. In some cases, multiple parameters (e.g., engine speed and load) can be analyzed to generate an alert message. In general, an alert message can be sent out after analyzing one or more data parameters using any type of algorithm. These algorithms range from the relatively simple (e.g., determining mileage values for each vehicle in a fleet) to the complex (e.g., predictive engine diagnoses using ‘data mining’ techniques). Data analysis may be used to characterize an individual vehicle as described above, or a collection of vehicles, and can be used with a single data set or a collection of historical data. Algorithms used to characterize a collection of vehicles can be used, for example, for remote vehicle or parts surveys, to characterize emission performance in specific geographic locations, or to characterize traffic.
[0085] Other embodiments of the invention include algorithms for analyzing data to characterize vehicle accidents and driving patterns for insurance purposes; algorithms for determining driving patterns for use-based leasing; and algorithms for recording vehicle use and driving patterns for tax purposes. In general, any algorithm that processes data collected with the above-described method is within the scope of the invention.
[0086] In other embodiments, additional hardware can be added to the in-vehicle wireless appliance to increase the number of parameters in the transmitted data. For example, hardware for global-positioning systems (GPS) may be added so that the location of the vehicle can be monitored along with its data. Or the radio modem used to transmit the data may employ a terrestrial GPS system, such as that available on modems designed by Qualcomm, Inc. In still other embodiments, the location of the base station that transmits the message can be analyzed to determine the vehicle's approximate location. In addition, the wireless appliance may be interfaced to other sensors deployed in the vehicle to monitor additional data. For example, sensors for measuring tire pressure and temperature may be deployed in the vehicle and interfaced to the appliance so that data relating the tires' performance can be transmitted to the host computer system.
[0087] In other embodiments, the antenna used to transmit the data packet is embedded in the wireless appliance, rather than being disposed in the vehicle's shade band.
[0088] In still other embodiments, data processed using the above-described systems can be used for: remote billing/payment of tolls; remote smog and emissions checks; remote payment of parking/valet services; remote control of the vehicle (e.g., in response to theft or traffic/registration violations); and general survey information.
[0089] Still other embodiments are within the scope of the following claims.
Claims
What is claimed is:
1. A system for interfacing with an on-board diagnostic computer in a vehicle, wherein the on-board diagnostic computer is configured to monitor a set of operational characteristics of the vehicle, the system comprising:
a wireless appliance in the vehicle configured to communicate with the vehicle's on-board diagnostic computer, said wireless appliance comprising (i) a wireless communication component and (ii) a data-collection component,
said wireless communication component configured to wirelessly receive from a base station a software component configured to identify a subset of the set of operational characteristics that are monitored by the on-board diagnostic computer, a user specified first schedule, and a user specified second schedule,
said data-collection component configured to process the received software component and to automatically, repeatedly collect from the vehicle's on-board diagnostic computer data for the subset of operational characteristics identified in the received software component according to said user specified first schedule,
said wireless communication component being further configured to automatically, repeatedly, and wirelessly transmit to a base station said collected data according to said user specified second schedule,
wherein the software component includes a field configured to describe said user specified first schedule,
wherein the software component includes a second field configured to describe said user specified second schedule,
wherein the operational characteristics include at least one of the following: diagnostic trouble codes, vehicle speed, fuel level, fuel pressure, miles per gallon, engine RPM, mileage, oil pressure, oil temperature, tire pressure, tire temperature, engine coolant temperature, intake-manifold pressure, engine-performance tuning parameters, alarm status, accelerometer status, cruise-control status, fuel-injector performance, spark-plug timing, or a status of an anti-lock braking system,
wherein the wireless appliance is configured to send an outgoing data packet that indicates a vehicle's location,
wherein the data-collection component is configured to automatically, repeatedly collect said data from the vehicle's on-board diagnostic computer at times determined by said user specified first schedule specified in the software component, and
wherein the wireless communication component is configured to automatically, repeatedly, and wirelessly transmit to a base station the collected data at times determined by said user specified second schedule specified in the software component.
2. A system for interfacing with an on-board diagnostic computer in a vehicle, wherein the on-board diagnostic computer is configured to monitor a set of operational characteristics of the vehicle, the system comprising:
a wireless appliance in the vehicle configured to communicate with the vehicle's on-board diagnostic computer, said wireless appliance comprising (i) a wireless communication component and (ii) a data-collection component,
said wireless communication component configured to wirelessly receive from a base station a software component configured to identify a subset of the set of operational characteristics that are monitored by the on-board diagnostic computer, a user specified first schedule, and a user specified second schedule,
said data-collection component configured to process the received software component and to automatically, repeatedly collect from the vehicle's on-board diagnostic computer data for the subset of operational characteristics identified in the received software component according to said user specified first schedule, and
said wireless communication component being further configured to automatically, repeatedly, and wirelessly transmit to a base station said collected data according to said user specified second schedule,
wherein the software component includes a field configured to describe said user specified first schedule,
wherein the software component includes a field configured to describe said user specified second schedule.
3. The system of claim 2, wherein the software component is configured to identify an address of an operational characteristic for which data is to be collected from the vehicle's on-board diagnostic computer.
4. The system of claim 2, wherein the software component comprises an address that describes a location of a diagnostic datum in a computer memory in the vehicle.
5. The system of claim 2, wherein the software component is an ASCII or binary data file.
6. The system of claim 2, wherein the operational characteristics include at least one of the following: diagnostic trouble codes, vehicle speed, fuel level, fuel pressure, miles per gallon, engine RPM, mileage, oil pressure, oil temperature, tire pressure, tire temperature, engine coolant temperature, intake-manifold pressure, engine-performance tuning parameters, alarm status, accelerometer status, cruise-control status, fuel-injector performance, spark-plug timing, or a status of an anti-lock braking system.
7. The system of claim 2, wherein the wireless appliance is configured to send an outgoing data packet that indicates a vehicle's location.
8. The system of claim 2, wherein the vehicle is selected from a group comprising an automobile, truck, wheeled commercial equipment, heavy truck, power sport vehicle, collision repair vehicle, marine vehicle, and recreational vehicle.
Patent Citations (196)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3748894(A) | 1973-07-01 | White et al. | Applicant |
| US4258421(A) | 1981-03-01 | Juhasz et al. | Examiner |
| 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. | Examiner |
| US5737215(A) | 1998-04-01 | Schricker et al. | Applicant |
| US5754965(A) | 1998-05-01 | Hagenbuch | Examiner |
| 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 |
| 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 |
| 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 | Examiner |
| 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. | Examiner |
| 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 |
| 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 | Lightner et al. | Applicant |
| US6732032(B1) | 2004-05-01 | Banet et al. | Applicant |
| US6738697(B2) | 2004-05-01 | Breed | Applicant |
| US6751452(B1) | 2004-06-01 | Kupczyk et al. | Examiner |
| 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 |
| 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 |
| 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 (23)
- Disclosed Anonymously, Abstract, “Vehicle Diagnostics 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. 758-785, 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), pp. 502-639.Applicant
- Motorola, Inc., “Automative 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
- U.S. Appl. No. 11/799,848, filed May 3, 2007.Applicant