Skip to main content
diamond_k_logo.png
support_center_logo.png
J. J. Keller Support Center

ELD Malfunctions and Data Diagnostics

  1. Last updated
  2. Save as PDF

 

Per the FMCSA, "An ELD must monitor its compliance with the ELD technical requirements and detect malfunctions and data inconsistencies related to power, data synchronization, missing data, timing, positioning, data recording, data transfer, and unidentified driver records requirements. The ELD output will identify these data diagnostic and malfunction events and their status as either 'detected' or 'cleared'." See these FAQs from FMCSA regarding ELD malfunction occurrences: ELD Malfunctions and Data Diagnostics

 

When a diagnostic event or ELD malfunction occurs, it is displayed at the top of the mobile applications dashboard with yellow or red indicators; Yellow for a data diagnostic event, red for an ELD malfunction. Tap on the (i) icon to view its details.

clipboard_e4d917bddebb8b7098b1197bbc40aca50.png

ELD Malfunctions

The recommended actions for each malfunction do not guarantee that the malfunction will be cleared. While a recommended action may clear an ELD malfunction, the initial actions required by the FMCSA must still be completed. See the link above to understand what must occur when an ELD malfunction occurs.

Code

Description
P Power Compliance Malfunction - Occurs when an ELD is not powered and fully functional within one minute of the vehicle's engine receiving power and does not remain powered for as long as the vehicle's engine stays powered. These malfunctions occur when an ELD is not powered for an aggregated in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles.
  • Check all connections with the harness, ELD, and the vehicle.
  • If the malfunction does not resolve within 24 hours, have mechanic unplug the ELD for 3-5 minutes to reset it.
E Engine Synchronization Compliance - Occurs when an ELD loses ECM connectivity to any of the required data sources (engine power status, vehicle motion status, miles driven, and engine hours) and can no longer acquire updated values for the required ELD parameters within 5 seconds of the need. Additionally, this malfunction occurs when ECM connectivity to any of the required data sources (engine power status, vehicle motion status, miles driven, and engine hours) is lost for more than 30 minutes during a 24-hour period aggregated across all driver profiles.
  • Ensure that the ELD is configured correctly with the appropriate engine data bus. 
  • Release from the ELD within the mobile application and reconnect to the ELD.
  • Have mechanic check the ECM port for proper data being transmitted.
  • If the above to not resolve the malfunction, contact Client Services.
T Timing Compliance Malfunction - Occurs when the ELD can no longer meet the underlying compliance requirement to record Coordinated Universal Time (UTC), where ELD time must be synchronized with UTC, not to exceed an absolute deviation of 10 minutes at any time.
  • Check for a network connection (3G/4G/LTE/WiFi).
  • If there is a network connection, release from the ELD within the mobile application and reconnect to the ELD.
  • Log out and log back into the mobile application (logoff in an 'On Duty' status)
L Positioning Compliance Malfunction - Occurs when an ELD fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed.
  • Release and reconnect to the ELD to start the 'Reading History' process
  • If this malfunction does not clear after 24 hours, contact Client Services.
R Data Recording Compliance - Occurs when an ELD can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier.
  • Check memory on the mobile phone/tablet. If there is high usage, reboot the mobile device.
  • If memory is good, contact Client Services.
S Data Transfer Compliance - Occurs when the operation of the data transfer mechanism is not confirmed.  The data transfer mechanism is checked at least once every 7 days; if the data check fails, then  the data transfer mechanism begins being checked every 24 hours hours.  If 3 consecutive data checks fail, this malfunction is triggered.
  • Check the network connect (3G/4G/LTE/WiFi).  If they have a poor connection, inform the user to let us know if this malfunction persists when they are in a good area for network connection.
O Other ELD Detected
  • Contact Client Services

Data Diagnostics

When a data diagnostic event occurs, there isn't anything that the driver or company need to do at that point.  They are best described as a warning that a malfunction may occur and is best practice to monitor. How to handle the malfunctions are covered in the prior section.

 

Code

Description
1 Power - Indicates that the ELD may not have complied with the power requirements.
2 Engine Synchronization - Occurs when connectivity to required data sources is lost and the ELD can no longer acquire undated values for the ELD parameters required for records within 5 seconds of the need.
3 Missing Required Data Elements - Occurs when the ELD event record information is deficient in relation to the required data elements for each event type. Details about ELD event types can be found here.
4 Data Transfer - Occurs when the ELD fails to confirm proper in-service operation of the data transfer mechanism (this check is performed at least once every 7 days).
5 Unidentified Driving Records - Occurs when more than 30 minutes of driving in a 24-hour period show the 'unidentified driver' on ELD events. This event triggers an indicator that is then turned on for all drivers connecting to that ELD for the current 24-hour period and the following 7 days.
6 Other - ELD provider-specific data diagnostic values to communicate the ELD's malfunction or non-compliant state to the operator

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    This page has no tags.