A data diagnostic event signals a monitored data inconsistency; a malfunction is a defined failure that can prevent the ELD from meeting a technical requirement. The icon alone is not enough—drivers and carriers should open the detail, follow the documented procedure, and preserve the event record.
What this means for your fleet
Give drivers a two-path response card: capture the code and context for either event, then follow the stricter malfunction workflow when the device indicates a malfunction or cannot produce a compliant record.
Driver and carrier response
A data diagnostic event flags a monitored inconsistency and normally follows the carrier’s and provider’s resolution procedure. A malfunction is a defined failure the carrier must correct.
When a malfunction prevents accurate HOS recording or presentation, the driver must notify the carrier in writing within 24 hours. Reconstruct the current 24-hour period and previous seven consecutive days when they are not retrievable, then use a permitted manual record until service is restored. The carrier normally has eight days to repair, replace, or service the ELD.
What to check
Use these checks before changing a log, policy, device, integration, or buying decision.
| Check | How to verify |
|---|---|
| 1. Open the event details | Capture the exact icon, event detail, code, date, time, vehicle, driver, device/app version, and affected functions. |
| 2. Record code time and vehicle | Keep the original event record and a timeline showing when the code appeared, who was notified, and what the vehicle was doing. |
| 3. Check whether required functions still work | Test required recording, display, transfer, location, engine synchronization, and account functions; record each result. |
| 4. Notify the carrier under policy | Preserve the driver's notice, carrier acknowledgement, policy deadline, assigned owner, and escalation outcome. |
| 5. Follow reconstruction and repair steps when required | Keep reconstructed records, repair ticket, repair date, supporting documents, cleared-event evidence, and repeat test. |
Common failure modes
- Ignoring a diagnostic until inspection.
- Calling every warning a malfunction.
- Rebooting before capturing evidence.
Limits and exceptions
This guide does not decide a fact-specific legal exception, certify a record, or guarantee a compliance, safety, cost, or audit outcome. Keep the original ELD record and any edit history. Use the current official rule for applicability and the exact installed-device manual for screen-by-screen actions.
Sources, review date, and limits
Reviewed August 10, 2026. Each source supports only the point described beside it. Rules and product details can change; recheck dynamic facts before changing a fleet workflow or signing a contract.
- ELD malfunction and data-diagnostic responsibilities — Federal Motor Carrier Safety Administration.
- Official carrier and driver implementation resources, compliant-device selection, transfer, training, and operating guidance — Federal Motor Carrier Safety Administration.
- Current first-party product, plan, feature, and support representations; dynamic facts require release-date recheck — Factor ELD.
Review the exact operation
Bring the driver, vehicle, trip, jurisdiction, current official rule, and original ELD record for a qualified determination. Factor ELD can demonstrate its current product; rule applicability remains a fleet compliance decision.