Before restarting an ELD or app, capture the exact malfunction/diagnostic code, timestamp, driver, vehicle, and whether required HOS recording and display/transfer still work. Follow the installed device's manual and the carrier's policy. Use paper logs only when the malfunction hinders accurate HOS recording or presentation, and follow FMCSA's 24-hour driver notice and eight-day carrier repair rules.
Fast diagnostic branches
| Symptom | Preserve first | Next action |
|---|---|---|
| Malfunction or diagnostic indicator | Exact code, time, truck, driver, and affected functions | Follow the device instructions. Report a malfunction to the carrier in writing within 24 hours; correction is normally required within eight days of discovery or notice, whichever comes first. Recording can remain accurate and these duties still apply. FMCSA excepts an event from additional reporting when it does not affect HOS and the ELD clears it itself; any repair extension must follow the applicable procedure. |
| No vehicle data | VIN, cable/device serial, engine state, power/connection status | Check assignment and provider diagnostics before replacing or resetting |
| Wrong driver or unidentified driving | Original event, login, dispatch, maintenance, and yard activity | Review the event through the carrier’s assignment and correction procedure, preserving the original record |
| Transfer failure | Transfer method, routing code or comment, error message, and network status | Follow the officer’s instructions for the available display or printout, contact support, and record the result |
| Map or mileage anomaly | Event source, timestamp, units, position, odometer/engine hours | Separate optional map data from required ELD data and reproduce the issue |
What to check
| Check | How to verify |
|---|---|
| 1. Capture the exact warning code and operating context | Keep the exact icon and wording, code, date/time, vehicle, driver, device/app versions, screenshots, and affected functions. |
| 2. Identify whether the message concerns a diagnostic event, malfunction, HOS issue, or vendor-specific alert | Retain the authoritative classification source, category, facts compared, reviewer, uncertainty, and escalation route. |
| 3. Test every required function affected by the class | Record pass/fail for engine synchronization, position, recording, display, transfer, accounts, timestamps, and any class-specific function. |
| 4. Follow the installed-device procedure without altering originals | Save the manual version and steps, original HOS record, notices, reconstructed records if required, user actions, and audit history. |
| 5. Confirm the correction with support and repeat the test | Keep the support case or repair record, root cause, correction, cleared indicator, affected records, reviewer, repeat scenario, and final result. |
Before you act
Use this guide to plan your checks; it does not guarantee compliance, savings, safety, inspection results, or other operating outcomes. Keep original records and follow the current rules and the manual for your installed device.
Sources and review date
Reviewed August 10, 2026. Check the current rules, device registration, product instructions, and commercial terms before making a decision.
- Federal Motor Carrier Safety Administration — ELD malfunction and data-diagnostic responsibilities.
- Federal Motor Carrier Safety Administration — Official ELD technical FAQ covering engine synchronization, VIN, odometer, position, data transfer, events, and device behavior.
- Federal Motor Carrier Safety Administration — Roadside and safety-official ELD data-transfer methods.
Reproduce the issue on the installed setup
Bring the vehicle, device and app versions, timestamp, exact warning, affected functions, and result of the documented recovery steps.