User manual for "Drive ELD"

Below you will find the vendor provided user manual for the ELD product "Drive ELD".

For contact information and additional devices produced by the same vendor see their page Drive ELD LLC.

www.drive-eld.com

DriveELD

User Manual

01
04
11

Getting Started
Operation
Malfunctions

For more information or instructional videos, please visit
drive-eld.com/customer-support

Version History
Version
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.1.0

DriveELD

Date
11/21/2017
11/30/2017
12/11/2017
01/10/2018
01/24/2018
06/07/2018

866.623.7483
www.drive-eld.com
[email protected]

Version
1.2.0
1.2.1
1.2.2
1.3.0
1.3.1

Date
06/20/2018
10/28/2019
02/13/2020
11/18/2020
12/03/2020

Table of Contents
 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Connect the Hardware
 Locate your diagnostic port in
your vehicle while the engine is
turned off.
 Four common locations for
diagnostic ports are starred on
the right.

*
*
*

 Connect the DriveELD cable to
your diagnostic port.

*

 Attach the free end of the cable to the
DriveELD device.
 Position the device so that it does not impact
your driving abilities or restrict your movement.

Hardware Lights
Red LED State
Off

GPS power management engaged. GPS is turned off, GPS
backup clock is ON.

Blinking

GPS is in acquisition mode.

On

GPS signal is locked.

Green LED State
Off

Device is not plugged in.

Short Blink

Device is powered, but a vehicle is not detected.

Fast Blink

Vehicle activity detected, device is registering.

On

Device is registered on the vehicle.

Note: When the device is fully operational and both lights are
on together they will bleed into an orangey red color.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Getting Started
1

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

1. Download App
 Download the free DriveELD mobile app from the Apple App Store
or the Google Play Store.

2. Sign Up
 Select the Sign Up button.
 Enter your email address and a password to create an account.
 Note: The email address used for a Driver Account on the
mobile app cannot be the same as an email address used for
a Carrier Account on the fleet website.

3. Connect to a Carrier
 If a carrier has added you as a driver on the fleet website with the
same email address that you used to create your Driver Account
on the mobile app you will be able to see the carrier once you
create a Driver Account. Select your carrier and select confirm to
continue.
 If you do not see your carrier search for your carrier with the Find
Your Carrier button.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Getting Started
2

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Pair your ELD
 Make sure Bluetooth
is enabled on your
phone.
 Android devices
require Location to be
turned on for
Bluetooth to work.
 Select your device
from the device list
below and its
information will show
above when it has
connected.
 You may occasionally
be asked to update
your firmware on this
screen.
Todays Trip

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Getting Started
3

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Todays Trip

Daily Log
See details of the
current days log.

Clock
Breakdowns

Device Status

Duty Status

Connect and
update your
ELD device.

Change duty
status.

Cycle through
the displays by
selecting clocks.

Trip
Configuration
Add co-driver,
shipment & trailer
info, toggle on/off
split sleeper berth.*

*Note: The FMCSA requires a trailer number for all combination vehicles.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Operation
4

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

App Overview

Todays Trip

DOT Inspection

View daily info,
connect ELD,
configure trip, and
change duty status.

Send or display
logs to an officer.

Log History

Documents

Vehicle Inspection Driver Profile
& Settings
(DVIR)
View, edit, certify, or
add information to View, add, or sign Edit your driver
vehicle inspections. profile settings.
past logs.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Scan fuel receipts
for IFTA.

Operation
5

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Edit Past Log
 From the log history
screen select a day
and then an event
during that day.
 Change the start time,
duty status, and
location as needed.
 At the bottom add
notes. Notes will show
up as annotations in
the logs. All edits
require an annotation
 Note: you will be
asked to resign your
logs whenever an
edit is made.
Past Log

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Operation
6

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Unidentified
Driving Events
 On the Unidentified
Driving Events Page
you will be able to
review the event.
 When you are done
select the Finish
button at the top
and that event is
added to your Daily
Log.

Daily Log
Past Log

or

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Operation
7

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Sign Log
 A Sign Log button will
appear in the header
if a past log has not
been signed.
 Select this button to
sign the log.

Log History

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Operation
8

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

