SYSTEM AND METHOD FOR TRANSFERRING DIAGNOSTIC COMMANDS TO A VEHICLE

• US 20180151003A1
• Filed: 05/16/2016
• Published: 05/31/2018
• Est. Priority Date: 05/19/2015
• Status: Active Grant

• Current Assignee: HEX Microsystems (Pty) Ltd.
• Original Assignee: HEX Microsystems (Pty) Ltd.
• Inventors: GROBLER, Jacobus, BADENHORST, Petrus Johannes
• Granted Patent: US 10,621,797 B2
• Time in Patent Office: Days
• CPC Class Codes: G05B 23/0216 Human interface functionality, e.g. monitoring system providing help to the user in the selection of tests or in its configuration
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 16/90335 Query processing
• CPC Class Codes: G07C 2205/02 using a vehicle scan tool
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G07C 5/08 Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
• CPC Class Codes: H04W 4/44 for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]

Abstract

Systems and methods for transferring diagnostic commands to an on-board diagnostics (OBD) system of a vehicle are provided. A diagnostic interface device has a dedicated connection to a vehicle OBD system, and is in data communication with a diagnostic server over an open network. An instruction indicator is transmitted from the diagnostic interface device to the diagnostic server, and the diagnostic server transmits several instructions to be provided to the OBD system to execute the instruction to the diagnostic interface device. The instructions are provided in a batch which includes timing parameters specific to each instruction in the batch, so that the diagnostic interface device is capable of transferring each instruction in the batch to the vehicle OBD system in accordance with the timing parameters.

Claims

1. A method for transferring diagnostic commands to an on-board diagnostics (OBD) system of a vehicle, the method performed at a diagnostic server which is in data communication with a diagnostic interface device over an open network, the diagnostic interface device being connected to the vehicle OBD system by means of a dedicated connection, the method comprising:

receiving, from the diagnostic interface device, details of an electronic control unit (ECU) associated with the OBD system;

retrieving a list of functions executable by the ECU from a database,

transmitting, to the diagnostic interface device, the list of functions executable by the ECU;

receiving, from the diagnostic interface device, an indication of a function selected from the list of executable functions; and

transmitting a batch of instructions to the diagnostic interface device for performing the selected function, the batch of instructions including timing parameters specific to each instruction within the batch, so that the diagnostic interface device is capable of transferring each instruction in the batch to the vehicle OBD system over the dedicated connection in accordance with the timing parameters.

2. The method as claimed in claim 1, including a step of transmitting a further batch of instructions to the diagnostic interface device, the further batch of instructions including a configuration file instruction for facilitating readying of the timing parameters for the function.

3. The method as claimed in claim 1, including the steps of:

transmitting an initial batch of instructions to the diagnostic interface device, the initial batch of instructions including a request for ECU parameters;

receiving the requested ECU parameters; and

analyzing the ECU parameters to confirm that they allow for the function to be performed before transmitting the batch of instructions for performing the selected function.

4. The method as claimed in claim 1 wherein the batch of instructions includes an instruction to keep a communication session alive.

5. The method as claimed in claim 1, including the step of:

responsive to receiving a user termination action indicator, transmitting instructions to facilitate termination of the function to the diagnostic interface device.

6. The method as claimed in claim 1, including the steps of:

responsive to a predetermined waiting time expiring before a user termination action is performed, transmitting further instructions to the diagnostic interface device;

responsive to receiving an error code from the diagnostic interface device, transmitting an error message to the diagnostic interface device; and

responsive to receiving a function completed indicator, transmitting a function completed message to the diagnostic interface device.

7. The method as claimed in claim 1 wherein the timing parameters include one or more of:

time required to execute the function, timing limitations of a communication protocol of the OBD system, and inter-byte and inter-packet gaps.

8. The method as claimed in claim 1, wherein the batch of instructions includes a collection of commands to initiate a diagnostic session, to perform the specific function, to wait for a certain time unless a user termination action has been performed, and an instruction to repeat a subset of the current batch a predetermined number of times.

9. The method as claimed in claim 8, including the step of:

responsive to the subset of the batch having been performed the predetermined number of times, transmitting commands to facilitate termination of the function to the diagnostic interface device.

10. The method as claimed in claim 9, wherein the commands to facilitate termination of the function include instructions to terminate a current function, to read any error codes, and to stop the diagnostic session.

11. The method as claimed in claim 1, wherein the list of functions executable by the ECU is transmitted in a format suitable for display on a display associated with the diagnostic interface device;

and wherein batched instructions transmitted to the diagnostic interface device include detail to be displayed on the display.

12. (canceled)

13. A method for transferring diagnostic commands to an on-board diagnostics (OBD) system of a vehicle, the method performed at a diagnostic interface device connected to the OBD system via a dedicated connection and in data communication with a diagnostic server over an open network, the method including the steps of:

transmitting, to the diagnostic server, details of an ECU associated with the OBD system;

receiving, from the diagnostic server, a list of functions executable by the ECU;

receiving, from a user, an indication of a function in the list to be provided to the OBD;

transmitting, to the diagnostic server, the indication of the function;

receiving a batch of instructions from the diagnostic server for performing the selected function, the batch of instructions including timing parameters specific to each instruction within the batch; and

transferring each instruction in the batch to the OBD system in accordance with the timing parameters.

14. The method as claimed in claim 13, including the steps of:

receiving a configuration file instruction from the diagnostic server, the configuration file facilitating readying of timing parameters for the instruction; and

loading the configuration file into a memory.

15. The method as claimed in claim 13, including the steps of:

receiving, from the diagnostic server, an initial batch of instructions, the initial batch including a request for ECU parameters;

transmitting a request for ECU parameters to the OBD system;

receiving ECU parameters from the OBD system; and

transmitting the ECU parameters to the diagnostic server in a batched format.

16. The method as claimed in claims 13, including the steps of:

responsive to receiving a user termination action, transmitting a user termination indicator to the diagnostic server;

responsive to receiving an error code from the OBD system, transmitting the error code to the diagnostic server; and

responsive to recognizing that a function is completed, transmitting a function completed indicator to the diagnostic server.

17. The method as claimed in claim 13, including the step of:

responsive to receiving details to be displayed on a display associated with the diagnostic interface device as part of the batched instructions, sending the details to the display.

18. The method as claimed in claim 13, including the steps of:

in response to the OBD system responding to an instruction with a response that the instruction cannot be performed now, waiting a predetermined amount of time and repeating the specific instruction; and

in respond to the OBD system responding to an instruction with a response that the instruction has been received but the OBD system cannot respond now, waiting a predetermined amount of time for the response.

19. A diagnostic interface device for transferring diagnostic commands to an on-board diagnostics (OBD) system of a vehicle, comprising:

a physical interface for communicating with the OBD system over a dedicated network;

a communication interface for communicating with a diagnostic server over an open network; and

a processing module, wherein the processing module includes;

a list receiving component for receiving a list of functions from the diagnostic server;

a user input component for receiving, from a user, an indication of a function in the list to be provided to the OBD system;

a function transmitting component for transmitting an indication of the function to the server;

an instruction receiving component for receiving a batch of instructions from the diagnostic server, the batch of instructions including timing parameters specific to each instruction within the batch; and

an OBD system transferring component for transferring each instruction in the batch to the OBD system in accordance with the timing parameters.

20. (canceled)

21. (canceled)