WO2007126549A2 - Vehicle diagnostic method and system with intelligent data collection - Google Patents

Vehicle diagnostic method and system with intelligent data collection Download PDF

Info

Publication number
WO2007126549A2
WO2007126549A2 PCT/US2007/005786 US2007005786W WO2007126549A2 WO 2007126549 A2 WO2007126549 A2 WO 2007126549A2 US 2007005786 W US2007005786 W US 2007005786W WO 2007126549 A2 WO2007126549 A2 WO 2007126549A2
Authority
WO
WIPO (PCT)
Prior art keywords
data
maintenance process
vehicle
occurrence
diagnostic
Prior art date
Application number
PCT/US2007/005786
Other languages
French (fr)
Other versions
WO2007126549A3 (en
Inventor
Matthew Gabriel Logsdon
Original Assignee
Snap-On Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Snap-On Incorporated filed Critical Snap-On Incorporated
Publication of WO2007126549A2 publication Critical patent/WO2007126549A2/en
Publication of WO2007126549A3 publication Critical patent/WO2007126549A3/en

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0808—Diagnosing performance data
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C2205/00—Indexing scheme relating to group G07C5/00
    • G07C2205/02—Indexing scheme relating to group G07C5/00 using a vehicle scan tool
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/006—Indicating maintenance

Definitions

  • the present disclosure relates to vehicle diagnostic methods and systems with intelligent data collection, and more specifically, to detecting an occurrence or completion of a maintenance process and responsively collecting and transmitting data related to the maintenance process.
  • the automotive diagnostic industry has been using data mining techniques to develop expert suggestions and identify effective fixes for vehicle problems.
  • Data related to maintenance activities is collected from garages located all over the country.
  • a group of human experts or expert computer systems then review and analyze the collected data for the purpose of identifying and validating effective fixes, and generating expert suggestions.
  • the effective fixes and expert suggestions are then implemented in diagnostic software or incorporated in user's manuals to assist technicians in performing diagnoses on vehicles.
  • This disclosure describes various vehicle diagnostic devices and methods that detect the occurrence or completion of a maintenance process performed on a vehicle, and responsive to the detected occurrence or completion of the maintenance process, initiate a data collection process to collect data related to the performed maintenance process.
  • the collected data may be transmitted to a remote data depository for further processing.
  • a data solicitation process is performed to solicit a user to input data related to the maintenance process.
  • the maintenance process may be performed in connection with a specific symptom.
  • the collected data includes at least one of an effective fix of the symptom and a description of the symptom.
  • a screen may
  • WDC99 1098226-1 066396.0253 be provided to display a message requesting input of the data related to the maintenance process.
  • the occurrence or completion of the maintenance process is determined based on the existence of a command to clear an error code, a change of a serial number associated with a controller on the vehicle, or a removal of an error code from an error code record.
  • the diagnostic device is implemented as an integral part of the vehicle.
  • FIG. 1 is a block diagram of an exemplary diagnostic system.
  • FIG. 2 shows an exemplary user interface providing suggestions of test procedures.
  • FIG. 3 depicts a block diagram of another exemplary diagnostic system for use with a vehicle.
  • FIG. 1 shows an exemplary diagnostic system 10 for use with a vehicle 11.
  • Diagnostic system 10 further includes a data processor 12 and a data storage device 19 for storing data.
  • data storage device 19 include floppy disks, hard disk drives, magnetic tapes, optical disks, such as CD-ROM, DVD, semiconductor storage devices, such as RAM, PROM, and EPROM, FLASH-EPROM, memory chips or cartridges, etc., or any combination(s) thereof.
  • Data processor 12, data storage device 19, sensors 17 and ECUs 18 are coupled to a diagnostic bus 16.
  • Data processor 12 performs diagnoses on various subsystems of vehicle 11 based on
  • diagnostic system 10 includes dashboard displays and/or user interface for informing the driver of various operating conditions and/or receiving input from the driver.
  • diagnostic system 10 includes a data communication device for establishing data links with a remote data processing system and/or a data network.
  • the data communication device can be an internet link, a wireless transceiver, a Bluetooth interface, etc. Data or information generated by diagnostic system 10 may be sent to a remote data processing system via the data communication device.
  • a data port 15 is provided for coupling to external devices, such as a scan tool 20.
  • data port 15 include OBD Il interface, USB connectors, wireless transceivers, or any type of data outlet for transmitting data.
  • Scan tools are widely used in the automotive diagnostic industry for communicating with, or downloading data from, on-board computers. Examples of scan tools include SOLUSTM Scanner made by Snap-on Inc. Scan tool 20 may further couple to another data processing system or a data network, such as the internet, so that data generated by diagnostic system 10 or scan tool 20 can be transmitted to, or accessed by, other data processing systems.
  • sensors 17 and ECUs 18 constantly collect and deliver operation information related to various subsystems of vehicle 11 to data processor 12.
  • ECUs 18 generate and store error codes indicating errors encountered by ECUs 18 and/or their associated subsystems. The operation
  • WDC99 IO98226-I 0663960253 information and/or error codes are sent to data processor 12 and stored in data storage device 19.
  • scan tool 20 is connected to OBD Il port 15 to download error codes stored in diagnostic system 10. Based on the downloaded error codes, a technician determines what symptoms or problems are encountered by vehicle 11 , and what types of errors occurred in which subsystems of vehicle 11. Appropriate analysis and repair can then be performed to pinpoint trouble spots and cure the problem. If needed, old ECUs 18 or parts are replaced by new ECUs or parts.
  • Some scan tools integrate diagnostics, tests and scanner functions on a single device.
  • FIG. 2 shows an exemplary user interface 30 of scan tool 20.
  • User interface 30 includes icons respectively designated as "Vehicle Identification” and "Test/Analysis.”
  • Vehicle Identification icon When the Vehicle Identification icon is selected, scan tool presents the user with a number of questions or fields, such as model year, make, model name, engine size and the like, each field presenting the user with a menu of unique values from within that field from which the user may select to identify the vehicle under diagnosis.
  • test/Analysis icon 32 brings up a screen display 39 as shown in FIG. 2.
  • a list of symptoms 40 related to vehicle 11 is displayed.
  • the screen display 39 presents a list 42 of possible causes of the symptom or symptoms selected and an associate list of test procedures to be performed to check for those causes. The test procedures are listed in the order of the probability or likelihood that the test will be successful in diagnosing the cause of the
  • scan tool 20 presents a list of suggested fixes for each symptoms such that the user may proceed to repair the vehicle directly.
  • Diagnostic system 10 has the capacity to determine when a maintenance process or repair work has been performed or completed on vehicle 11 , and responsively transmits data related to the maintenance process to a remote data server for data mining purpose.
  • the technician after the technician finishes a maintenance job to repair certain subsystems of vehicle 11 , the technician is required to issue an erase command or a clear code via scan tool 20 to clear the error codes stored in diagnostic system 10.
  • the format of the erase command or clear code may be in the format of: [0022] ID of erase command + ID of error code to be erased
  • diagnostic system 10 In response to the erase command or clear code, the error code associated with the fixed problem is removed or erased from the data storage device 19 and/or associated ECUs 18. Diagnostic system 10 constantly monitors commands sent from scan tool 20. According to the receipt of an erase command or clear code, diagnostic system 10 determines that a maintenance process has occurred or completed. Based on the content of the erase command, the error code to be erased by the erase command can be determined. According to
  • diagnostic system 10 stores a list of all error codes representing all errors encountered by the subsystems of vehicle 11. Whenever a problem is fixed, the technician is required to issue an erase command or clear code to remove the corresponding error code stored in ECUs and/or the list of error codes maintained by diagnostic system 10. Thus, the removal of an error code indicates that a maintenance process has been performed on vehicle 11 to repair certain problems. [0024] According to still another embodiment, diagnostic system 10 keeps track of serial numbers of ECUs 18 and/or parts installed in vehicle 11.
  • Each ECU reads serial numbers of the parts in its associated subsystem, and communicates with data processor 12 to convey the serial numbers.
  • a list of serial numbers of ECUs 18 and/or the parts of vehicle 11 is maintained in data storage device 19. Whenever a new ECU or part is installed, the list of serial numbers is updated accordingly.
  • Diagnostic system 10 detects the occurrence or completion of a maintenance process based on the existence of a new part installed in vehicle 11. If the technician replaces an old part with a new part to fix a problem, the serial number of the new part is reported to data processor 12. Based on the receipt of the information related to the new part, diagnostic system 10 determines that a maintenance process has occurred.
  • diagnostic system 10 In response to the determination that a maintenance process has been performed on vehicle 11, diagnostic system 10 generates a message to solicit data
  • the message is displayed on a dashboard display.
  • diagnostic system 10 sends a command to scan tool 20 to display a message on scan tool 20 to solicit data input from the technician regarding the tasks performed on the vehicle.
  • the technician enters his or her input via the user interface of diagnostic system 10, such as a dashboard display and input buttons of the vehicle, or via the user interface of scan tool 20.
  • the data to be input by the technician includes vehicle information, symptoms and/or problems encountered by vehicle 11 , identification of failed subsystems or parts, tests performed during the diagnoses, etc.
  • diagnostic system 10 in addition to the information entered by the technician, diagnostic system 10 also collects and compiles additional data related to the maintenance process.
  • the additional data may be any data that is stored in diagnostic system 10 and/or scan tool 20, and associated with the failed parts, the performed tests and diagnoses, attributes of the vehicles (year, make, model, engine particulars, etc.), operation history of the vehicle, symptoms or faults, effective tests for finding causes of a specific symptom, effective fixes corresponding to a specific fault, measurements obtained during the diagnoses, information obtained from vehicle onboard computers, additional comments/descriptions entered by technicians, ineffective tests/fixes corresponding to various symptoms/faults, information related to the technician who conducted the diagnostics, etc.
  • Diagnostic system 10 then initiates a data transmission process to send the data collected from the technician and/or any additional data relating to the vehicle
  • diagnostic system 10 stores the collected data and any additional data related to the maintenance process in data storage device 19, such that the data related to the maintenance process is not lost. If at a later time, vehicle 11 is brought to another maintenance facility that has the data transmission capacity, diagnostic system 10 initiates a data transmission process to transmit the stored data to the remote data depository.
  • the above-described functions are implemented by machine-readable instructions stored in data storage device 19, and for execution by data processor 12 of diagnostic system 10.
  • the detection of the occurrence or completion of a maintenance process, and the transmission of diagnostic data are performed by scan tool 20.
  • scan tool 20 determines that a maintenance process has occurred.
  • scan tool 20 prompts the technician to input data related to the maintenance service.
  • Scan tool 20 may also communicate with diagnostic system 10 to
  • WDC99 1098226-1.066396.0253 obtain data that is stored in diagnostic system 10 and related to the fault cured by the maintenance process.
  • Scan tool 20 then initiates a process to send the collected data and/or any additional data relating to the vehicle problem and the maintenance process to the remote data depository for further processing or data mining purpose.
  • the additional data may be any data that is stored in scan tool 20 and/or diagnostic system 10, and associated with the failed parts, the performed tests and diagnoses, attributes of the vehicles (year, make, model, engine particulars, etc.), symptoms or faults, effective tests for finding causes of a specific symptom, effective fixes corresponding to a specific fault, measurements obtained during the diagnoses, information obtained from vehicle on-board computers, additional comments/descriptions entered by technicians, ineffective tests/fixes corresponding to various symptoms/faults, information related to the technician who conducted the diagnostics, etc.
  • Fig. 3 depicts a block diagram of another embodiment of a diagnostic system 30 for use with an on-board diagnostic system 35 of a vehicle 31.
  • On-board diagnostic system 35 is substantially similar to the diagnostic system 10 shown in Fig. 1. Elements having the same reference numeral designations represent like elements throughout.
  • Data processor 32 executes instructions stored in storage device 39 and performs diagnoses on various subsystems of vehicle 11 based on information provided by ECUs 18 and sensors 17, and records error codes in data storage device 19.
  • diagnostic system 36 is implemented as a separate device from on-board diagnostic system 35.
  • a data processor 36 is provided to process data and execute instructions. Diagnostic system 36 further includes a wireless
  • VVDC99 1098226-1.066396.0253 communication device 38 for establishing wireless communications with a data processing system that is external to the vehicle.
  • Diagnostic system 36 is detachably connected to on-board diagnostic system 35 via a connector which couples diagnostic system 36 to bus 16 of on-board diagnostic system 35.
  • CPU 37 constantly monitors the signals and traffic on bus 16. As discussed earlier, after the technician finishes a maintenance job to repair certain subsystems of vehicle 31 , the technician is required to issue an erase command or a clear code via a scan tool connected to data port 15 to clear the error codes stored in on-board diagnostic system 35. The clear code is sent from the scan tool to on-board diagnostic system 35 via bus 16. According to the receipt of an erase command or clear code detected on bus 16, diagnostic system 36 determines that a maintenance process has occurred or completed. Based on the content of the erase command, the error code to be erased by the erase command can be determined. [0035] According to another embodiment, the occurrence or completion of a maintenance process is determined based on a change of an error code list. Diagnostic system 36 constantly monitors the error codes generated by ECUs 18 or sensors 17, and maintains a list of all error codes representing all errors encountered by the subsystems of vehicle 31.
  • diagnostic system 36 communicates with ECUs 18 and/or parts installed in vehicle 31 , and keeps track of the serial numbers or IDs thereof.
  • the list of serial numbers or IDs can also be obtained by communicating with data processor 32. Whenever a new ECU 18 or part is installed, the list of serial numbers is updated accordingly. The replacement of a new part installed in vehicle 31 indicates that a maintenance process has occurred or completed on vehicle 31. Based on the receipt of the information related to the new part, diagnostic system 36 determines that a maintenance process has occurred.
  • diagnostic system 36 In response to the determination that a maintenance process has been performed on vehicle 31 , diagnostic system 36 performs a process to solicit input from a technician regarding the tasks performed on vehicle 31. The process is similar to those described related to Figs. 1 and 2.
  • Diagnostic system 36 then initiates a data transmission process to send the data collected from the technician, the error codes cleared and/or any data relating to the vehicle problem and the maintenance process, to a remote data depository for further processing or data mining.
  • the transmission of the data is performed in various manners, such as via the communication device 38 of diagnostic system 36, via a scan tool connected to data port 15, or via any other communication devices coupled to vehicle 31 , such as an on-vehicle wireless phone.
  • diagnostic system 36 stores the collected data in a storage device for later access.
  • WDC99 1098226- 1.066396.02S3 [0040] After the data is transmitted to the data depository, the data can be used for data mining and/or any further analyses and uses. Detailed process related to data mining and further processing of the transmitted data are described in U.S. Patent Application No. 10/613,230 (attorney docket No. 10473-998), titled DISTRIBUTED EXPERT DIAGNOSTIC SERVICE AND SYSTEM, filed on July 7. 2003 and commonly assigned to the assignee of this application, the disclosure of which is incorporated herein by reference in its entirety.

Abstract

Vehicle diagnostic devices and methods that detect the occurrence of a maintenance process performed on a vehicle, and responsive to the detected occurrence of the maintenance process, initiate a data collection process to collect data related to the performed maintenance process, and a data transmission process to provide the collected data to a remote data depository.

Description

Attorney Docket No. 066396-0253
VEHICLE DIAGNOSTIC METHOD AND SYSTEM WITH INTELLIGENT DATA COLLECTION
FIELD OF DISCLOSURE
[0001] The present disclosure relates to vehicle diagnostic methods and systems with intelligent data collection, and more specifically, to detecting an occurrence or completion of a maintenance process and responsively collecting and transmitting data related to the maintenance process.
BACKGROUND OF THE DISCLOSURE
[0002] The automotive diagnostic industry has been using data mining techniques to develop expert suggestions and identify effective fixes for vehicle problems. Data related to maintenance activities is collected from garages located all over the country. A group of human experts or expert computer systems then review and analyze the collected data for the purpose of identifying and validating effective fixes, and generating expert suggestions. The effective fixes and expert suggestions are then implemented in diagnostic software or incorporated in user's manuals to assist technicians in performing diagnoses on vehicles.
[0003] The process of collecting diagnostic data is often tedious and requires a lot of human work and intervention. Some garages require technicians to write down steps and services that they perform on each vehicle. A clerk then reviews, compiles and enter the data into a computer system for transmission to a remote data depository
- 1 -
WDC99 1098226-1 066396 0253 such that data mining can be performed. However, not all garages have the resources or capacity needed to collect and transmit diagnostic data. Some garages do not have enough manpower to compile and enter the diagnostic data, while others do not have the hardware or equipment to transmit the data. As a result, a lot of valuable data is unavailable for analysis due to difficulties in collecting or transmitting diagnostic data. [0004] Therefore, there is a need to automate the process of collecting diagnostic data. There is another need to identify the occurrence or completion of a maintenance process and collect the diagnostic data. There is a further need to timely transmit the diagnostic data to a data depository.
SUMMARY OF THE DISCLOSURE
[0005] This disclosure describes various vehicle diagnostic devices and methods that detect the occurrence or completion of a maintenance process performed on a vehicle, and responsive to the detected occurrence or completion of the maintenance process, initiate a data collection process to collect data related to the performed maintenance process. The collected data may be transmitted to a remote data depository for further processing.
[0006] In one embodiment, responsive to the detected occurrence or completion of the maintenance process, a data solicitation process is performed to solicit a user to input data related to the maintenance process. The maintenance process may be performed in connection with a specific symptom. The collected data includes at least one of an effective fix of the symptom and a description of the symptom. A screen may
- 2 -
WDC99 1098226-1 066396.0253 be provided to display a message requesting input of the data related to the maintenance process.
[0007] In another embodiment, the occurrence or completion of the maintenance process is determined based on the existence of a command to clear an error code, a change of a serial number associated with a controller on the vehicle, or a removal of an error code from an error code record. In another embodiment, the diagnostic device is implemented as an integral part of the vehicle.
[0008] Additional advantages and novel features of the present disclosure will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following, or may be learned by practice of the present disclosure. The drawings and description are to be regarded as illustrative in nature, and not as restrictive. The advantages of the present disclosure may be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0009] The present disclosure is illustrated by way of example, and not by way of limitation, in the accompanying drawings, wherein elements having the same reference numeral designations represent like elements throughout and wherein:
[0010] Fig. 1 is a block diagram of an exemplary diagnostic system.
[0011] FIG. 2 shows an exemplary user interface providing suggestions of test procedures.
- 3 -
WDC99 1098226-1.0663960253 [0012] FIG. 3 depicts a block diagram of another exemplary diagnostic system for use with a vehicle.
DETAILED DESCRIPTIONS OF ILLUSTRATIVE EMBODIMENTS
[0013] In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be apparent, however, to one skilled in the art that concepts of the disclosure may be practiced or implemented without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present disclosure.
System Architecture
[0014] Fig. 1 shows an exemplary diagnostic system 10 for use with a vehicle 11.
Sensors 17 and electronic control units (ECUs) 18 are disposed at various portions of vehicle 11 to control the operations, and collect operation data, of various subsystems or parts of the vehicle, such as engine, transmission, tires, electronic system, AC, oil level, emission, etc. Diagnostic system 10 further includes a data processor 12 and a data storage device 19 for storing data. Examples of data storage device 19 include floppy disks, hard disk drives, magnetic tapes, optical disks, such as CD-ROM, DVD, semiconductor storage devices, such as RAM, PROM, and EPROM, FLASH-EPROM, memory chips or cartridges, etc., or any combination(s) thereof. Data processor 12, data storage device 19, sensors 17 and ECUs 18 are coupled to a diagnostic bus 16. Data processor 12 performs diagnoses on various subsystems of vehicle 11 based on
- 4 -
WDC99 1098226-1.066396.0253 information provided by ECUs 18 and sensors 17, and records error codes in data storage device 19. In one embodiment, diagnostic system 10 includes dashboard displays and/or user interface for informing the driver of various operating conditions and/or receiving input from the driver. In another embodiment, diagnostic system 10 includes a data communication device for establishing data links with a remote data processing system and/or a data network. For example, the data communication device can be an internet link, a wireless transceiver, a Bluetooth interface, etc. Data or information generated by diagnostic system 10 may be sent to a remote data processing system via the data communication device.
[0015] A data port 15 is provided for coupling to external devices, such as a scan tool 20. Examples of data port 15 include OBD Il interface, USB connectors, wireless transceivers, or any type of data outlet for transmitting data. Scan tools are widely used in the automotive diagnostic industry for communicating with, or downloading data from, on-board computers. Examples of scan tools include SOLUS™ Scanner made by Snap-on Inc. Scan tool 20 may further couple to another data processing system or a data network, such as the internet, so that data generated by diagnostic system 10 or scan tool 20 can be transmitted to, or accessed by, other data processing systems.
System Operation
[0016] In operation, sensors 17 and ECUs 18 constantly collect and deliver operation information related to various subsystems of vehicle 11 to data processor 12. In one embodiment, ECUs 18 generate and store error codes indicating errors encountered by ECUs 18 and/or their associated subsystems. The operation
- 5 -
WDC99 IO98226-I 0663960253 information and/or error codes are sent to data processor 12 and stored in data storage device 19. During a diagnostic process, scan tool 20 is connected to OBD Il port 15 to download error codes stored in diagnostic system 10. Based on the downloaded error codes, a technician determines what symptoms or problems are encountered by vehicle 11 , and what types of errors occurred in which subsystems of vehicle 11. Appropriate analysis and repair can then be performed to pinpoint trouble spots and cure the problem. If needed, old ECUs 18 or parts are replaced by new ECUs or parts. [0017] Some scan tools integrate diagnostics, tests and scanner functions on a single device. FIG. 2 shows an exemplary user interface 30 of scan tool 20. User interface 30 includes icons respectively designated as "Vehicle Identification" and "Test/Analysis." When the Vehicle Identification icon is selected, scan tool presents the user with a number of questions or fields, such as model year, make, model name, engine size and the like, each field presenting the user with a menu of unique values from within that field from which the user may select to identify the vehicle under diagnosis.
[0018] Once the vehicle is identified, the user is able to begin diagnosis by selecting the Test/Analysis icon 32, scan tool 20 brings up a screen display 39 as shown in FIG. 2. A list of symptoms 40 related to vehicle 11 is displayed. [0019] When a user selects one or more of the listed symptoms that are exhibited by the vehicle under test, the screen display 39 presents a list 42 of possible causes of the symptom or symptoms selected and an associate list of test procedures to be performed to check for those causes. The test procedures are listed in the order of the probability or likelihood that the test will be successful in diagnosing the cause of the
- 6 -
WDC99 1098226-1.066396.0253 selected symptom or symptoms. In one embodiment, scan tool 20 presents a list of suggested fixes for each symptoms such that the user may proceed to repair the vehicle directly.
Detection Of Occurrence Of Maintenance Process
[0020] Diagnostic system 10 has the capacity to determine when a maintenance process or repair work has been performed or completed on vehicle 11 , and responsively transmits data related to the maintenance process to a remote data server for data mining purpose.
[0021] In one embodiment, after the technician finishes a maintenance job to repair certain subsystems of vehicle 11 , the technician is required to issue an erase command or a clear code via scan tool 20 to clear the error codes stored in diagnostic system 10. The format of the erase command or clear code may be in the format of: [0022] ID of erase command + ID of error code to be erased
[0023] For instance, according to the SAE (Society of Automotive Engineers)
Recommended Practices, a technician is required to issue a DM3 command or PID 195 command to erase error codes stored in diagnostic system 10. In response to the erase command or clear code, the error code associated with the fixed problem is removed or erased from the data storage device 19 and/or associated ECUs 18. Diagnostic system 10 constantly monitors commands sent from scan tool 20. According to the receipt of an erase command or clear code, diagnostic system 10 determines that a maintenance process has occurred or completed. Based on the content of the erase command, the error code to be erased by the erase command can be determined. According to
- 7 -
WDC99 1098226-1.066396.0253 another embodiment, the occurrence or completion of a maintenance process is determined based on a change of an error code list maintained in diagnostic system 10. As discussed earlier, diagnostic system 10 stores a list of all error codes representing all errors encountered by the subsystems of vehicle 11. Whenever a problem is fixed, the technician is required to issue an erase command or clear code to remove the corresponding error code stored in ECUs and/or the list of error codes maintained by diagnostic system 10. Thus, the removal of an error code indicates that a maintenance process has been performed on vehicle 11 to repair certain problems. [0024] According to still another embodiment, diagnostic system 10 keeps track of serial numbers of ECUs 18 and/or parts installed in vehicle 11. Each ECU reads serial numbers of the parts in its associated subsystem, and communicates with data processor 12 to convey the serial numbers. A list of serial numbers of ECUs 18 and/or the parts of vehicle 11 is maintained in data storage device 19. Whenever a new ECU or part is installed, the list of serial numbers is updated accordingly. Diagnostic system 10 detects the occurrence or completion of a maintenance process based on the existence of a new part installed in vehicle 11. If the technician replaces an old part with a new part to fix a problem, the serial number of the new part is reported to data processor 12. Based on the receipt of the information related to the new part, diagnostic system 10 determines that a maintenance process has occurred.
Solicitation Of Data Input And Data Transmission
[0025] In response to the determination that a maintenance process has been performed on vehicle 11, diagnostic system 10 generates a message to solicit data
- 8 -
WDC99 I098226-1.O66396.O253 input from the technician regarding the tasks performed on the vehicle. In one embodiment, the message is displayed on a dashboard display. According to another embodiment, diagnostic system 10 sends a command to scan tool 20 to display a message on scan tool 20 to solicit data input from the technician regarding the tasks performed on the vehicle.
[0026] The technician enters his or her input via the user interface of diagnostic system 10, such as a dashboard display and input buttons of the vehicle, or via the user interface of scan tool 20. In one embodiment, the data to be input by the technician includes vehicle information, symptoms and/or problems encountered by vehicle 11 , identification of failed subsystems or parts, tests performed during the diagnoses, etc. [0027] In another embodiment, in addition to the information entered by the technician, diagnostic system 10 also collects and compiles additional data related to the maintenance process. The additional data may be any data that is stored in diagnostic system 10 and/or scan tool 20, and associated with the failed parts, the performed tests and diagnoses, attributes of the vehicles (year, make, model, engine particulars, etc.), operation history of the vehicle, symptoms or faults, effective tests for finding causes of a specific symptom, effective fixes corresponding to a specific fault, measurements obtained during the diagnoses, information obtained from vehicle onboard computers, additional comments/descriptions entered by technicians, ineffective tests/fixes corresponding to various symptoms/faults, information related to the technician who conducted the diagnostics, etc.
[0028] Diagnostic system 10 then initiates a data transmission process to send the data collected from the technician and/or any additional data relating to the vehicle
- 9 -
WDC99 1O98226-I.O66396.O253 problem and the maintenance process, to a remote data depository for further processing or data mining. The transmission of the data is performed via the communication device of diagnostic system 10, via scan tool 20, or via any other communication devices coupled to diagnostic system 10. If vehicle 11 or the garage that performs the maintenance process does not have data transmission capacity, diagnostic system 10 stores the collected data and any additional data related to the maintenance process in data storage device 19, such that the data related to the maintenance process is not lost. If at a later time, vehicle 11 is brought to another maintenance facility that has the data transmission capacity, diagnostic system 10 initiates a data transmission process to transmit the stored data to the remote data depository.
[0029] In one embodiment, the above-described functions are implemented by machine-readable instructions stored in data storage device 19, and for execution by data processor 12 of diagnostic system 10.
[0030] In another embodiment, the detection of the occurrence or completion of a maintenance process, and the transmission of diagnostic data are performed by scan tool 20. As discussed earlier, after a technician finishes a maintenance job to repair certain subsystems of vehicle 11 , the technician is required to issue an erase command or a clear code via scan tool 20 to diagnostic system 10 to clear the error codes stored in diagnostic system 10. Therefore, whenever an input to issue an erase command or a clear code is to be issued, scan tool 20 determines that a maintenance process has occurred. In response, scan tool 20 prompts the technician to input data related to the maintenance service. Scan tool 20 may also communicate with diagnostic system 10 to
- 10 -
WDC99 1098226-1.066396.0253 obtain data that is stored in diagnostic system 10 and related to the fault cured by the maintenance process.
[0031] Scan tool 20 then initiates a process to send the collected data and/or any additional data relating to the vehicle problem and the maintenance process to the remote data depository for further processing or data mining purpose. The additional data may be any data that is stored in scan tool 20 and/or diagnostic system 10, and associated with the failed parts, the performed tests and diagnoses, attributes of the vehicles (year, make, model, engine particulars, etc.), symptoms or faults, effective tests for finding causes of a specific symptom, effective fixes corresponding to a specific fault, measurements obtained during the diagnoses, information obtained from vehicle on-board computers, additional comments/descriptions entered by technicians, ineffective tests/fixes corresponding to various symptoms/faults, information related to the technician who conducted the diagnostics, etc.
[0032] Fig. 3 depicts a block diagram of another embodiment of a diagnostic system 30 for use with an on-board diagnostic system 35 of a vehicle 31. On-board diagnostic system 35 is substantially similar to the diagnostic system 10 shown in Fig. 1. Elements having the same reference numeral designations represent like elements throughout. Data processor 32 executes instructions stored in storage device 39 and performs diagnoses on various subsystems of vehicle 11 based on information provided by ECUs 18 and sensors 17, and records error codes in data storage device 19. [0033] In this embodiment, diagnostic system 36 is implemented as a separate device from on-board diagnostic system 35. A data processor 36 is provided to process data and execute instructions. Diagnostic system 36 further includes a wireless
- 11 -
VVDC99 1098226-1.066396.0253 communication device 38 for establishing wireless communications with a data processing system that is external to the vehicle. Diagnostic system 36 is detachably connected to on-board diagnostic system 35 via a connector which couples diagnostic system 36 to bus 16 of on-board diagnostic system 35.
[0034] CPU 37 constantly monitors the signals and traffic on bus 16. As discussed earlier, after the technician finishes a maintenance job to repair certain subsystems of vehicle 31 , the technician is required to issue an erase command or a clear code via a scan tool connected to data port 15 to clear the error codes stored in on-board diagnostic system 35. The clear code is sent from the scan tool to on-board diagnostic system 35 via bus 16. According to the receipt of an erase command or clear code detected on bus 16, diagnostic system 36 determines that a maintenance process has occurred or completed. Based on the content of the erase command, the error code to be erased by the erase command can be determined. [0035] According to another embodiment, the occurrence or completion of a maintenance process is determined based on a change of an error code list. Diagnostic system 36 constantly monitors the error codes generated by ECUs 18 or sensors 17, and maintains a list of all error codes representing all errors encountered by the subsystems of vehicle 31.
[0036] Whenever a problem is fixed, the technician is required to issue an erase command or clear code to remove the corresponding error code stored in ECUs 18 and or data storage device 39. The erase command or clear code can be detected by diagnostic system 36 by monitoring the traffic of bus 16. The list of error codes maintained by diagnostic system 36 is updated or revised accordingly. Thus, the
- 12 -
\VDC99 1098226-l.066396.0253 removal of an error code indicates that a maintenance process has been performed on vehicle 31 to repair certain problems.
[0037] According to still another embodiment, diagnostic system 36 communicates with ECUs 18 and/or parts installed in vehicle 31 , and keeps track of the serial numbers or IDs thereof. The list of serial numbers or IDs can also be obtained by communicating with data processor 32. Whenever a new ECU 18 or part is installed, the list of serial numbers is updated accordingly. The replacement of a new part installed in vehicle 31 indicates that a maintenance process has occurred or completed on vehicle 31. Based on the receipt of the information related to the new part, diagnostic system 36 determines that a maintenance process has occurred. [0038] In response to the determination that a maintenance process has been performed on vehicle 31 , diagnostic system 36 performs a process to solicit input from a technician regarding the tasks performed on vehicle 31. The process is similar to those described related to Figs. 1 and 2.
[0039] Diagnostic system 36 then initiates a data transmission process to send the data collected from the technician, the error codes cleared and/or any data relating to the vehicle problem and the maintenance process, to a remote data depository for further processing or data mining. The transmission of the data is performed in various manners, such as via the communication device 38 of diagnostic system 36, via a scan tool connected to data port 15, or via any other communication devices coupled to vehicle 31 , such as an on-vehicle wireless phone. In one embodiment, diagnostic system 36 stores the collected data in a storage device for later access.
- 13 -
WDC99 1098226- 1.066396.02S3 [0040] After the data is transmitted to the data depository, the data can be used for data mining and/or any further analyses and uses. Detailed process related to data mining and further processing of the transmitted data are described in U.S. Patent Application No. 10/613,230 (attorney docket No. 10473-998), titled DISTRIBUTED EXPERT DIAGNOSTIC SERVICE AND SYSTEM, filed on July 7. 2003 and commonly assigned to the assignee of this application, the disclosure of which is incorporated herein by reference in its entirety.
[0041] In the previous descriptions, numerous specific details are set forth, such as specific materials, structures, processes, etc., in order to provide a thorough understanding of the present disclosure. However, as one having ordinary skill in the art would recognize, the present disclosure can be practiced without resorting to the details specifically set forth. In other instances, well known processing structures have not been described in detail in order not to unnecessarily obscure the present disclosure. It is to be understood that the disclosure is capable of use in various other combinations and environments and is capable of changes or modifications within the scope of the inventive concept as expressed herein.
- 14 -
WDC99 1098226-1.066396.0253

