Vehicle diagnostic tool with copy protection and automatic identification of vehicle ECUs and fault display

• US 8,589,018 B2
• Filed: 02/09/2010
• Issued: 11/19/2013
• Est. Priority Date: 02/09/2009
• Status: Active Grant

• Current Assignee: IDSC Holdings LLC (Snap-On Incorporated)
• Original Assignee: IDSC Holdings LLC (Snap-On Incorporated)
• Inventors: Sarnacke, James G., Garibay, Paul, Laferle, Michael D., Morris, Dan O., Skladanowski, David F., Sinha, Venkateshwar, Shock, David Paul
• Primary Examiner(s): MANCHO, RONNIE M
• Application Number:
  US12/702,694
• Publication Number:
  US 20100205450A1
• Time in Patent Office: 1,379 Days
• Field of Search: 701/29, 701/33, 701/2, 701/31.5, 701/35, 701/1, 701/213, 701/29.1, 701/29.2, 701/33.2, 701/33.4, 709/249, 709/250, 710/62, 710/72, 370464-467, 707/100, 340/5.2, 340/5.23, 340/5.61, 340/568.2, 340/439, 713/185
• US Class Current: 701/29.2
• CPC Class Codes: B60R 25/00 Fittings or systems for preventing or indicating unauthorised use or theft of vehicles locks for vehicles E05B77/00-E05B85/00
• CPC Class Codes: G07C 5/0808 Diagnosing performance data testing of vehicles G01M17/00; testing of electrical installation on vehicles G01R31/005

Abstract

A diagnostic tool for a vehicle configured to automatically identify different communication protocols used by Electronic Control Units (ECUs) on-board the vehicle. The diagnostic tool includes a connector connectable to a data port of the vehicle; a data processor and a data storage device configured to store a list of different communication protocols. The data processor automatically initiates communications with the ECUs on-board the vehicle using a first communication protocol and if the data processor receives a response comporting to the first communication protocol, the data processor determines that at least one ECU on-board the vehicle is using the first communication protocol. Additionally, the data processor automatically initiates communications with the ECUs on-board the vehicle using a second communication protocol and if the data processor receives a response comporting to the second communication protocol, the data processor determines that at least one ECU on-board the vehicle is using the second communication protocol.

Claims

1. A diagnostic tool for a vehicle configured to automatically identify different types of Electronic Control Units (ECUs) on-board the vehicle and automatically launch software applications for interacting with the ECUs, the diagnostic tool comprising:

a connector connectable to a data port of the vehicle;

a data processor; and

a data storage device configured to store a list of installed software applications for interacting with respectively associated ECU types on-board the vehicle, wherein;

the data processor automatically initiates communications with the ECUs on-board the vehicle using a first communication protocol and if the data processor receives a response comporting to the first communication protocol, the data processor determines that a first ECU on-board the vehicle is using the first communication protocol, uses the first communication protocol to communicate with the first ECU and, based on the communication with the first ECU, automatically launches one of the installed software applications associated with the first ECU, and

the data processor automatically initiates communications with the ECUs on-board the vehicle using a second communication protocol and if the data processor receives a response comporting to the second communication protocol, the data processor determines that a second ECU on-board the vehicle is using the second communication protocol, uses the second communication protocol to communicate with the second ECU and, based on the communication with the second ECU, automatically launches one of the installed software applications associated with the second ECU;

wherein the installed software applications are different from the first and second communication protocols.

2. The diagnostic tool of claim 1, wherein:

the data processor generates a list identifying ECUs communicating with the first communication protocol and ECUs communicating with the second communication protocol.

3. The diagnostic tool of claim 1, wherein:

the data processor automatically initiates communications with the ECUs on-board the vehicle using a third communication protocol and if the data processor receives no response comporting to the third communication protocol, the data processor determines the vehicle does not include ECUs comporting to the third communication protocol.

4. The diagnostic tool of claim 1, wherein:

the data processor sequentially initiates communications with the ECUs on-board the vehicle using the first and second communication protocols.

5. The diagnostic tool of claim 1, wherein:

the data processor concurrently initiates communications with the ECUs on-board the vehicle using the first and second communication protocols.

