Drive ELD

Electronic Logging DeviceDrive ELD LLC Drive ELD
Model Numberdriveeld_2017_1.0
ELD ID Number100DE1
Software Version4.5+

Model Information

Data Transfer MethodsTo transfer data using the DriveELD application. A user must log into the smartphone app on their phone or mobile device. Immediately upon logging in, a user can access the menu by pressing the button in the upper left corner. The menu icon is labeled, “menu” and is represented by a standard hamburger menu icon (i.e. three horizontal lines). A drawer will open, DOT Inspection is one of the options available in the menu. The user clicks DOT Inspection. The user has two options “View Logs on Phone” or “Transfer to FMCSA”. The user should select “Transfer to FMCSA” and click the “confirm” button in the upper right hand corner of the screen. On the next screen, the user selects either web services or email as their certified transfer method. Below these options is a text box where users can type in comments from the enforcement official, this is the Output File Comment. The user then selects “Send”. The user’s device communicates with the DriveELD server and the server sends the output file using the mechanism selected on the mobile device.
Malfunction Notes4.6.1.1. (P / power compliance malfunction): An ELD must set a power compliance malfunction if the power data diagnostics event described in paragraph 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. (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. (T / Timing Compliance Malfunction): The ELD must periodically cross-check its compliance with the requirement specified in section 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. (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 CMV’s 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. (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. (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
Certifying StatementThe product was tested using the FMCSA’s eldtestplanandprocedures07-18-201721-all-chapters.pdf as a template. Tests were performed using the app, Pacific Track hardware, a CMV simulator, and vehicles with OBDII and j1939 protocols.

Company Information

ManufacturerDrive ELD LLC
Contact Email[email protected]
Contact Phone Number866-623-7483
Address201 East Washington Street, Suite 1302, Iowa City, Iowa, 42240

Devices From Drive ELD LLC

Device ID
Drive ELD LLC Drive ELD 100DE1

Related ELDs

This site's data is aggregated programmatically and provided "as is" without any representations or warranties, express or implied. is not affiliated with the DOT, the NHTSA, or the US government in any way.

© 2022 Transportation.Report | Definitions