DOT Inspection Setup
After picking how
the officer wants to
see your logs select
confirm to continue.

Click the share button
in order to bring up
sharing options on
your device.

Transfer to
FMCSA

View Logs
on Phone

Transfer logs
through web
services or email.

Show or share
logs with an
officer.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Operation
9

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Navigator
If you have the Navigator tier subscription you will have all the
features from DriveELD as well as turn-by-turn navigation and
messaging.

Search for
destination.

App main menu.
Tap to change
duty status and
view current
daily log.

Connect to
ELD device.
Messaging.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Mute the
navigation voice.
Switch to night
mode or set as
automatic.
Switch between
2D and 3D view.
Re-center map.

Operation
10

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Malfunctions
 395.22 Motor carrier responsibilities - In general.
(h) In-vehicle information. A motor carrier must ensure that
its drivers possess onboard a commercial motor vehicle
an ELD information packet containing the following items:
... (3) An instruction sheet for the driver describing ELD malfunction
reporting requirements and record keeping procedures during ELD
malfunctions; ...

*
If you do not see that the lights are powered on while the truck is
running, please contact your carrier or call DriveELD Support
(866-623-7486 ext. 2).

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Malfunctions
11

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

The instructions below follow the guidelines
specified in rule  395.22 and  395.34.
For Drivers
 Contact DriveELD support at (866) 623-7483 or
[email protected]
 Note the malfunction of the ELD and provide written notice of the
malfunction to the motor carrier within 24 hours.
 Create a paper log for the current day and the last 7 days, unless
you already can access the last 7 days through the ELD.

For Carriers
 If a motor carrier receives or discovers information concerning
the malfunction of an ELD, the motor carrier must take actions to
correct the malfunction of the ELD within 8 days of discovery
of the condition or a drivers notification to the motor carrier,
whichever occurs first.
 If the ELD stops working as a result of the malfunction, then per
the warranty DriveELD will ship a new device when given notice of
the malfunction.
 A motor carrier seeking to extend the period of time permitted
for repair, replacement, or service of one or more ELDs shall
notify the FMCSA Division Administrator for the State of
the motor carriers principal place of business within 5 days after
a driver notifies the motor carrier under paragraph (a)(1) of the
ruling  395.34 section (d) 2.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Malfunctions
12

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Malfunctions Events
Requirement #

Event
Code

Event Name

Description

4.6.1.1

P

Power
Compliance
Malfunction

An ELD must set a power compliance malfunction
if the power data diagnostics event described in
paragraph 4.6.1.1(a) of this appendix indicates an
aggregated in-motion driving time understatement
of 30 minutes or more on the ELD over a 24-hour
period across all driver profiles, including the
unidentified driver profile.

4.6.1.2

E

Engine
Synchronization
Compliance
Malfunction

An ELD must set an engine synchronization
compliance malfunction if connectivity to any of
the required data sources specified in section 4.3.1
of this appendix is lost for more than 30 minutes
during a 24-hour period aggregated across all driver
profiles, including the unidentified driver profile.

4.6.1.3

T

Timing
Compliance
Malfunction

The ELD must periodically cross-check its
compliance with the requirement specified in
section 4.3.1.5 of this appendix with respect
to an accurate external UTC source and must
record a timing compliance malfunction when it
can no longer meet the underlying compliance
requirement.

4.6.1.4

L

Position
Compliance
Malfunction

ELD records requiring location information must
use the last valid position measurement and
include the latitude/longitude coordinates and
distance traveled, in miles, since the last valid
position measurement. An ELD must monitor
elapsed time during periods when the ELD fails to
acquire a valid position measurement within 5 miles
of the CMVs movement. When such elapsed time
exceeds a cumulative 60 minutes over a 24 hour
period, the ELD must set and record a positioning
compliance malfunction.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Malfunctions
13

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Malfunctions Events cont.
Requirement #

Event
Code

Event Name

Description

4.6.1.5

R

Data Recording
Compliance
Malfunction

An ELD must monitor its storage capacity and
integrity and must detect a data recording
compliance malfunction if it can no longer record
or retain required events or retrieve recorded logs
that are not otherwise catalogued remotely by the
motor carrier.

