Vehicles, such as automobiles, light-duty trucks, and heavy-duty trucks, play an important role in the lives of many people. To keep vehicles operational, some of those people rely on vehicle technicians to diagnose and repair their vehicle.
Vehicle technicians use a variety of tools in order to diagnose and/or repair vehicles. Those tools may include common hand tools, such as wrenches, hammers, pliers, screwdrivers and socket sets, or more vehicle-specific tools, such as cylinder hones, piston ring compressors, and vehicle brake tools. The tools used by vehicle technicians may also include electronic diagnostic tools such as a digital voltage-ohm meter (DVOM) or a vehicle scan tool that communicates with an electronic control unit (ECU) within a vehicle.
A number of different types of diagnostic tools have been used, such as engine analyzers, which are designed to monitor a variety of operating conditions of an internal combustion engine, and scanners for downloading data from vehicle on-board computers, such as the ECU. In addition, diagnostic tools may include laboratory-type tools like oscilloscopes, digital volt-ohm meters (DVOM) and the like.
Electronic diagnostic tools include displays for providing the desired information to a technician. These displays are often interactive so the technician can easily retrieve whatever information is needed. However, current tools have operating systems that require multiple steps to retrieve certain specific information regarding the vehicle.
By providing the repair technician with detailed information for quickly diagnosing and repairing vehicles, vehicle repair times can be decreased, vehicle turn-over is increased, and as a result, repair technicians may reap increased profits from a same amount of garage space.
In one embodiment, a diagnostic tool for displaying data is described. The diagnostic tool includes a display having a non-graph view including a plurality of demarcated portions. Each of the plurality of demarcated portions includes a graph selection element, a parameter identifier that corresponds to the graph selection element, and a current parameter value that corresponds to the graph selection element. The display also includes a graph view upon selection of the graph selection element in one of the demarcated portions. The graph view includes a first parameter identifier and a first current parameter value, each corresponding to the selected graph selection element. The graph view also includes a text selection element and a graph of parameter values associated with the first parameter identifier. In the graph view, some of the demarcated portions may be viewable within the display, and the demarcated portions which are not shown in the display are viewable using a scrollbar.
In another embodiment, the diagnostic tool includes a display having a non-graph view including a plurality of demarcated portions. Each of the plurality of demarcated portions includes a graph selection element, a parameter identifier that corresponds to the graph selection element, and a current parameter value that corresponds to the graph selection element. The display also includes a graph view upon selection of the graph selection element in one of the demarcated portions. The graph view includes a first parameter identifier and a first current parameter value each corresponding to the selected graph selection element. The graph view also includes a text selection element and a graph of parameter values associated with the first parameter identifier. Upon the selection of the text selection element, the display returns to the non-graph view.
In yet another embodiment, a method for displaying data on a diagnostic tool having a display is disclosed. The method includes providing, in the display, a non-graph view having a plurality of demarcated portions. Each of the plurality of demarcated portions includes a graph selection element, a parameter identifier that corresponds to the graph selection element, and a current parameter value that corresponds to the graph selection element. Next, a graph selection element in one of the demarcated portions is selected to show a graph view in the display. The graph view includes a first parameter identifier and a first current parameter value, each corresponding to the selected graph selection element. The graph view also includes a text selection element and a graph of parameter values associated with the first parameter identifier. Upon selection of the text selection element, the display returns to the non-graph view.
These as well as other aspects and advantages will become apparent to those of ordinary skill in the art by reading the following detailed description, with reference where appropriate to the accompanying drawings. Further, it should be understood that the embodiments described in this overview and elsewhere are intended to be examples only and do not necessarily limit the scope of the claims.
Example embodiments are described herein with reference to the drawings, in which:
This description sets forth systems comprising multiple devices for use in servicing (e.g., diagnosing and/or repairing) a device-under-service. Each device of a described system is operable independently (e.g., as a stand-alone device) as well as in combination with other devices of the system. Each device of a described system may alternatively be referred to as an apparatus.
Each device of a described system is operable to carry out functions for servicing a device-under-service. The device-under-service may comprise a vehicle, a refrigeration unit, a personal computer, or some other serviceable device. Additionally or alternatively, the device-under-service may comprise a system such as a heating, ventilation, and air conditioning (HVAC) system, a security system, a computer system (e.g., a network), or some other serviceable system. The functions for servicing the device-under-service may include but are not limited to diagnostic functions, measurement functions, and scanning functions.
To work in combination with each other, the device of a described system is operable to communicate with another device via a communications network. The communications network may comprise a wireless network, a wired network, or both a wireless network and a wired network. Data obtained by a device from a device-under-service or data otherwise contained in that device may be transmitted to another device via the communications network between those devices.
Devices shown in the Figures and described in this specification are also described in U.S. patent application Ser. No. 61/374,723, filed on Aug. 18, 2010, entitled “Method and Apparatus to Use Remote and Local Control Modes to Acquire and Visually Present Data”, which is incorporated by reference herein in its entirety.
The block diagram of
A wireless network 110 may be established between any two or more of devices 104, 106, and 108. Any one of those devices may join (e.g., begin communicating via) wireless network 110 after wireless network 110 is established. As an example,
Wireless network 110 may comprise one or more wireless networks. Each of the one or more wireless networks may be arranged to carry out communications according to a respective air interface protocol. Each air interface protocol may be arranged according to an industry standard, such as an Institute of Electrical and Electronics Engineers (IEEE) 802 standard. The IEEE 802 standard may comprise an IEEE 802.11 standard for Wireless Local Area Networks (e.g., IEEE 802.11 a, b, g, or n), an IEEE 802.15 standard for Wireless Personal Area Networks, an IEEE 802.15.1 standard for Wireless Personal Area Networks—Task Group 1, an IEEE 802.16 standard for Broadband Wireless Metropolitan Area Networks, or some other IEEE 802 standard. For purposes of this description, a wireless network arranged to carry out communications according to the IEEE 802.11 standard is referred to as a Wi-Fi network, and a wireless network arranged to carry out communications according to the IEEE 802.15.1 is referred to as a Bluetooth network.
DAQ device 104 may connect to device-under-service 102 via wired link 112. Wired link 112 may comprise input leads, for example. DAQ device 104 may comprise a digital volt meter (DVM), a digital volt ohm meter (DVOM), an oscilloscope, or some other type of measurement device operational to acquire data from device-under-service 102.
Vehicle scanner 106 may connect to device-under-service 102 via wired link 114. Wired link 114 may be arranged as a cable assembly described in U.S. patent application Ser. No. 61/374,805, filed on Aug. 18, 2010, and is entitled “Cable assembly for protection against undesired signals,” which is incorporated herein by reference, or wired link 114 may be arranged as some other wired link. Vehicle scanner 106 may comprise a device that is operable to request and/or monitor data from one or more electronic control units (ECU) located on and/or within device-under-service 102. The data from the ECU(s) may comprise serial data arranged according to serial data available at an On Board Diagnostic (OBD) II connector within an automobile, such as a Society of Automotive Engineers (SAE) J1850 standard or an International Organization for Standardization (ISO) 9141-2 standard.
Vehicle scanner 106 may be operable as a stand-alone-device when vehicle scanner 106 operates as a data recorder to collect data from device-under-service 102 and other devices of system 100 are not connected to device-under-service 102 or communicating with vehicle scanner 106. Such data obtained when vehicle scanner operates as a data recorder can subsequently be displayed via another device of system 100, such as display device 108.
Device-under-service 102 may comprise a vehicle, such as an automobile, a motorcycle, a semi-tractor, a light-duty truck, a medium-duty truck, a heavy-duty truck, farm machinery, or some other vehicle. System 100 is operable to carry out a variety of functions, including functions for servicing device-under-service 102. The example embodiments may include or be utilized with any appropriate voltage or current source, such as a battery, an alternator, a fuel cell, and the like, providing any appropriate current and/or voltage, such as about 12 volts, about 42 volts, and the like. The example embodiments may be used with any desired system or engine. Those systems or engines may comprise items utilizing fossil fuels, such as gasoline, natural gas, propane, and the like, electricity, such as that generated by battery, magneto, fuel cell, solar cell and the like, wind and hybrids or combinations thereof. Those systems or engines may be incorporated into other systems, such as an automobile, a truck, a boat or ship, a motorcycle, a generator, an airplane and the like.
One or more of remote devices 104 and 106 and display device 108 may connect to a wired network 116. Vehicle scanner 106 and display device 108 may connect to a network 116 via wired links 118 and 120, respectively. Network 116 may include and/or connect to the Internet, and network 116 may include and/or connect to one or more network nodes, such as an access node 122 and a network node 124. Access node 122 may provide any of DAQ device 104, vehicle scanner 106, and display device 108 with wireless connectivity to network 116. Network node 124 may comprise a desktop personal computer (PC), a workstation that executes a Unix-based or Linux-based operating system, or some other node that interfaces and/or connects to network 116. In accordance with an example in which device-under-service 102 comprises an automobile, network node 124 may comprise a desktop PC or workstation operating at an automobile repair facility. In that regard, network node 124 may operate as a server that provides data (e.g., automobile repair data and/or instruction data) to display device 108.
DAQ device 104 and remote device 106 may each transmit data to display device 108 for display via a user interface 200 (shown in
Next,
User interface 200 is operable to present data to a user and to enter user inputs (e.g., user selections). User interface 200 may include a display, such as display 300 illustrated in
Wireless transceiver 202 comprises a wireless transceiver that is operable to carry out communications via wireless network 110. Wireless transceiver 202 may carry out communications with one or more remote devices, such as one or more of DAQ device 104, vehicle scanner 106, and some other device (other than display device 108) that is operating to communicate via wireless network 110. As an example, wireless transceiver 202 may comprise a transceiver that is operable to carry out communications via a Bluetooth network. For purposes of this description, a transceiver that is operable to carry out communications via a Bluetooth network is referred to as a Bluetooth transceiver. As another example, wireless transceiver 202 may comprise a transceiver that is operable to carry out communications via a Wi-Fi network. For purposes of this description, a transceiver that is operable to carry out communications via a Wi-Fi network is referred to as a Wi-Fi transceiver.
In accordance with an embodiment in which DAQ device 104, vehicle scanner 106, and display device 108 each include a single wireless transceiver (e.g., a Bluetooth transceiver), one of the devices, such as display device 108, can operate as a master (e.g., a controller), and the other devices, such as DAQ device 104 and vehicle scanner 106, can operate as slaves to the master. DAQ device 104, vehicle scanner 106, and display device 108 may transmit communications via wireless network 110 using a time-division duplex arrangement and synchronized to a clock signal of the master.
Wireless transceiver 202 is not limited to a single wireless transceiver. For example, wireless transceiver 202 may comprise a Bluetooth transceiver and a Wi-Fi transceiver. In accordance with such an example, the Bluetooth transceiver may communicate with DAQ device 104 and/or vehicle scanner 106 via a Bluetooth network of wireless network 110, and the Wi-Fi transceiver may communicate with DAQ device 104 and/or vehicle scanner 106 via a Wi-Fi network of wireless network 110.
In accordance with an embodiment in which display device 108 includes two wireless transceivers (e.g., a Bluetooth transceiver and a Wi-Fi transceiver) and DAQ device 104 and vehicle scanner 106 each include two wireless transceivers (e.g., a Bluetooth transceiver and a Wi-Fi transceiver), DAQ device 104 and vehicle scanner 106 may simultaneously transmit data to display device 108 for display via display 300. In that regard, DAQ device 104 may transmit data to display device 108 via the Bluetooth network of wireless network 110 and vehicle scanner 106 may transmit data to display device 108 via the Wi-Fi network of wireless network 110. Alternatively, DAQ device 104 and vehicle scanner 106 may take turns transmitting data to display device 108 via the Bluetooth network, the Wi-Fi network, or both the Bluetooth network and the Wi-Fi network.
In accordance with an embodiment in which wireless transceiver 202 includes three or more wireless transceivers, two or more of the wireless transceivers may communicate according to a common air interface protocol or different air interface protocols.
Each wireless transceiver of the example embodiments may operate in a transceiver-on state. In the transceiver-on state, the transceiver is powered on. While operating in the transceiver-on state, the transceiver can transmit and receive data via an air interface. For some transceivers, while operating in the transceiver-on state, the transceiver can transmit and receive data via the air interface simultaneously. For other transceivers, at any given time while operating in the transceiver-on state, the transceiver can either transmit data or receive data via the air interface. Each wireless transceiver of the example embodiments may operate in a transceiver-off state. While operating in the transceiver-off state, the transceiver does not transmit or receive data via an air interface. While operating in the transceiver-off state, the transceiver can be powered off.
Wired interface 206 may include one or more ports. Examples of those ports include, but are not limited to, a Universal Serial Bus (USB) port, an audio output port, an audio input port, and a power port. Each port of wired interface 206 provides an interface to display device 108 and to one or more circuits. In one respect, the one or more circuits may comprise electrical circuits, such as the electrical circuits of a Universal Serial Bus (USB) cable or the electrical circuits of an Ethernet cable (e.g., a CAT 5 cable). In another respect, the one or more circuits may comprise optical fibers that are operable to carry optical signals. Other examples of the one or more circuits are also possible.
Processor 204 may comprise one or more general purpose processors (e.g., INTEL microprocessors) and/or one or more special purpose processors (e.g., digital signal processors). Processor 204 may execute computer-readable program instructions (CRPI) 212 that are contained in computer-readable data storage device 208.
Data storage device 208 may comprise a computer-readable storage medium readable by processor 204. The computer-readable storage medium may comprise volatile and/or non-volatile storage components, such as optical, magnetic, organic or other memory or disc storage, which can be integrated in whole or in part with processor 204. Data storage device 208 may contain various data including, but not limited to, CRPI 212, remote device data 214, menu data 216, and instruction data 218.
Remote device data 214 may include data associated with a device that is arranged to communicate with display device 108 via wireless network 110. For example, remote device data 214 may include data associated with DAQ 104, such as a radio identifier and password associated with DAQ 104. The data associated with DAQ 104 may be received at display device 108, for storing as remote device data 214, during a pairing process carried out between display device 108 and DAQ 104. The pairing process between DAQ 104 and display device 108 may include DAQ 104 providing display device 108 with the data associated with DAQ 104 and display device 108 providing DAQ 104 with data associated with display device 108. After carrying out the paring process with DAQ 104, display device 108 may use the remote device data 214 when establishing communication network 110 with DAQ 104.
Remote device data 214 is not limited to data associated with one remote device. In that regard, remote device data 214 may include respective data associated with each of a plurality of devices operable to communicate via wireless network 110, such as data associated with DAQ 104 and data associated with vehicle scanner 106. The data associated with vehicle scanner 106 may include a radio identifier and password associated with vehicle scanner 106. The data associated with vehicle scanner 106 may be received at display device 108, for storing as remote device data 214, during a pairing process carried out between display device 108 and vehicle scanner 106. The pairing process between vehicle scanner 106 and display device 108 may include vehicle scanner 106 providing display device 108 with the data associated with vehicle scanner 106 and display device 108 providing vehicle scanner 106 with data associated with display device 108. After carrying out the paring process with vehicle scanner 106, display device 108 may use the remote device data 214 when establishing wireless network 110 with vehicle scanner 106.
Menu data 216 comprises data that can be visually presented via display 300, such as a menu which may comprise one or more menu items that is/are selectable by a user. Selection of a menu item can cause display 300 to display instruction data 218. Additionally or alternatively, selection of a menu item can cause wireless transceiver 202 to transmit instruction data 218 to a remote device (e.g., DAQ 104 or vehicle scanner 106) as payload of a message, such as a data-share message or to transmit a mode-selection command to the remote device.
Instruction data 218 may comprise various data. As an example, instruction data 218 may comprise data that illustrates how to connect DAQ 104 and/or vehicle scanner 106 to device-under-service 102. As another example, instruction data 218 may comprise diagnostic information for diagnosing device-under-service 102. For instance, in accordance with an example embodiment in which device-under-service 102 comprises an automobile, the diagnostic information may comprise diagnostic flow charts for diagnosing an electrical system on the automobile. The diagnostic flow charts can provide different paths to follow based on measurement data display device 108 obtains from DAQ 104 and/or vehicle scanner 106.
CRPI 212 may comprise program instructions that are executable as an operating system that provides for direct control and management of hardware components (e.g., processor 204 and data storage device 208) of display device 108. The operating system can manage execution of other program instructions within CRPI 212. As an example, the operating system may comprise the Windows XP Embedded (XPe) operating system available from Microsoft Corporation, Redmond, Wash., United States. Other examples of the operating system are also possible. CRPI 212 may comprise program instructions that are executable by processor 204 to cause display 300 to display menu data 216 or instruction data 218. Displaying menu data 216 may include displaying a list of operating modes of DAQ 104 or of vehicle scanner 106.
Next,
Display 300 may comprise a liquid crystal display (LCD), a plasma display, or some other type of display. Display 300 is operable to visually present (e.g., display) data to a user. Display 300 may visually present data using numbers, letters, punctuation marks, pictures, graphs, or some other visually presentable form of data. The data visually presentable and/or presented at display 300 may include locally-acquired data (LAD), such as menu data 216 and a cursor that can be moved between menu items of menu data 216. The data visually presentable and/or presented at display 300 may include remotely-acquired data (RAD), such as data acquired via wireless transceiver 202 or wired interface 206.
Display 300 may comprise a touch screen that can detect the presence and location of a touch within its display area. The various menu items of a displayed menu may be selected via the touch screen.
User controls 306 are operable to enter a user-selection. User controls 306 may be arranged in various ways. In that regard, user controls 306 may be arranged to include a keypad, rotary switches, push buttons, or some other means to enter a user-selection. In the example embodiment illustrated in
As described above, the display 300 may be an interactive touch screen where a number of different actions can be selected by the user. The actions may be selected by touching the display 300 with a user's finger or with a stylus, for example. One such action may include selecting specific data related to the device-under-service 102 to be displayed.
The data shown on the data display screen 400 may be arranged in a plurality of demarcated portions 402. The demarcated portions 402 may be presented in a dual column format, as shown in
Each of the plurality of demarcated portions 402 may include a graph selection element 406 located within or directly adjacent to the demarcated portion 402. In
The processor 204 may execute CRPI 212 to detect selection of graph selection element 406 (e.g., detecting a given area of display 300, where graph selection element 406 is located, is touched via a user's finger, a stylus, or some other selection device). In response to detecting selection of graph selection 406, processor 204 may execute CRPI 212 to cause display 300 to transition from a non-graph view to a graph view.
Each of the plurality of demarcated portions 402 may also include an associated PID 408 and current parameter value 410. The PID and parameter value both correspond to a single graph selection element 406. The PID 408 may be a parameter associated with the retrieved data (e.g., data received from vehicle scanner 106). In this example, the retrieved data is engine data for a vehicle (a 2001 Chevrolet Tahoe), and thus example PIDs may include Engine Revolutions per Minute (RPM), Throttle Position Sensor voltage (TPS), and Heated Oxygen Sensor voltage (HO2S). Other PIDs may include any OBD I or OBD II parameter. The PID 408 may take the form of an abbreviated parameter name. The current parameter value 410 is a current value of the PID with which the parameter value is associated. The current parameter value 410 is constantly changing and/or refreshing to display the current, up-to-date information associated with the specific PID of the device-under-service 102.
The non-graph screen 400 may also include one or more icons 412 for performing additional functions in the non-graph view, such as a zoom function, pausing and restarting the constant flow of data, taking a snapshot of the screen, and returning to the home screen, for example. These icons may be located toward the bottom of the display 300. A movie control or jog function 413 may also be located on the non-graph screen 400. The movie control function 413 may include a scroll bar which allows a user to fast forward or rewind the data received by the display device 108 and viewed on the display 300 in small or large increments.
Referring to
The text selection element 506 may be located within or directly adjacent to the graph demarcated portion 502. In
Each graph 501 may be scrolling and constantly updating according to the current readings of the device-under-service 102. The newest current parameter value 510 is added to the right portion of the graph, and the oldest parameter value (at the left portion of the graph) is removed. The graph 501 may further include a display of the minimum and maximum parameter values retrieved from the device-under-service. These values may be displayed as “Min” and Max” on the graph 501.
More than one graph 501 can be viewed on the data display screen 500 at a time. For example, as shown in
The graph view 500 may also include one or more icons 512 for performing additional functions in the graph view, such as a zoom function, pausing and restarting the constant flow of data, taking a snapshot of the screen, and returning to the home screen, for example. These icons may be located toward the bottom of the display 300. A movie control or jog function 513 may also be located on the graph screen 500. The movie control function 513 may include a scroll bar which allows a user to fast forward or rewind the data received by the display device 108 and viewed on the display 300 in small or large increments.
The graphs 501 may include additional icons for specific graph functions, such as an expand/collapse icon 514 and a graph properties icon 516. When the graph 501 is displayed in only a portion of the data display screen 500, the expand/collapse icon 514 may be selected to expand the graph 501 to fill a larger portion of the screen or the entire screen 500. The processor 204 detects selection of the expand/collapse icon 514 and in response, CRPI are carried out which cause the graph 501 to expand. The expand/collapse icon 514 may then be selected again, causing the processor 204 to carry out a different set of CRPI which causes the screen to return to the standard view of the graph, where the graph is displayed in a smaller portion of the screen.
The graph properties icon 516 may allow a user to select triggers for recording a snapshot and to adjust the scale of the graph. When the graph properties icon 516 is selected, the processor 204 carries out CRPI which cause a screen 600 (shown in
In operation, a user selects one of the graph selection elements 406 in the non-graph view of the data display screen 400. Upon selection of a first graph selection element 406, a graph 501 of the information located in the demarcated portion 402 appears on the screen 400 in the graph view 500. Selection may include selecting the first graph selection element 406 on the display 300, or pressing a button on the display device 108 located next to the desired demarcated portion 402 which corresponds to the first graph selection element 406, for example. Selecting the first graph selection element 406 for the graph view moves the associated demarcated portion and graph 501 to the top of the plurality of graph demarcated portions 502. Some, or a portion of, the remaining demarcated portions 402 are viewable within the display 300 underneath the graph 501, and those demarcated portions which are not viewable in the display can be brought onto the display 300 by moving the scrollbars 504. In another embodiment, the graph view may not include scrollbars, and the remaining demarcated portions 402 or graphs may be viewed on the display 300 by touching and dragging the screen up or down with a finger or stylus.
As described above, more than one graph 501 can be viewed on the data display screen 500 at a time. To view an additional graph, a second graph selection element is selected by the user. If the second graph selection element is located in a different column than the graph 501, a second graph 520 appears at the top of the second column beside the first graph 501. If the second graph selection element is located in the same column as the graph 501, then the second graph 520 appears in the place of the graph 501 at the top of the column, and the graph 501 appears underneath the second graph 520. The latest selected graph appears at the top of its associated column.
When a large amount of graphs are viewable on the display 300 at once, such as four graphs, for example, the demarcated portions 402 may be only be visible by moving the scrollbars 504 or by touching and dragging the screen up or down with a user's finger or stylus. Additional graphs may also be viewable on the display 300 by moving the scrollbars 504 or by touching and dragging the screen up or down with a user's finger or stylus.
To return to the non-graph view, a user selects the text selection element 506 located in the graph demarcated portion 502 of the graph 501. Thus, as explained above, a user does not have to perform multiple actions in order to alternate the viewing of information as a graph or as text. This allows the user to be more efficient in their evaluation of the device-under-service 102.
While examples have been described in conjunction with present embodiments of the application, persons of skill in the art will appreciate that variations may be made without departure from the scope and spirit of the application. For example, the apparatus and methods described herein may be implemented in hardware, software, or a combination, such as a general purpose or dedicated processor running a software application through volatile or non-volatile memory. The true scope and spirit of the application is defined by the appended claims, which may be interpreted in light of the foregoing.
Number | Name | Date | Kind |
---|---|---|---|
4113980 | Bell | Sep 1978 | A |
4270174 | Karlin et al. | May 1981 | A |
4404639 | McGuire et al. | Sep 1983 | A |
4441359 | Ezoe | Apr 1984 | A |
4602127 | Neely et al. | Jul 1986 | A |
4853850 | Krass, Jr. et al. | Aug 1989 | A |
4962456 | Abe et al. | Oct 1990 | A |
5157610 | Asano et al. | Oct 1992 | A |
5160892 | Makhija et al. | Nov 1992 | A |
5365436 | Schaller et al. | Nov 1994 | A |
5373458 | Bishay et al. | Dec 1994 | A |
5432904 | Wong | Jul 1995 | A |
5442553 | Parrillo | Aug 1995 | A |
5465207 | Boatwright et al. | Nov 1995 | A |
5506772 | Kubozono et al. | Apr 1996 | A |
5521443 | Imura et al. | May 1996 | A |
5532927 | Pink et al. | Jul 1996 | A |
5541840 | Gurne et al. | Jul 1996 | A |
5553235 | Chen | Sep 1996 | A |
5583912 | Schillaci et al. | Dec 1996 | A |
5592383 | Rogers et al. | Jan 1997 | A |
5758300 | Abe | May 1998 | A |
5766020 | Hughes | Jun 1998 | A |
5850209 | Lemke et al. | Dec 1998 | A |
5884202 | Arjomand | Mar 1999 | A |
5899947 | Hall et al. | May 1999 | A |
6021366 | Fieramosca et al. | Feb 2000 | A |
6055468 | Kaman et al. | Apr 2000 | A |
6067486 | Aragones et al. | May 2000 | A |
6094609 | Arjomand | Jul 2000 | A |
6134489 | Smedley | Oct 2000 | A |
6169943 | Simon et al. | Jan 2001 | B1 |
6178527 | Vidales | Jan 2001 | B1 |
6179214 | Key et al. | Jan 2001 | B1 |
6181563 | Shimbo et al. | Jan 2001 | B1 |
6188384 | Sullivan et al. | Feb 2001 | B1 |
6192303 | Takakura et al. | Feb 2001 | B1 |
6294982 | Hooks et al. | Sep 2001 | B1 |
6314422 | Barker et al. | Nov 2001 | B1 |
6321151 | Shultz | Nov 2001 | B1 |
6348935 | Malacinski | Feb 2002 | B1 |
6356823 | Iannotti et al. | Mar 2002 | B1 |
6360551 | Renders | Mar 2002 | B1 |
6374315 | Okada et al. | Apr 2002 | B1 |
6385300 | Mohammadian et al. | May 2002 | B1 |
6401049 | Ehmer | Jun 2002 | B1 |
6477478 | Jones et al. | Nov 2002 | B1 |
6487478 | Azzaro et al. | Nov 2002 | B1 |
6609050 | Li | Aug 2003 | B2 |
6622070 | Wacker et al. | Sep 2003 | B1 |
6640166 | Liebl et al. | Oct 2003 | B2 |
6662123 | Maeckel et al. | Dec 2003 | B2 |
6693367 | Schmeisser et al. | Feb 2004 | B1 |
6711524 | Wolf et al. | Mar 2004 | B2 |
6745151 | Marko et al. | Jun 2004 | B2 |
6757521 | Ying | Jun 2004 | B1 |
6778931 | Letts et al. | Aug 2004 | B1 |
6789007 | Ellis et al. | Sep 2004 | B2 |
6802032 | Budinger et al. | Oct 2004 | B1 |
6807469 | Funkhouser et al. | Oct 2004 | B2 |
6822639 | Silverbrook et al. | Nov 2004 | B1 |
6823243 | Chinnadurai et al. | Nov 2004 | B2 |
6844823 | Hooks et al. | Jan 2005 | B2 |
6847916 | Ying | Jan 2005 | B1 |
6873940 | Kamatani | Mar 2005 | B1 |
6947043 | Klingman et al. | Sep 2005 | B1 |
6957128 | Ito et al. | Oct 2005 | B1 |
6959235 | Abdel-Malek et al. | Oct 2005 | B1 |
6972669 | Saito et al. | Dec 2005 | B2 |
6982653 | Voeller et al. | Jan 2006 | B2 |
6988053 | Namaky | Jan 2006 | B2 |
7020546 | Nagai et al. | Mar 2006 | B2 |
7023332 | Saito et al. | Apr 2006 | B2 |
7073714 | Namaky et al. | Jul 2006 | B2 |
7124058 | Namaky et al. | Oct 2006 | B2 |
7155321 | Bromley et al. | Dec 2006 | B2 |
7200483 | Kavadeles | Apr 2007 | B1 |
7216116 | Nilsson | May 2007 | B1 |
7224262 | Simon et al. | May 2007 | B2 |
7251552 | Schmeisser et al. | Jul 2007 | B2 |
7254550 | Reichwein et al. | Aug 2007 | B2 |
7269482 | Shultz et al. | Sep 2007 | B1 |
7272476 | Ortiz et al. | Sep 2007 | B2 |
7281663 | Schmidt et al. | Oct 2007 | B2 |
7294906 | Ukaji | Nov 2007 | B2 |
7327228 | Min et al. | Feb 2008 | B2 |
7336082 | Mofield | Feb 2008 | B1 |
7383318 | Craik | Jun 2008 | B2 |
7444216 | Rogers et al. | Oct 2008 | B2 |
7504926 | Bessho et al. | Mar 2009 | B2 |
7505038 | Bell | Mar 2009 | B2 |
7580781 | Mindeman | Aug 2009 | B2 |
7613554 | Rollinger et al. | Nov 2009 | B2 |
7634337 | Brozovich et al. | Dec 2009 | B2 |
7648062 | Corniot | Jan 2010 | B2 |
7702437 | Gilbert | Apr 2010 | B2 |
7711462 | Daniels et al. | May 2010 | B2 |
7751955 | Chinnadurai et al. | Jul 2010 | B2 |
20010001850 | Miller | May 2001 | A1 |
20020077780 | Liebl | Jun 2002 | A1 |
20020174416 | Bates | Nov 2002 | A1 |
20030020759 | Cancilla et al. | Jan 2003 | A1 |
20040172177 | Nagai | Sep 2004 | A1 |
20050083965 | Sodergren | Apr 2005 | A1 |
20050144069 | Wiseman | Jun 2005 | A1 |
20050152294 | Yu et al. | Jul 2005 | A1 |
20050157732 | Joy et al. | Jul 2005 | A1 |
20050182537 | Tefft et al. | Aug 2005 | A1 |
20050267655 | Gessner | Dec 2005 | A1 |
20060025897 | Shostak et al. | Feb 2006 | A1 |
20060078175 | Brozovich | Apr 2006 | A1 |
20060101311 | Lipscomb et al. | May 2006 | A1 |
20060106508 | Liebl et al. | May 2006 | A1 |
20060149434 | Bertosa et al. | Jul 2006 | A1 |
20060180371 | Breed et al. | Aug 2006 | A1 |
20060212239 | Letts et al. | Sep 2006 | A1 |
20060212540 | Chon et al. | Sep 2006 | A1 |
20060226298 | Pierson | Oct 2006 | A1 |
20070083307 | Pasztor et al. | Apr 2007 | A1 |
20070100520 | Shah | May 2007 | A1 |
20070156311 | Elcock et al. | Jul 2007 | A1 |
20070200550 | Corredoura | Aug 2007 | A1 |
20070244611 | Brozovich | Oct 2007 | A1 |
20070244614 | Nathanson | Oct 2007 | A1 |
20070244990 | Wells | Oct 2007 | A1 |
20070288134 | Rollinger et al. | Dec 2007 | A1 |
20070290847 | Harrington et al. | Dec 2007 | A1 |
20070294556 | Wutka | Dec 2007 | A1 |
20080033609 | Razavi | Feb 2008 | A1 |
20080070501 | Wyld | Mar 2008 | A1 |
20080082278 | Tan et al. | Apr 2008 | A1 |
20080122288 | Plante et al. | May 2008 | A1 |
20080125067 | Bells et al. | May 2008 | A1 |
20080140281 | Morris et al. | Jun 2008 | A1 |
20080295014 | Hennum | Nov 2008 | A1 |
20090125351 | Davis, Jr. | May 2009 | A1 |
20090265057 | Chinnadurai et al. | Oct 2009 | A1 |
20090276115 | Chen | Nov 2009 | A1 |
20090288009 | Dulaney | Nov 2009 | A1 |
20090299539 | Chinnadurai et al. | Dec 2009 | A1 |
20090307188 | Oldham | Dec 2009 | A1 |
20100076644 | Cahill et al. | Mar 2010 | A1 |
20110069769 | Stennicke | Mar 2011 | A1 |
20110141953 | Wright et al. | Jun 2011 | A1 |
20120010765 | Wilson | Jan 2012 | A1 |
20120089893 | Bousamra | Apr 2012 | A1 |
20120255160 | Boone | Oct 2012 | A1 |
Number | Date | Country |
---|---|---|
2385934 | Sep 2003 | GB |
9956201 | Nov 1999 | WO |
0034838 | Jun 2000 | WO |
0155690 | Aug 2001 | WO |
0167420 | Sep 2001 | WO |
0186576 | Nov 2001 | WO |
2006050454 | May 2006 | WO |
2006110786 | Oct 2006 | WO |
2007038983 | Apr 2007 | WO |
2009149007 | Dec 2009 | WO |
2010019771 | Feb 2010 | WO |
Entry |
---|
YouTube Gets Theater View for Long Videos http://lifehacker.com/5060101/youtube-gets-theater-view-for-long-videos, Oct. 7, 2008. 1page. |
YouTube Threater View, http://blogoscoped.com/forum/142450.html, Oct. 6, 2008, 2 pages. |
Fluke Corporation, Digital Multimeters, downloaded from the World Wide Web at http://us.fluke.com/usen/products/categorydmm on Jan. 28, 2010. |
Fluke Corportation, 233 True=rms Remote Display Digital Multimeter Users Manual, Sep. 2009. |
Shigeru et al, DL7100 Signal Explorer, A High-Speed Digital Oscilloscope with Long Record Length, Yokogawa Electric Corporation, Yogogawa Technical Report English Edition, No. 30, (2000). |
bluetomorrow.com, Bluetooth Pairing, downloaded from the World Wide Web at www.bluetomorrow.com on Apr. 30, 2010. |
Snap-On Diagnostics, Snap-on Introduces Verdict Diagnostic and Information System, Aug. 24, 2010. |
Testpath, Inc., Fluke Meter Holsters, downloaded from the World Wide Web at http://www.testpath.com/Categories/Fluke-Meter-Holsters-2220.htm on May 6, 2010. |
BMW Canada, Bluetooth Pairing Instructions, Sep. 2009. |
Accessory Geeks, Bluetooth Pairing Guides, downloaded from the World Wide Web at http://www.accessorygeeks.com/bluetooth-pairing-guide1.html on Apr. 30, 2010. |
Quatech, Inc., Bluetooth Communication Overview, downloaded from the World Wide Web at http://www.quatech.com/support/comm-over-bluetooth.php on May 3, 2010. |
Omitec Limited, T4 Diagnostic System, downloaded from the World Wide Web at http://web.archive.org/web/20091119041838/http://www.omitec.com/us/products/diagnostic-testers/t4-diagnostic-system/ as archived on Nov. 19, 2009. |
Omitec Limited, Workstations, downloaded from the World Wide Web at http://web.archive.org/web/20100322213801/http://www.omitec.com/us/products/workstation/ as archived on Mar. 22, 2010. |
anotherurl.com, Bluetooth, What is Bluetooth? downloaded from the World Wide Web at http://www.anotherurl.com/library/bluetooth—research.htm on May 17, 2010.verdict. |
Snap-On Incorporated, EEDM604C, Multimeter, Digital, Automotive, True RMS, Auto Ranging, Hybrid Vehicles, downloaded from the World Wide Web at http://buy1.snapon.com/catalog/item.asp?store=snapon-store&item—ID=88136&group—ID=1367 on May 4, 2010. |
Snap-On Incorporated, EEDM596DK, Multimeter, Digital, Advanced, Manual Ranging, downloaded from the World Wide Web at http://buy1.snapon.com/catalog/item.asp?store=snapon-store&item—ID=84657&group—ID=1367 on May 4, 2010. |
Snap-On Incorporated, EEDM503D, Multimeter, Digital, Automotive, True RMS, downloaded from the World Wide Web at http://buy1.snapon.com/catalog/item.asp?store=snapon-store&item—ID=84656&group—ID=1367 on May 4, 2010. |
Fluke, 163/164 MultiFunction Counter Users Manual, Feb. 1, 1997. |
Fluke, Fluke 164 2.7 GHz Multifunction Counter Technical Data, May 10, 2007. |
Flores, J., Wireless Diagnostics and Consultancy Services, Vital Engineering, Jan. 4, 2007. |
Fluke, Fluke 199B / 003 Scopemeter 200 MHz, Dual Portable Multimeter and Oscilloscope, downloaded from the World Wide Web at http://web.archive.org/web/20100413065253/http://www.fluke199.com/ as archived on Apr. 12, 2010. |
Fluke Corporation, ScopeMeter 120 and 190 Series incl. 225C and 215C, Technical Data, Jan. 2010. |
Fluke Corporation, Fluke 19xC-2x5C Scopemeter, Software version 8.00 onwards, Users Manual, Jul. 2008. |
Jones, Mike, Senior FAE, Micrel Inc., Ethernet Driving Down Automotive Cost of Ownership; Oct. 31, 2008. |
U.S. Appl. No. 12/859,040, filed Aug. 18, 2010. |
U.S. Appl. No. 13/198,426, filed Aug. 4, 2011. |
U.S. Appl. No. 12/859,077, filed Aug. 18, 2010. |
U.S. Appl. No. 12/858,699, filed Aug. 18, 2010. |
U.S. Appl. No. 12/859,051, filed Aug. 18, 2010. |
U.S. Appl. No. 13/189,940, filed Jul. 25, 2011. |
U.S. Appl. No. 13/205,318, filed Aug. 8, 2011. |
U.S. Appl. No. 13/198,974, filed Aug. 5, 2011. |
U.S. Appl. No. 12/913,249, filed Oct. 27, 2010. |
U.S. Appl. No. 12/913,184, filed Oct. 27, 2010. |
U.S. Appl. No. 12/859,011, filed Aug. 18, 2010. |
U.S. Appl. No. 13/198,530, filed Aug. 4, 2011. |
U.S. Appl. No. 12/858,725, filed Aug. 18, 2010. |
Zussman, Gil et al. “Bluetooth Time Division Duplex-Analysis as a Polling System.” Obtained from World Wide Web at http://web.archive.org/web/20041230040105/http://www.mit.edu/˜gilz/pub—files/secon4.pdf available on Dec. 30, 2004. |
“OBDII Automotive Scan Tool and Virtual Dashboard.” OBD-2 Vehicle Explorer Scan Tool Browser. Obtained from World Wide Web at http://web.archive.org/web/20100723052216/http://obd-2.com/ available on Jul. 23, 2010. |
“Nology, PDA-Dyno and OBD II Scan Tool, Operating Manual.” Nology Engineering, Inc. Obtained from World Wide Web at http://web.archive.org/web/20100927062436/http://nology.com/pdfandzipfiles/pdadynousermanual.pdf available on Sep. 27, 2010. |
Metzelaar, R.H.M. “Peugeot 205 holding back.” Automotive Oscilloscope Applications—TiePie engineering 1996, 2010. |
Report Lab, OBD-II PIDs. Obtained from the World Wide Web at http://web.archive.org/web/20100329141311/http://en.wikipedia.org/wiki/OBD-II—PIDs available on Mar. 29, 2010. |
Bluetooth Architecture—Data Transport. Bluetooth Sig, Inc. Downloaded from the World Wide Web at http://developer.bluetooth.org/KnowledgeCenter/TechnologyOverview/Pages/DataTransport.aspx Accessed on Nov. 21, 2012. |
Number | Date | Country | |
---|---|---|---|
20120047458 A1 | Feb 2012 | US |