Frequently Asked Questions
When does an electronic logging device (ELD) “missing required data elements data diagnostic event” occur?
When do electronic logging device (ELD) “data transfer data diagnostic events” and “data transfer compliance malfunctions” occur?
A “data transfer data diagnostic event” occurs when the operation of the data transfer mechanism(s) is not confirmed. A “data transfer compliance” malfunction occurs when the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks.
When does an electronic logging device (ELD) “unidentified driving records data diagnostic event” occur?
If an ELD malfunctions, a driver must:
- Note the malfunction of the ELD and provide written notice of the malfunction to the motor carrier within 24 hours;
- Reconstruct the record of duty status (RODS) for the current 24-hour period and the previous 7 consecutive days, and record the records of duty status on graph-grid paper logs that comply with 49 CFR 395.8, unless the driver already has the records or retrieves them from the ELD; and
- Continue to manually prepare RODS in accordance with 49 CFR 395.8 until the ELD is serviced and back in compliance.
If an ELD malfunctions, a motor carrier must:
- Correct, repair, replace, or service the malfunctioning ELD within eight days of discovering the condition or a driver’s notification to the motor carrier, whichever occurs first; and
- Require the driver to maintain paper record of duty status (RODS) until the ELD is back in service.
Yes. 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.” Typically, a driver can follow the ELD provider’s and the motor carrier’s recommendations to resolve the data inconsistencies that generate an ELD data diagnostic event, while a motor carrier must correct a malfunction.
When should a driver certify his or her record of duty status (RODS) on the electronic logging device (ELD) to avoid malfunction codes?
FMCSA recommends that drivers first certify their RODS before logging off the ELDs and then shutting down their CMVs’ engines. If drivers don’t follow this recommendation, malfunction codes may occur, such as indicating unaccounted odometer changes and suspicious driving activity.
When do electronic logging device (ELD) “power data diagnostic events” and “power compliance malfunctions” occur?
“Power data diagnostic events” occur 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. “Power compliance 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.
An ELD must display a single visual malfunction indicator on the ELD’s display or on a stand-alone indicator for all drivers using the ELD. The visual signal must be visible to the driver, be continuously communicated to the driver when the ELD is powered, and clearly illuminate an active malfunction. An ELD must also display a single visual data diagnostics indicator, apart from the malfunction indicator, for active data diagnostics events. The ELD may also provide an audible signal for the data diagnostics indicator.A malfunction is a situation in which an ELD is not working properly. A malfunction affects the integrity of the device and its compliance, and requires the motor carrier to repair, replace, or service the ELD.
An ELD must display a malfunction signal (or indicator) such as a light, symbol, or text on the ELD or on a stand-alone display. The malfunction signal must be visible to the driver and display function status whenever the ELD is powered on. It must also light up to draw attention to an active malfunction.
An ELD must also include a diagnostics indicator to display active diagnostic events. Data diagnostic events note data inconsistencies that a driver can typically resolve by following the motor carrier’s or ELD provider’s recommendations.
When do electronic logging device (ELD) “engine synchronization data diagnostic events” and “engine synchronization compliance malfunctions” occur?
“Engine synchronization data diagnostic events” occur 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 five seconds of the need. “Engine synchronization compliance malfunctions” occur 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.
A “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.