4.6.1.7

S

Data Transfer
Compliance
Malfunction

(a) An ELD must implement in-service monitoring
functions to verify that the data transfer
mechanism(s) described in section 4.9.1 of this
appendix are continuing to function properly. An
ELD must verify this functionality at least once
every 7 days. These monitoring functions may be
automatic or may involve manual steps for a driver.
(b) If the monitoring mechanism fails to confirm
proper in-service operation of the data transfer
mechanism(s), an ELD must record a data transfer
data diagnostic event and enter an unconfirmed
data transfer mode.
(c) After an ELD records a data transfer data
diagnostic event, the ELD must increase the
frequency of the monitoring function to check at
least once every 24-hour period. If the ELD stays
in the unconfirmed data transfer mode following
the next three consecutive monitoring checks,
the ELD must detect a data transfer compliance
malfunction.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Malfunctions
14

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Data Diagnostic Events
Requirement #

Event
Code

Event Name

Description

4.6.1.1

1

Power Data
Diagnostic
Event

An ELD must monitor data it receives from the
engine ECM or alternative sources as allowed
in sections 4.3.1.1-4.3.1.4 of this appendix, its
onboard sensors, and data record history to
identify instances when it may not have complied
with the power requirements specified in section
4.3.1.1, in which case, the ELD must record a power
data diagnostics event for the corresponding
driver(s), or under the unidentified driver profile
if no drivers were authenticated at the time of
detection.

4.6.1.2

2

Engine
Synchronization
Data Diagnostic
Event

An ELD required to establish a link to the engine
ECM as described in section 4.2 must monitor
its connectivity to the engine ECM and its ability
to retrieve the vehicle parameters described
under section 4.3.1 of this appendix and must
record an engine-synchronization data diagnostics
event when it no longer can acquire updated values
for the ELD parameters required for records within
5 seconds of the need.

4.6.1.4
(d)

3

Missing Data
Elements Data
Diagnostic
Event

If a new ELD event must be recorded at an instance
when the ELD had failed to acquire a valid position
measurement within the most recent elapsed
5 miles of driving, but the ELD has not yet set a
positioning compliance malfunction, the ELD must
record the character X in both the latitude and
longitude fields, unless location is entered manually
by the driver, in which case it must log the character
M instead. Under the circumstances listed in this
paragraph, if the ELD event is due to a change in
duty status for the driver, the ELD must prompt the
driver to enter location manually in accordance with
section 4.3.2.7 of this appendix. If the driver does
not enter the location information and the vehicle is
in motion, the ELD must record a missing required
data element data diagnostic event for the driver.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Malfunctions
15

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Data Diagnostic Events cont.
Requirement #

Event
Code

Event Name

Description

4.6.1.7

4

Data Transfer
Data Diagnostic
Event

If the monitoring mechanism fails to confirm
proper in-service operation of the data transfer
mechanism(s), an ELD must record a data transfer
data diagnostic event and enter an unconfirmed
data transfer mode.

4.6.1.6

5

Unidentified
Driver Data
Diagnostic
Event

(b) The ELD must provide a mechanism for the
driver to review and either acknowledge the
assignment of one or more of the unidentified
driver records attributable to the driver under
the authenticated driver's profile as described
in paragraph 4.3.2.8.2(b)(1) of this appendix or
indicate that these records are not attributable to
the driver. (c) If more than 30 minutes of driving
in a 24-hour period show unidentified driver
on the ELD, the ELD must detect and record an
unidentified driving records data diagnostic event
and the data diagnostic indicator must be turned
on for all drivers logged in to that ELD for the
current 24-hour period and the following 7 days.

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

Malfunctions
16

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

Visit our support page
If you would like more information on how to use the system, please
visit drive-eld.com/customer-support/

Give us a call
Call DriveELD Customer Support
(866) 623-7483 Ext. 2

Shoot us an email
[email protected]

DriveELD

866.623.7483
www.drive-eld.com
[email protected]

17

 2020, Drive ELD LLC, All Rights Reserved, v 1.3.1

DriveELD

866.623.7483
www.drive-eld.com
[email protected]


© ELD.report 2026

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.