Claims

CLAIMSWHAT IS CLAIMED IS:
1. A vehicle diagnostic method including the steps of: detecting an occurrence of a maintenance process performed on a vehicle; responsive to the detected occurrence of the maintenance process, initiating a data collection process to collect data related to the maintenance process; and initiating a data transmission process to transmit the collected data related to the maintenance process to a remote data processing system.
2. The method of claim 1 further comprising the step of soliciting input of the data related to the maintenance process from a user.
3. The method of claim 2, wherein: the maintenance process is performed in connection with a specific symptom; and the collected data includes at least one of an effective fix of the symptom and a description of the symptom.
4. The method of claim 2, wherein the soliciting step includes displaying a message requesting an input of the data related to the maintenance process.
5. The method of claim 1 , wherein the occurrence of the maintenance process is determined based on the existence of a command to clear an error code, a
- 15 -
WDC99 1098226-1.066396.0253 change of a serial number associated with a controller on the vehicle, or a removal of an error code from an error code record.
6. A vehicle diagnostic device comprising: a data processing unit configured to process data; and a storage device storing instructions that, upon execution by the data processing unit, control the diagnostic device to perform the steps of: detecting an occurrence of a maintenance process performed on a vehicle; responsive to the detected occurrence of the maintenance process, initiating a data collection process to collect data related to the maintenance process; and initiating a data transmission process to transmit the collected data related to the maintenance process to a remote data processing system.
7. The device of claim 6, wherein the instructions, upon execution by the data processing unit, control the diagnostic device to solicit input of the data related to the maintenance process from a user.
8. The device of claim 7, wherein: the maintenance process is performed in connection with a specific symptom; and
- 16 -
WDC99 1098226-1 0663960253 the collected data includes at least one of an effective fix of the symptom and a description of the symptom.
9. The device of claim 7 further including a screen configured to display a message requesting an input of the data related to the maintenance process.
10. The device of claim 6, wherein the occurrence of the maintenance process is determined based on the existence of a command to clear an error code, a change of a serial number associated with a controller on the vehicle, or a removal of an error code from an error code record.
11. The device of claim 6, wherein the device is non-integral to the vehicle and configured to couple to a data port of the vehicle to communicate with an on-board computer of the vehicle.
12. The device of claim 11, wherein the data port is an OBD Il interface.
13. The device of claim 6 further including a connector for coupling to a data bus of an on-board diagnostic system of the vehicle.
14. The device of claim 6, wherein the data is transmitted in a wireless manner.
- 17 -
WDC99 1098226-1.066396.0253
15. A vehicle diagnostic device comprising: data processing means for processing data; and storage means for storing instructions that, upon execution by the data processing means, controls the diagnostic device to perform the steps of: detecting an occurrence of a maintenance process performed on a vehicle; responsive to the detected occurrence of the maintenance process, initiating a data collection process to collect data related to the maintenance process; and initiating a data transmission process to transmit the collected data to a remote data processing system.
- 18 -
WDC99 1098226-1 0663960253
PCT/US2007/005786 2006-03-29 2007-03-09 Vehicle diagnostic method and system with intelligent data collection WO2007126549A2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/394,038 2006-03-29
US11/394,038 US7739007B2 (en) 2006-03-29 2006-03-29 Vehicle diagnostic method and system with intelligent data collection

