Lytx, Inc.

Drivecam, Inc.

Craig Denson

A system for drainage avoidance includes an interface and a processor. The interface is configured to receive an indication to power on. The processor is configured to query a wake up voltage threshold, perform a boot sequence, determine whether the boot sequence completed successfully, and in the event the boot sequence completed successfully, provide a reset indication to reset the wake up voltage threshold.

Vehicle battery drainage avoidance

A system for drainage avoidance includes an interface and a processor. The interface is configured to receive an indication to power on. A wake up voltage is increased after a power on signal is received. The processor is configured to perform a boot sequence, determine whether the boot sequence completed successfully, and in the event the boot sequence completed successfully, provide a reset indication to reset the wake up voltage.

A system for avoidance records comprises an interface and a processor. An interface is configured to receive an abbreviated record associated with a non-event profile identifier. A processor is configured to determine a counter value associated with the non-event profile identifier and, in the event that the counter value is greater than a predetermined threshold, create and store an avoidance record.

System and method for identifying non-event profiles

A system for identifying non-events comprising an event capture device and one or more processors in communication with the event capture device. The event capture device is associated with a vehicle that captures driving event data. The one or more processors is configured to receive the captured driving event data; classify the captured driving event data as a non-event or driving event by comparing the captured driving event data to a non-event profile; in the event that the captured driving event data is classified as a non-event, store an abbreviated record of the captured driving event data.

Valid driving events and non-events are identified, and detailed information is stored for valid events. Valid events are those captured driving events that are essential to testing of a driver's risky behavior. Remaining captured events which are not identified as involving risky behavior are non-events. At least one event capture device captures location, trigger force, images, and other information that collectively comprise an event. An event detector compares the captured event data to previously created non-event profiles and determines whether the captured event is a non-event. An abbreviated record is created for each identified non-event. For valid driving events, detailed driving event records are created. The records are stored at an evaluation server and are accessible to an analysis station for scoring and review.

Growing community of inventors

San Diego, CA, United States of America

Craig Denson