SYSTEM AND METHOD FOR REAL TIME WIRELESS ECU MONITORING AND REPROGRAMMING

• US 20190026962A1
• Filed: 07/30/2018
• Published: 01/24/2019
• Est. Priority Date: 08/05/2015
• Status: Active Grant

• Current Assignee: EZ Lynk SEZC
• Original Assignee: EZ Lynk SEZC
• Inventors: Gintz, Brad, Wood, Thomas, Savage, Frederick Hershel
• Granted Patent: US 10,614,640 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G07C 5/085 using electronic data carriers
• CPC Class Codes: G07C 5/12 in graphical form
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Disclosed are methods, systems, and apparatus for managing firmware, settings, and parameters of an automotive controller using a local device, a client device, and a system server. The local device is connected to the automotive controller and is wirelessly connected to the client device. The client device is connected to the system server. The client device receives engine data from the local device that receives the engine data from the automotive controller and the client device sends the engine data to the server system. Firmware, settings, and parameter updates are selected with the client device, sent to the local device, and then sent to the automotive controller.

Claims

1. A system for delivering information from a vehicle connected to a network, the network including a server, a customer client device, a local device, and a vehicle device, the system comprising:

a set of processors in the server, in the customer client device, in the local device and in the vehicle device;

a set of memories, each memory of the set of memories operably connected to at least one processor of the set of processors;

the set of memories including a set of instructions that, when executed causes the system to perform the steps of;

generating a first logged vehicle data request;

receiving, by the local device, the first logged vehicle data request;

filtering, by the local device, a first set of logged vehicle data based on the first logged vehicle data request to generate first filtered logged vehicle data; and

,

transmitting the first filtered logged vehicle data to the customer client device.

2. The system of claim 1, wherein the of instructions further causes the system to perform the steps of:

receiving the first filtered logged vehicle data; and

,

displaying the first filtered logged vehicle data.

3. The system of claim 2, wherein the step of displaying further comprises:

displaying the first filtered logged vehicle data in a scrolling mode.

4. The system of claim 1 wherein the network further comprises a technician client device and wherein the set of instructions further causes the system to perform the steps of:

generating one or more of a customer list, a vehicle list and a function list;

sending the one or more of the customer list, the vehicle list and the function list to the technician device;

selecting one or more of the customer list, the vehicle list and the function list;

sending a function request from one or more of the customer list, the vehicle list and the function list; and

,

authorizing the function request.

5. The system of claim 1 wherein the network further comprises a technician client device and wherein the set of instructions further causes the system to perform the steps of:

generating a second logged vehicle data request at the technician client device;

sending the second logged vehicle data request to the server;

authorizing the second logged vehicle data request;

sending the second logged vehicle data request to the customer client device;

sending the second logged vehicle data request to the local device;

generating a second set of filtered logged vehicle data related to the second logged vehicle data request;

sending the second set of filtered logged vehicle data to the customer client device;

sending the second set of filtered logged vehicle data to the server; and

,

sending the second set of filtered logged vehicle data to the technician client device.

6. The system of claim 5, wherein the set of instructions further causes the system to perform the steps of:

displaying the logged vehicle data.

7. The system of claim 1, wherein the set of instructions further causes the system to perform the steps of:

generating an active engine control unit (ECU) profile request;

transmitting the active ECU profile request to the server;

receiving, by the local device, an active ECU profile request;

generating, by the local device, a set of ECU profile instructions;

transmitting, by the local device, the set of ECU profile instructions to the vehicle device;

receiving, by the local device, the active ECU profile from the vehicle device;

transmitting the active ECU profile to the server;

receiving from the server the active ECU profile; and

,

displaying the active ECU profile.

8. The system of claim 1, wherein the set of instructions further causes the system to perform the steps of:

generating an available ECU profile request;

transmitting the available ECU profile request to the server;

receiving from the server and in response to the available ECU profile request, a set of available ECU profiles;

generating an updated ECU profile from one available ECU profiles from the set of available ECU profiles;

transmitting the updated ECU profile to the local device;

receiving, by the local device, an updated ECU profile; and

,

transmitting, by the local device, the updated ECU profile instructions to the vehicle device.

9. The system of claim 8, wherein the set of instructions further causes the system to perform the steps of:

displaying the updated ECU profile with at least one of a graph view and a chart view;

displaying the graph view with a number of dimensions based on a type of data selected;

displaying the chart view as a table based on the type of data selected; and

,

generating the updated ECU profile based on one or more adjustments made to data displayed in one or more of the graph view and the chart view.

10. The system of claim 1 wherein the set of instructions further causes the system to perform the steps of:

generating a start live vehicle data request;

transmitting the start live vehicle data request to the server;

receiving, by the local device, a start live vehicle data request;

transmitting, by the local device, a set of live vehicle data;

receiving the set of live vehicle data; and

,

displaying the set of live vehicle data.

11. The client device of claim 10, wherein the set of instructions further causes the system to perform the steps of:

generating a stop live vehicle data request;

transmitting the stop live vehicle data request to the server;

receiving a stop live vehicle data request; and

,

stopping the step of transmitting the set of live vehicle data.

12. The client device of claim 11, wherein the set of instructions further causes the system to perform the steps of:

displaying the set of live vehicle data in a scrolling mode.

30. The system of claim 1, wherein the first filtered logged vehicle data includes one or more of:

off duty time, sleeper berth time, driving time, on-duty not driving time, annotations, driver'"'"'s location description and modifications, comments, commercial motor vehicle power unit numbers, mileage records, trailer numbers, shipping document numbers, driver hours of service (HOS) records, and driver'"'"'s records of duty (RODS).

13. A system for communicating, over a network, between a server, an ECU, and a local device, the local device comprising:

a processor;

a memory operably connected to the processor;

a GSM module operably connected to the processor;

a first network connection to a mobile network established by the GSM module;

a second network connection to a vehicle network;

a third network connection to the ECU;

the memory including a set of instructions that, when executed by the processor, causes the local device to perform the steps of;

receiving vehicle data from the vehicle device over the third network connection;

generating logged vehicle data from the vehicle data;

receiving a logged vehicle data request over one of the first network connection and the second network connection;

generating a logged vehicle data response to the logged vehicle data request that includes a set of logged vehicle data; and

,

transmitting the logged vehicle data response using a one of the first network connection and the second network connection.

14. The system of claim 13 wherein the memory includes further instructions that cause the local device to perform the steps of:

receiving a start live vehicle data request over one of the first network connection and the second network connection; and

,

transmitting a set of live vehicle data over one of the first network connection and the second network connection.

15. The system of claim 14 wherein the memory includes further instructions that cause the local device to perform the steps of:

receiving a stop live vehicle data request over one of the first network connection and the second network connection; and

,

stopping transmission of the set of live vehicle data in response to the stop live vehicle data request.

16. The system of claim 14 wherein the memory includes further instructions that cause the local device to perform the steps of:

receiving an active ECU profile request over one of the first network connection and the second network connection; and

,

transmitting an active ECU profile over the third network connection.

17. The system of claim 14 wherein the memory includes further instructions that cause the local device to perform the steps of:

generating an active ECU profile alert from the active ECU profile;

transmitting the active ECU profile alert over one of the first network connection and the second network connection; and

,

receiving an updated ECU profile, in response to the active ECU profile alert over one of the first network connection and the second network connection.

18. A system for making adjustments to an ECU connected to a network, the network including a server, a client device, a local device, and a vehicle device, the system comprising:

a set of processors, in the server, in the client device, in the local device and in the vehicle device;

a set of memories, each memory of the set of memories connected to at least one processor of the set of processors;

the set of memories including a set of instructions that causes the system to perform the steps of;

sending a first message to the vehicle device;

receiving a response to the message within a time limit;

masking a set of response parameters upon receipt of the response;

retrieving a first configuration file and a set of PIDs from the vehicle device;

setting a power level associated with the vehicle device based on at least one of the configuration file and one or more PID of the set of PIDs.

19. The system of claim 18, wherein the set of instructions further causes the system to perform the steps of:

receiving a SOTF map from the client device;

reading the SOTF map; and

,

checking the vehicle data for one or more of a vehicle identifier, a part identifier, and a serial number identifier.

20. The system of claim 19, wherein the set of instructions further causes the system to perform the steps of:

receiving vehicle data from the client device; and

,

providing an error message when one or more of the vehicle identifier, the part identifier, and the serial number identifier is not in the vehicle data.

21. The system of claim 20, wherein the set of instructions further causes the system to perform the steps of:

checking at least one of an engine status, an ignition status, and a vehicle status; and

,

if the vehicle status is normal then parsing the PIDs.

22. The system of claim 21, wherein the set of instructions further causes the system to perform the steps of:

generating a second configuration file including a modified CRC and an unmodified CRC.

23. The system of claim 22, wherein the set of instructions further causes the system to perform the steps of:

checking for a previous failure;

performing a reflash recovery operation if a previous failure is indicated;

if the reflash recovery operation is successful then implementing a power level based on at least one of the configuration file and one or more PID of the set of PIDs.

24. The system of claim 23, wherein the system further comprises a technician client device, and wherein the set of instructions further causes the system to perform the steps of:

generating, at the customer client device, an authorization to share the logged vehicle data; and

,

sending the authorization to the local device.

25. The system of claim 24, wherein the set of instructions further causes the system to perform the step of:

sending the logged data response to the technician device.

26. The system of claim 25, wherein the system further comprises a third party server and wherein the set of instructions further causes the system to perform the step of:

sending the logged data response to the third party server.

27. The system of claim 26, wherein the set of instructions further causes the system to perform the steps of:

confirming the presence of a data set to determine that the set of logged vehicle data is one of certified or uncertified; and

,

sending a message based on the confirmation.

28. A system for third party proxy control of a vehicle controller comprising:

a network;

a server, having a first memory and a first processor, connected to the network;

a client device connected to the network;

a third party proxy device connected to the network;

a local device connected to the client device;

a vehicle controller connected to the local device;

the memory including a set of instructions that when executed by the processor cause the system to perform the steps of;

receiving, at the server, a proxy request from the third party proxy device;

identifying the client device;

generating a proxy request authorization;

generating a set of vehicle instructions based on the proxy request authorization;

sending the set of vehicle instructions to the local device;

sending the set of vehicle instructions to the vehicle controller; and

,

executing the set of vehicle instructions.

29. The system of claim 28, wherein the local device further comprises second memory and a second processor and wherein the second memory includes instructions that cause the second processor to:

format the set of vehicle instructions before sending the set of vehicle instructions to the vehicle controller.