6. The diagnostic tool of claim 1, wherein:

the list of software applications includes diagnostic applications associated with different vehicles serviced by the diagnostic tool.

7. The diagnostic tool of claim 1, wherein:

the vehicles include passenger vehicles, cargo vehicles, heavy duty vehicles, construction equipment agricultural equipment, industrial equipment, harvest equipment, or paving equipment.

8. The diagnostic tool of claim 1, wherein:

the ECUs include at least one of a powertrain control module (PCM), an engine control module (ECM), a transmission control module (TCM), an anti-locking brake system (ABS), and an air bag control module.

9. The diagnostic tool of claim 1, further comprising:

a connection driver configured to control coupling of the connector to the data port of the vehicle.

10. The diagnostic tool of claim 1, further comprising:

an input device configured to receive an input from the user.

11. The diagnostic tool of claim 1, wherein:

the input device is configured to receive user'"'"'s protocol preferences or types of vehicles serviced by the diagnostic tool.

12. The diagnostic tool of claim 1, wherein:

the communication protocols include at least one of CAN, J8150, ISO9141, J1708, J1939, or 160 Baud.

13. The diagnostic tool of claim 1, wherein:

the data processor is further configured to use the list of software applications stored at the storage device to automatically identify a software application associated with the first ECU and a software application associated with the second ECU.

14. The diagnostic tool of claim 1, wherein:

the software applications are usable to transfer and process information to or from the ECUs on-board the vehicle.

15. The diagnostic tool of claim 1, wherein:

the software applications are usable to retrieve error codes from the ECUs on-board the vehicle or to update calibrations of the ECUs on-board the vehicle.

16. The diagnostic tool of claim 1, wherein:

the diagnostic tool enables the user to manually select a software application for identified ECUs on-board the vehicle.

17. The diagnostic tool of claim 1, wherein:

the software applications include at least one of OEM applications and industry standard applications.

18. The diagnostic tool of claim 1, wherein:

the software applications comprise diagnostic applications, and include evaluation software applications which are subject to a limited number of usages.

19. The diagnostic tool of claim 18, wherein:

the diagnostic tool solicits from the user an activation key to unlock software applications that have exceeded their limited number of usages.

20. The diagnostic tool of claim 19, wherein:

the data processor receives the activation key from the user for unlocking a particular software application, and

the data processor verifies the received activation key to ensure that it corresponds to the particular software application and the diagnostic tool.

21. A method for activating a software application on a diagnostic tool, the method comprising:

storing software applications installed on the diagnostic tool, wherein the software applications are for interacting with respectively associated ECU types on-board a vehicle;

initiating communications with ECUs on-board the vehicle using a first communication protocol and if a response comporting to the first communication protocol is received, determining that a first ECU on-board the vehicle is using the first communication protocol, using the first communication protocol to communicate with the first ECU and, based on the communication with the first ECU, automatically launching one of the installed software applications associated with the first ECU, and

initiating communications with the ECUs on-board the vehicle using a second communication protocol and if a response comporting to the second communication protocol is received, determining that a second ECU on-board the vehicle is using the second communication protocol, using the second communication protocol to communicate with the second ECU and, based on the communication with the second ECU, automatically launching one of the installed software applications associated with the second ECU;

wherein the installed software applications are different from the first and second communications protocols;

receiving, from a user, a first key and a serial number associated with the diagnostic tool;

determining whether the first key corresponds to the serial number associated with the diagnostic tool;

upon determining that the first key corresponds to the serial number associated with the diagnostic tool, registering the diagnostic tool;

receiving, from the user, a request for activating one of the software applications stored on the diagnostic tool;

in response to the request, requesting from the user a second key associated with the software application;

receiving, from the user, the second key associated with the software application;

determining whether the second key is valid; and

upon determining that the second key is valid, providing an activation key to the user for activating the software application on the diagnostic tool.

22. The method of claim 21, wherein:

the software application includes a software application that is in evaluation mode and expired.

23. The method of claim 21, wherein:

determining whether the second key is valid includes determining whether the second key does not belong to another software application.

24. The method of claim 21, wherein:

determining whether the second key is valid includes determining whether the second key has not been used to activate the software application in another diagnostic tool.