Before restarting or resetting, capture the exact warning, diagnostic/malfunction code, timestamp, driver, vehicle, app/device versions, and whether HOS recording and display/transfer still work. Then follow the exact provider procedure and preserve the support ticket and result.
Connectivity decision tree
- Capture exact warning/code, time, driver, truck, device/app/OS versions, and whether HOS recording and display/transfer still work.
- If phone-to-device is lost, check pairing ownership, permissions, shared-cab conflicts, power, and the documented reconnect path.
- If cellular service is lost but vehicle connection remains, verify local recording and later synchronization without duplicate/missing events.
- If positioning is lost, preserve the diagnostic and compare event/location behavior; do not relabel duty status to fix a pin.
- Follow the carrier’s reporting and repair procedure for ELD malfunctions. A malfunction can require action even while HOS recording remains accurate; FMCSA excepts an event from additional reporting when it does not affect HOS and the ELD clears it itself. Use the required backup records when accurate recording or presentation is hindered.
- Close only after a controlled repeat test and retained support result.
What to check
| Check | How to verify |
|---|---|
| 1. Record the connection problem, time, and affected component | Keep the exact warning, first occurrence, timestamps, vehicle, driver, device/app versions, screenshots, and affected ELD functions. |
| 2. Check vehicle power, the cable, and engine-data stability | Record connector/cable condition, stable power, device serial, VIN/miles/engine-hours values, movement event, expected result, and defect. |
| 3. Check device permissions, pairing, and background operation | Save phone/tablet, OS/app versions, permissions, pairing owner, background and power settings, reconnect result, and screenshots. |
| 4. Separate cellular, GPS, Bluetooth, and offline recording problems | Retain controlled layer-by-layer tests with signal state, GPS result, pairing state, queued events, timestamps, and observed difference. |
| 5. Reconcile records after recovery and repeat the failure test | Compare original, queued, and recovered events for gaps, duplicates, order, edits and certification; keep root cause, support case, correction, and retest. |
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.