Skip to main content
ONE20 Help

Handling System Malfunctions

This article covers the types of system malfunctions and what they mean.

What to Do

If you are notified that your ELD solution is experiencing a system malfunction, do these things:

  • Click on the Details link in the System Issues screen for more detailed information
  • Keep paper logs until the issue is fixed
  • Record the malfunction and provide written notice to your fleet in under 24 hours
  • Refer to your Cab Card document for more information

What the Malfunctions Mean

Power System Malfunctions An ELD must set a power compliance malfunction if the power data diagnostics event 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.
Engine Synchronization System Malfunctions An ELD must set an engine synchronization compliance malfunction if connectivity to any of the required data sources specified is lost for more than 30 minutes during a 24-hour period aggregated across all driver profiles, including the unidentified driver profile.
Timing System Malfunction An ELD must record a timing compliance malfunction when it can no longer meet the underlying compliance requirement.
GPS System Malfunction An ELD must monitor the elapsed time during periods when the ELD fails to acquire a valid position measurement within five miles of the CMV's movement. When this elapsed time exceeds a cumulative 60 minutes over a 24-hour period, the ELD must set and record a positioning compliance malfunction.
Data Recording System 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 cataloged remotely by the motor carrier.
Data Transfer System Malfunction An ELD must implement in-service monitoring functions to verify that the data transfer mechanisms 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 the driver. 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.