Publications (2)

Publication Number Publication Date
WO2007126549A2 true WO2007126549A2 (en) 2007-11-08
WO2007126549A3 WO2007126549A3 (en) 2008-01-03

Family

ID=38560398

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/005786 WO2007126549A2 (en) 2006-03-29 2007-03-09 Vehicle diagnostic method and system with intelligent data collection

Country Status (2)

Country Link
US (1) US7739007B2 (en)
WO (1) WO2007126549A2 (en)

Families Citing this family (92)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9824507B2 (en) * 2005-06-30 2017-11-21 Innova Electronics Corporation Mobile device based vehicle diagnostic system
US7739007B2 (en) * 2006-03-29 2010-06-15 Snap-On Incorporated Vehicle diagnostic method and system with intelligent data collection
US7953530B1 (en) * 2006-06-08 2011-05-31 Pederson Neal R Vehicle diagnostic tool
US7765040B2 (en) * 2006-06-14 2010-07-27 Spx Corporation Reverse failure analysis method and apparatus for diagnostic testing
US8762165B2 (en) 2006-06-14 2014-06-24 Bosch Automotive Service Solutions Llc Optimizing test procedures for a subject under test
US7643916B2 (en) 2006-06-14 2010-01-05 Spx Corporation Vehicle state tracking method and apparatus for diagnostic testing
US9081883B2 (en) 2006-06-14 2015-07-14 Bosch Automotive Service Solutions Inc. Dynamic decision sequencing method and apparatus for optimizing a diagnostic test plan
US8428813B2 (en) 2006-06-14 2013-04-23 Service Solutions Us Llc Dynamic decision sequencing method and apparatus for optimizing a diagnostic test plan
US8423226B2 (en) * 2006-06-14 2013-04-16 Service Solutions U.S. Llc Dynamic decision sequencing method and apparatus for optimizing a diagnostic test plan
US20100324376A1 (en) * 2006-06-30 2010-12-23 Spx Corporation Diagnostics Data Collection and Analysis Method and Apparatus
US7908053B2 (en) * 2007-07-02 2011-03-15 Honeywell International Inc. Apparatus and method for troubleshooting a computer system
JP5144169B2 (en) * 2007-08-17 2013-02-13 本田技研工業株式会社 Cogeneration equipment
WO2009058972A2 (en) * 2007-10-30 2009-05-07 Sosy Technologies Stu, Inc. An apparatus for collecting, storing and transmitting vehicle information
US20090265364A1 (en) * 2008-04-16 2009-10-22 Gm Global Technology Operations, Inc. Method and process for automatic generation of symptom codes from textual problem descriptions to enable problem classification, early warning trend prediction, and fast recall of prognostic/diagnostic solutions
US20090271066A1 (en) * 2008-04-23 2009-10-29 Underdal Olav M Diagnostic data mining
US8239094B2 (en) * 2008-04-23 2012-08-07 Spx Corporation Test requirement list for diagnostic tests
JP4475346B2 (en) * 2008-05-13 2010-06-09 トヨタ自動車株式会社 Fault diagnosis system and in-vehicle ECU used therefor
CA2736168C (en) 2008-09-09 2018-04-10 United Parcel Service Of America, Inc. Systems and methods of utilizing telematics data to improve fleet management operations
US11482058B2 (en) 2008-09-09 2022-10-25 United Parcel Service Of America, Inc. Systems and methods for utilizing telematics data to improve fleet management operations
US8812172B2 (en) 2008-09-15 2014-08-19 Hti Ip, Llc Method for generating a vehicle identifier
TWI377469B (en) * 2008-11-13 2012-11-21 Transcend Information Inc Storage apparatus and on-line client service system, soft and method thereof
US8656227B2 (en) 2008-11-13 2014-02-18 Transcend Information, Inc. On-line client service method for storage apparatus
US8095261B2 (en) * 2009-03-05 2012-01-10 GM Global Technology Operations LLC Aggregated information fusion for enhanced diagnostics, prognostics and maintenance practices of vehicles
US20100318396A1 (en) * 2009-06-15 2010-12-16 Infosys Technologies Limited Framework for supporting repair processes of aircraft
US8648700B2 (en) 2009-06-23 2014-02-11 Bosch Automotive Service Solutions Llc Alerts issued upon component detection failure
US8612086B2 (en) * 2009-09-01 2013-12-17 Bosch Automotive Service Solutions Llc Diagnostic device wireless interface via diagnostic cable adapter
US8972804B2 (en) * 2010-09-16 2015-03-03 Xerox Corporation Point of need access to an electronic maintenance manual utilizing current machine status
US20120185124A1 (en) * 2011-01-18 2012-07-19 Control-Tec, Llc Automated vehicle-wide data acquisition and issue management system
US10482475B2 (en) 2011-02-10 2019-11-19 Adp Dealer Services, Inc. Systems and methods for providing targeted advertising
ITBO20110063A1 (en) * 2011-02-15 2012-08-16 Ferrari Spa METHOD AND SYSTEM OF DIAGNOSIS OF A ROAD VEHICLE PROVIDED WITH AN ON-BOARD CONTROL UNIT
US20120215491A1 (en) * 2011-02-21 2012-08-23 Snap-On Incorporated Diagnostic Baselining
US9208626B2 (en) 2011-03-31 2015-12-08 United Parcel Service Of America, Inc. Systems and methods for segmenting operational data
US9953468B2 (en) 2011-03-31 2018-04-24 United Parcel Service Of America, Inc. Segmenting operational data
DE102011101505A1 (en) * 2011-05-13 2012-11-15 Still Gmbh Method for managing industrial trucks and industrial trucks
US8958945B2 (en) 2012-02-07 2015-02-17 Ge Aviation Systems Llc System and methods for maintaining and operating an aircraft
US20140309853A1 (en) * 2013-04-15 2014-10-16 Flextronics Ap, Llc Vehicle diagnostics and roadside assistance
US8958943B2 (en) * 2012-06-12 2015-02-17 Bosch Automotive Service Solutions Llc Method and apparatus for tracking, scheduling, and reminding about maintenance status
US9158834B2 (en) * 2013-01-21 2015-10-13 Snap-On Incorporated Methods and systems for mapping repair orders within a database
US11080734B2 (en) 2013-03-15 2021-08-03 Cdk Global, Llc Pricing system for identifying prices for vehicles offered by vehicle dealerships and other entities
US9212970B2 (en) * 2013-04-17 2015-12-15 Ford Global Technologies, Llc Laser ignition system based diagnostics
US9384453B2 (en) 2013-04-30 2016-07-05 Cummins Inc. Engine diagnostic system for high volume feedback processing
US20150142260A1 (en) * 2013-11-20 2015-05-21 Hyundai Motor Company Apparatus that supports starting-failure-handling and method of handling starting failure
US9805521B1 (en) 2013-12-03 2017-10-31 United Parcel Service Of America, Inc. Systems and methods for assessing turns made by a vehicle
US9824505B2 (en) 2014-02-25 2017-11-21 Ford Global Technologies, Llc Method for triggering a vehicle system monitor
DE102015206134B4 (en) * 2015-04-07 2023-01-05 Bayerische Motoren Werke Aktiengesellschaft Method for fault diagnosis for a motor vehicle and motor vehicle
US10309788B2 (en) 2015-05-11 2019-06-04 United Parcel Service Of America, Inc. Determining street segment headings
US9983919B2 (en) 2015-05-19 2018-05-29 The United States Of America, As Represented By The Secretary Of The Navy Dynamic error code, fault location, and test and troubleshooting user experience correlation/visualization systems and methods
US10216796B2 (en) 2015-07-29 2019-02-26 Snap-On Incorporated Systems and methods for predictive augmentation of vehicle service procedures
US9704141B2 (en) 2015-11-05 2017-07-11 Snap-On Incorporated Post-repair data comparison
US10692126B2 (en) 2015-11-17 2020-06-23 Nio Usa, Inc. Network-based system for selling and servicing cars
US10643158B2 (en) 2016-04-01 2020-05-05 Snap-On Incorporated Technician timer
US10853769B2 (en) * 2016-04-21 2020-12-01 Cdk Global Llc Scheduling an automobile service appointment in a dealer service bay based on diagnostic trouble codes and service bay attributes
US10867285B2 (en) 2016-04-21 2020-12-15 Cdk Global, Llc Automatic automobile repair service scheduling based on diagnostic trouble codes and service center attributes
US20180012197A1 (en) 2016-07-07 2018-01-11 NextEv USA, Inc. Battery exchange licensing program based on state of charge of battery pack
US10002473B1 (en) 2016-07-11 2018-06-19 State Farm Mutual Automobile Insurance Company Method and system for receiving and displaying user preferences corresponding to a vehicle event
US9928734B2 (en) 2016-08-02 2018-03-27 Nio Usa, Inc. Vehicle-to-pedestrian communication systems
US10031523B2 (en) 2016-11-07 2018-07-24 Nio Usa, Inc. Method and system for behavioral sharing in autonomous vehicles
US10410064B2 (en) 2016-11-11 2019-09-10 Nio Usa, Inc. System for tracking and identifying vehicles and pedestrians
US10708547B2 (en) 2016-11-11 2020-07-07 Nio Usa, Inc. Using vehicle sensor data to monitor environmental and geologic conditions
US10694357B2 (en) 2016-11-11 2020-06-23 Nio Usa, Inc. Using vehicle sensor data to monitor pedestrian health
US10515390B2 (en) 2016-11-21 2019-12-24 Nio Usa, Inc. Method and system for data optimization
US10249104B2 (en) 2016-12-06 2019-04-02 Nio Usa, Inc. Lease observation and event recording
US10074223B2 (en) 2017-01-13 2018-09-11 Nio Usa, Inc. Secured vehicle for user use only
US10471829B2 (en) 2017-01-16 2019-11-12 Nio Usa, Inc. Self-destruct zone and autonomous vehicle navigation
US10031521B1 (en) 2017-01-16 2018-07-24 Nio Usa, Inc. Method and system for using weather information in operation of autonomous vehicles
US9984572B1 (en) 2017-01-16 2018-05-29 Nio Usa, Inc. Method and system for sharing parking space availability among autonomous vehicles
US10464530B2 (en) 2017-01-17 2019-11-05 Nio Usa, Inc. Voice biometric pre-purchase enrollment for autonomous vehicles
US10286915B2 (en) 2017-01-17 2019-05-14 Nio Usa, Inc. Machine learning for personalized driving
EP3574481A4 (en) * 2017-01-24 2020-10-28 Tweddle Group, Inc. Method and system of vehicle diagnostics
US10897469B2 (en) 2017-02-02 2021-01-19 Nio Usa, Inc. System and method for firewalls between vehicle networks
US10733548B2 (en) 2017-06-16 2020-08-04 Snap-On Incorporated Technician assignment interface
US10234302B2 (en) 2017-06-27 2019-03-19 Nio Usa, Inc. Adaptive route and motion planning based on learned external and internal vehicle environment
US10710633B2 (en) 2017-07-14 2020-07-14 Nio Usa, Inc. Control of complex parking maneuvers and autonomous fuel replenishment of driverless vehicles
US10369974B2 (en) 2017-07-14 2019-08-06 Nio Usa, Inc. Control and coordination of driverless fuel replenishment for autonomous vehicles
US20190019356A1 (en) * 2017-07-14 2019-01-17 Launch Tech Co., Ltd. Vehicle diagnostic method, terminal device and computer readable storage medium
US10837790B2 (en) 2017-08-01 2020-11-17 Nio Usa, Inc. Productive and accident-free driving modes for a vehicle
US10635109B2 (en) 2017-10-17 2020-04-28 Nio Usa, Inc. Vehicle path-planner monitor and controller
US10606274B2 (en) 2017-10-30 2020-03-31 Nio Usa, Inc. Visual place recognition based self-localization for autonomous vehicles
US10935978B2 (en) 2017-10-30 2021-03-02 Nio Usa, Inc. Vehicle self-localization using particle filters and visual odometry
US10717412B2 (en) 2017-11-13 2020-07-21 Nio Usa, Inc. System and method for controlling a vehicle using secondary access methods
US11501351B2 (en) 2018-03-21 2022-11-15 Cdk Global, Llc Servers, systems, and methods for single sign-on of an automotive commerce exchange
US11190608B2 (en) 2018-03-21 2021-11-30 Cdk Global Llc Systems and methods for an automotive commerce exchange
US11315369B2 (en) 2018-03-23 2022-04-26 The Boeing Company Blockchain configuration history for vehicle maintenance, modification, and activity tracking
US10369966B1 (en) 2018-05-23 2019-08-06 Nio Usa, Inc. Controlling access to a vehicle using wireless access devices
US20200090430A1 (en) * 2018-09-17 2020-03-19 Westinghouse Air Brake Technologies Corporation Diagnostic System for a Transit Vehicle
US10562541B1 (en) * 2018-11-15 2020-02-18 GM Global Technology Operations LLC Contextual autonomous vehicle support through speech interaction
US11151512B2 (en) * 2018-12-14 2021-10-19 The Boeing Company Interlocking blockchains for aircraft part history and current aircraft configuration
US11574510B2 (en) 2020-03-30 2023-02-07 Innova Electronics Corporation Multi-functional automotive diagnostic tablet with interchangeable function-specific cartridges
US11651628B2 (en) 2020-04-20 2023-05-16 Innova Electronics Corporation Router for vehicle diagnostic system
US11080105B1 (en) 2020-11-18 2021-08-03 Cdk Global, Llc Systems, methods, and apparatuses for routing API calls
US11514021B2 (en) 2021-01-22 2022-11-29 Cdk Global, Llc Systems, methods, and apparatuses for scanning a legacy database
US11803535B2 (en) 2021-05-24 2023-10-31 Cdk Global, Llc Systems, methods, and apparatuses for simultaneously running parallel databases

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5442553A (en) * 1992-11-16 1995-08-15 Motorola Wireless motor vehicle diagnostic and software upgrade system
WO1996027171A1 (en) * 1995-02-27 1996-09-06 United Parcel Service Of America, Inc. Method and system for coordinating maintenance activities for a plurality of motor vehicles
WO2001071306A1 (en) * 2000-03-18 2001-09-27 Global Engineering And Technology Vehicle diagnostic system and method using mobile telecommunication system
US20030083794A1 (en) * 2001-10-27 2003-05-01 Juergen Halm System and method for diagnosing aircraft components for maintenance purposes
US20040210360A1 (en) * 2003-04-21 2004-10-21 International Business Machines Corporation On-board automotive vehicle control system for tracking vehicle operational data and maintenance and repair data, entered through reading visual code representing such maintenance and repair data
US6927682B1 (en) * 2002-12-21 2005-08-09 Jeff Touhey Digital vehicle service indicator
FR2865994A1 (en) * 2004-02-10 2005-08-12 J C Decaux Bicycle for urban journey, has CPU detecting whether fault appears in primary or secondary circuits, when bicycle is in movement and generating characteristic signal of detected fault to inform existence of fault to maintenance service

