IP Library Granted Patent US 10,417,844
Granted Patent B2
US 10,417,844 · App. 15/462,552 · Granted Sep 17, 2019

Electronic logging device event generator

Inventors: James Allen Ambrose (McMinnville, OR); Jason Philip Goodrich (Fort Collins, CO)
Assignee: J. J. KELLER & ASSOCIATES, INC.
G07C5/085G07C5/008G07C5/0808
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,417,844
App. No.
15/462,552
Granted
Sep 17, 2019
Kind
B2
Abstract

A driver logging device events generator. In example, the events generator includes an input port configured to receive telemetric data generated by a vehicle control module and sent from a vehicle diagnostic port; a positioning information source; and an electronic processor coupled to the input port and the positioning information source. The electronic processor is configured to receive telemetric data, location information, and timing data; process the telemetric data to extract a subset of data points; receive driver input from a mobile device; determine at least one event value based on the driver input, the location information, and the timing data; generate a logging device event from a pre-determined set of events based on the at least one event value, the event including an event type and an event code based on the driver input and the subset of data points; and send the event to the mobile device.

Claims (33)

1. A driver logging device events generator comprising:

an input port configured to receive telemetric data generated by a vehicle control module and sent from a vehicle diagnostic port;

a positioning information source;

an electronic processor coupled to the input port and the positioning information source and configured to

receive telemetric data, location information, and timing-related information;

process the telemetric data to extract a subset of data points;

receive driver input from a mobile device, the driver input including a driver duty status change;

determine at least one event value based on the driver input, the location information, and the timing-related information;

generate at least one of a logging device event from a predetermined set of logging device events based on the at least one event value, the logging device event including an event type and an event code based on the driver input and the subset of data points, the at least one of the logging device event including a first logging device event being one selected from a group consisting of on-duty, off-duty, sleeper, and driving; and

send the at least one of the logging device event to the mobile device.

2. The driver logging device events generator as claimed in claim 1 , wherein the telemetric data includes vehicle speed, and wherein the electronic processor is configured to determine whether the speed is greater than or equal to a predetermined threshold, and to generate a second logging device event when the speed is greater than or equal to the predetermined threshold.

3. The driver logging device events generator as claimed in claim 2 , wherein the electronic processor is further configured to determine, when the speed is greater than or equal to the predetermined threshold, if a change in the driver duty status was provided within a predetermined time period.

4. The driver logging device events generator as claimed in claim 3 , wherein the electronic processor is configured to record the logging device event in a history container when a driver identifier is not provided.

5. The driver logging device events generator as claimed in claim 4 , wherein the driver input includes a driving category selected from the group consisting of personal use and yard use.

6. The driving logging device events generator as claimed in claim 5 , wherein the driver input includes a certification and submission of a daily log.

7. The driving logging device events generator as claimed in claim 6 , wherein the driver input includes one selected from the group consisting of a log-off command and log-in command and the driver identifier.

8. The driving logging device events generator as claimed in claim 7 , wherein the electronic processor is further configured to generate the at least one event value based on whether an engine of the vehicle control module is on or off when the driver input includes the log-off command.

9. The driving logging device events generator as claimed in claim 8 , wherein the electronic processor is further configured to indicate a warning when a malfunction of the driver logging device event generator is detected.

10. A method for generating a logging device event through an electronic processor of a driver logging device events generator, the method comprising:

receiving telemetric data, location information, and timing-related information;

processing the telemetric data to extract a subset of data points;

receiving driver input from a mobile device, the driver input including a driver duty status change;

determining at least one event value based on the driver input, the location information, and the timing-related information;

generating at least one of a logging device event from a pre-determined set of logging device events based on the at least one event value, the logging device event including an event type and an event code based on the driver input and the subset of data points, the at least one of the logging device event including a first logging device event being one selected from a group consisting of on-duty, off-duty, sleeper, and driving; and

sending the at least one of the logging device event to a mobile device.

11. The method as claimed in claim 10 wherein the telemetric data includes vehicle speed, and wherein the method further includes determining whether the speed is greater than or equal to a predetermined threshold, and generating the logging device event when the speed is greater than or equal to the predetermined threshold.

12. The method as claimed in claim 11 , wherein the method further includes determine, when the speed is greater than or equal to the predetermined threshold, if a change in the driver duty status was provided within a predetermined time period.

13. The method as claimed in claim 12 , wherein the method further includes recording the logging device event in a history container when a driver identifier is not provided.

14. The method as claimed in claim 13 , wherein the driver input includes a driving category selected from the group consisting of personal use and yard use.

15. The method as claimed in claim 14 , wherein the driver input includes a certification and a submission of a daily log.

16. The method as claimed in claim 15 , wherein the driver input includes one selected from the group consisting of a log-off command and log-in command and the driver identifier.

17. The method as claimed in claim 16 , wherein the method further includes generating the at least one event value based on whether an engine of the vehicle control module is on or off when the driver input includes the log-off command.

18. The method as claimed in claim 17 , wherein the method further includes indicating a warning when a malfunction of the driver logging device event generator is detected.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 31, 2017
From: AMBROSE, JAMES ALLEN; GOODRICH, JASON PHILIP
To: J. J. KELLER & ASSOCIATES, INC.
Reel/Frame 041810/0644 →
Continuity (1)
Related Publication 20180268623A1 · Sep 20, 2018
Cited By (1)
US 12,419,480