Family Cites Families (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4404639A (en) * 1980-12-02 1983-09-13 Chevron Research Company Automotive diagnostic system
US5111402A (en) * 1990-01-19 1992-05-05 Boeing Company Integrated aircraft test system
GB2249398B (en) * 1990-09-08 1995-04-19 Genrad Ltd Fault identification system
US5798647A (en) * 1996-05-06 1998-08-25 Chrysler Corporation Diagnostic test controller apparatus
JPH10253505A (en) * 1997-03-10 1998-09-25 Honda Motor Co Ltd Vehicle diagnosing method and device therefor
US6512968B1 (en) * 1997-05-16 2003-01-28 Snap-On Technologies, Inc. Computerized automotive service system
US6285932B1 (en) * 1997-05-16 2001-09-04 Snap-On Technologies, Inc. Computerized automotive service system
US5961561A (en) * 1997-08-14 1999-10-05 Invacare Corporation Method and apparatus for remote maintenance, troubleshooting, and repair of a motorized wheelchair
US6141608A (en) * 1997-10-28 2000-10-31 Snap-On Tools Company System for dynamic diagnosis of apparatus operating conditions
DE19921845A1 (en) * 1999-05-11 2000-11-23 Bosch Gmbh Robert Diagnostic test device for motor vehicles with programmable control units
US6330499B1 (en) * 1999-07-21 2001-12-11 International Business Machines Corporation System and method for vehicle diagnostics and health monitoring
US6993421B2 (en) * 1999-07-30 2006-01-31 Oshkosh Truck Corporation Equipment service vehicle with network-assisted vehicle service and repair
US6263265B1 (en) * 1999-10-01 2001-07-17 General Electric Company Web information vault
US6959235B1 (en) * 1999-10-28 2005-10-25 General Electric Company Diagnosis and repair system and method
JP2001154725A (en) * 1999-11-30 2001-06-08 Mitsubishi Motors Corp Method and device for diagnosing fault of vehicle, and computer readable recording medium recorded with fault diagnostic program
US6366199B1 (en) * 2000-02-04 2002-04-02 General Electric Company Method and apparatus for measuring and accumulating critical automobile warranty statistical data
US6370454B1 (en) * 2000-02-25 2002-04-09 Edwin S. Moore Iii Apparatus and method for monitoring and maintaining mechanized equipment
US6718425B1 (en) * 2000-05-31 2004-04-06 Cummins Engine Company, Inc. Handheld computer based system for collection, display and analysis of engine/vehicle data
US20020007237A1 (en) * 2000-06-14 2002-01-17 Phung Tam A. Method and system for the diagnosis of vehicles
US6308120B1 (en) * 2000-06-29 2001-10-23 U-Haul International, Inc. Vehicle service status tracking system and method
US20020016655A1 (en) * 2000-08-01 2002-02-07 Joao Raymond Anthony Apparatus and method for processing and/or for providing vehicle information and/or vehicle maintenance information
DE10043358A1 (en) * 2000-09-02 2002-03-14 Beissbarth Gmbh Method and device for program-controlled wheel alignment
US6370455B1 (en) * 2000-09-05 2002-04-09 Hunter Engineering Company Method and apparatus for networked wheel alignment communications and service
US20020077781A1 (en) * 2000-10-17 2002-06-20 Spx Corporation Data monitoring and display method and apparatus
JP4816992B2 (en) * 2001-01-31 2011-11-16 マツダ株式会社 Vehicle remote failure diagnosis server, vehicle remote failure diagnosis method, remote failure diagnosis program, and in-vehicle remote failure diagnosis device
JP2002228552A (en) * 2001-01-31 2002-08-14 Mazda Motor Corp Remote failure diagnostic server of vehicle, remote failure diagnostic method of vehicle, remote failure diagnostic program, on-vehicle remote failure diagnostic system and remote failure diagnostic system of vehicle
US6732028B2 (en) * 2001-02-15 2004-05-04 Joe Auto, Inc. Network based automotive service monitoring system
JP2002244724A (en) * 2001-02-20 2002-08-30 Honda Motor Co Ltd Remote monitoring device for machine and management method therefor
US6611740B2 (en) * 2001-03-14 2003-08-26 Networkcar Internet-based vehicle-diagnostic system
CN1266463C (en) * 2001-03-20 2006-07-26 斯耐普昂技术公司 Diagnostic director
US6879894B1 (en) * 2001-04-30 2005-04-12 Reynolds & Reynolds Holdings, Inc. Internet-based emissions test for vehicles
US6807469B2 (en) * 2001-06-15 2004-10-19 Carcheckup, Llc Auto diagnostic method and device
DE10138833A1 (en) * 2001-08-14 2003-02-27 Daimler Chrysler Ag Device and method for remote diagnostics of vehicles
US7130769B1 (en) * 2002-01-30 2006-10-31 Advanced Micro Devices, Inc. Method of dynamically designing a preventative maintenance schedule based upon sensor data, and system for accomplishing same
US20030236601A1 (en) * 2002-03-18 2003-12-25 Club Car, Inc. Control and diagnostic system for vehicles
US7073714B2 (en) * 2002-04-11 2006-07-11 Spx Corporation Code reader display
US20040044452A1 (en) * 2002-08-29 2004-03-04 Lester Electrical Of Nebraska, Inc. Vehicle monitoring system
US7136728B2 (en) * 2003-04-21 2006-11-14 Hunter Engineering Company Computerized wheel alignment system with improved stability and serviceability
US20040215379A1 (en) * 2003-04-22 2004-10-28 Vericom Compters Inc. Vehicle performance analyzer
US7209860B2 (en) 2003-07-07 2007-04-24 Snap-On Incorporated Distributed expert diagnostic service and system
CA2531602A1 (en) * 2003-07-09 2005-01-27 U.S. Environmental Protection Agency Vehicle on-board reporting system for state emissions test
US20060136104A1 (en) * 2004-12-22 2006-06-22 Snap-On Incorporated Distributed diagnostic system
US7516000B2 (en) * 2004-12-28 2009-04-07 Snap-On Incorporated Test procedures using pictures
US7209815B2 (en) * 2004-12-28 2007-04-24 Snap-On Incorporated Test procedures using pictures
US7171929B2 (en) * 2005-02-02 2007-02-06 Ford Global Technologies, Llc Method to estimate variable valve performance degradation
US7577503B2 (en) * 2005-09-23 2009-08-18 Spx Corporation Vehicle diagnostic device with adaptive data retrieval and method
US7739007B2 (en) * 2006-03-29 2010-06-15 Snap-On Incorporated Vehicle diagnostic method and system with intelligent data collection
WO2008063818A2 (en) * 2006-10-25 2008-05-29 Idsc Holdings, Llc Automatic system and method for vehicle diagnostic data retrieval using multiple data sources

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5442553A (en) * 1992-11-16 1995-08-15 Motorola Wireless motor vehicle diagnostic and software upgrade system
WO1996027171A1 (en) * 1995-02-27 1996-09-06 United Parcel Service Of America, Inc. Method and system for coordinating maintenance activities for a plurality of motor vehicles
WO2001071306A1 (en) * 2000-03-18 2001-09-27 Global Engineering And Technology Vehicle diagnostic system and method using mobile telecommunication system
US20030083794A1 (en) * 2001-10-27 2003-05-01 Juergen Halm System and method for diagnosing aircraft components for maintenance purposes
US6927682B1 (en) * 2002-12-21 2005-08-09 Jeff Touhey Digital vehicle service indicator
US20040210360A1 (en) * 2003-04-21 2004-10-21 International Business Machines Corporation On-board automotive vehicle control system for tracking vehicle operational data and maintenance and repair data, entered through reading visual code representing such maintenance and repair data
FR2865994A1 (en) * 2004-02-10 2005-08-12 J C Decaux Bicycle for urban journey, has CPU detecting whether fault appears in primary or secondary circuits, when bicycle is in movement and generating characteristic signal of detected fault to inform existence of fault to maintenance service

Also Published As

Publication number Publication date
US7739007B2 (en) 2010-06-15
WO2007126549A3 (en) 2008-01-03
US20070233341A1 (en) 2007-10-04

Similar Documents

Publication Publication Date Title
US7739007B2 (en) Vehicle diagnostic method and system with intelligent data collection
US5313388A (en) Method and apparatus for diagnosing engine and/or vehicle system faults based on vehicle operating or drive symptoms
US8996235B2 (en) Repair assist system for vehicle servicing
EP2112492B1 (en) Test requirement list for diagnostic tests
US7987028B2 (en) Method and apparatus for reading and erasing diagnostic trouble codes from a vehicle
US20070250228A1 (en) Configurable method and system for vehicle fault alert
US20090216401A1 (en) Feedback loop on diagnostic procedure
CN106406273A (en) Method for determining the cause of failure in a vehicle
US20230063326A1 (en) Vehicle Health Record
US9858733B2 (en) Vehicle diagnostic data collecting apparatus, vehicle diagnostic data collecting method, vehicle diagnostic machine, and vehicle diagnosing method
US8041476B2 (en) Error message details for debug available to end user
US20090271066A1 (en) Diagnostic data mining
US6192302B1 (en) Motor vehicle diagnostic system and apparatus
CN100476666C (en) Device and method for on-board diagnosis based on a model
EP3767406A1 (en) Controller area network and connectivity health troubleshooting system
US6363304B1 (en) Personal data computer for vehicle monitoring
US20080291014A1 (en) System and method for remote diagnosis and repair of a plant malfunction with software agents
US20090216584A1 (en) Repair diagnostics based on replacement parts inventory
CN101986124A (en) Support for preemptive symptoms
CN114490161B (en) Fault diagnosis method and device, vehicle and storage medium
US20230252829A1 (en) Method and diagnostic device for performing vehicle diagnostics
CN115016428A (en) Three-dimensional multi-stage diagnosis system and method applied to special vehicle
CN114564002B (en) Method and device for quickly diagnosing lost packet and computer equipment
JP4284962B2 (en) Electrical component inspection method and apparatus
CN111352646B (en) MPU software upgrading method and upgrading system thereof

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07752480

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 07752480

Country of ref document: EP

Kind code of ref document: A2