By Michael Nielsen, Publisher | 15+ Years in Diesel Repair
Last Updated: October 2026
⏱ Estimated reading time: 15+ minutes
ELD troubleshooting starts with one question: is the electronic logging device (ELD) reporting a data diagnostic event, which the driver usually resolves by following the provider's steps, or a compliance malfunction, which triggers paper logs and an 8-day repair clock under 49 Code of Federal Regulations (CFR) 395.34?
A data diagnostic event flags a data inconsistency, such as a missing required data element or driving logged to an unidentified driver. A malfunction means the ELD can no longer meet a federal technical requirement, such as staying powered, staying connected to the engine, or holding time accurate to within 10 minutes of Coordinated Universal Time (UTC).
Heavy Duty Journal (HDJ) publisher Michael Nielsen and the HDJ editorial team built this guide from the ELD rule text, the technical specifications in Appendix A to Subpart B of Part 395, and the Federal Motor Carrier Safety Administration's (FMCSA) ELD pages as of October 2026. It also covers the revoked-device cutoff that passed on October 6, 2026, and it treats the owner-operator as both driver and motor carrier, because an independent operator carries both sets of duties.
Key Takeaways
- ✓Two faults, two responses. A data diagnostic event is usually cleared by following the ELD provider's and carrier's instructions, while a malfunction requires paper logs and a repair or replacement within 8 days.
- ✓The owner-operator holds both roles. The driver's written notice within 24 hours and the carrier's 8-day repair clock land on the same person, so a dated record of each is the proof that matters.
- ✓Paper logs mean a seven-day rebuild. Reconstruct the current 24-hour period and the previous 7 consecutive days unless the ELD can still produce them, and keep at least 8 days of blank graph-grids in the cab.
- ✓Roadside transfer failure falls back to the display. If electronic transfer fails, the officer reviews the ELD display or a printout, so both must be ready even when the device is working.
- ✓A revoked ELD counts as no ELD. FMCSA's 60-day window for the five devices removed on August 6, 2026 closed on October 6, 2026, and a driver still using one can be placed out of service.
In This Guide
- What Is ELD Troubleshooting? Malfunctions vs. Data Diagnostic Events
- ELD Malfunction Triggers and Data Diagnostic Events Explained
- Common ELD Problems and How to Fix Them
- What to Do When Your ELD Malfunctions: Driver and Carrier Duties
- ELD Problems at Roadside Inspection
- Revoked, Exempt, or Unregistered: When the ELD Itself Is the Problem
- How to Prevent ELD Problems on the Road
- Frequently Asked Questions
- The Bottom Line
What Is ELD Troubleshooting? Malfunctions vs. Data Diagnostic Events
ELD troubleshooting is the process of finding out why an electronic logging device has stopped recording, connecting, or transferring hours-of-service data correctly, then responding the way the federal rule requires. The right response depends on the type of fault. The rule separates ELD malfunctions from data diagnostic events, and the two carry very different obligations.
A data diagnostic event is the ELD's flag that it detected a data inconsistency. Under § 395.34(c), the driver follows the recommendations of the motor carrier and the ELD provider to resolve it. The paper-log duties in § 395.34(a) apply to malfunctions, not to data diagnostic events.
A malfunction is the ELD's own finding that it can no longer meet a technical requirement in Appendix A. The motor carrier must correct it, and the driver keeps manual records until the device is repaired or replaced. FMCSA's ELD malfunction and data diagnostic event FAQs state the split plainly: the driver usually resolves a data inconsistency, but a motor carrier must correct a malfunction.
For an owner-operator, that split has a practical edge, because the driver and the motor carrier are often the same person. The notice a driver owes the carrier within 24 hours, the 8-day repair clock the carrier owns, and any extension request to FMCSA all land on one desk. HDJ's ELD compliance guide for fleet management covers the same rules from the fleet side.
ELD Malfunction Triggers and Data Diagnostic Events Explained
The ELD decides when a fault becomes a malfunction, using thresholds written into Appendix A. As of October 2026, the specification defines six compliance malfunctions, plus an "other" category that providers can use for technology-specific faults. Each has a matching early warning in most cases, so a data diagnostic event often appears before the malfunction sets. A provider's app may label faults differently, so match the on-screen message to the fault category in the table rather than to a code number.
| Fault | Malfunction triggers when | Related data diagnostic event | First checks |
|---|---|---|---|
| Power | The ELD understates in-motion driving time by an aggregate of 30 minutes or more in 24 hours, across all driver profiles | ELD is not powered and fully functional within 1 minute of engine power, or loses power with the engine running | Connector seating, cable, power circuit fuse |
| Engine synchronization | Connection to a required engine data source is lost for more than 30 minutes in 24 hours, across all profiles | ELD cannot get updated values within 5 seconds of need | Engine data link connection and adapter |
| Timing | ELD can no longer hold UTC accuracy; absolute deviation may not exceed 10 minutes | None defined | Provider support; device clock source |
| Positioning | No valid position within 5 miles of the moving vehicle after 60 minutes | Position unavailable, recorded with "X" in the latitude and longitude fields | Antenna view, location services, mounting |
| Data recording | ELD cannot record or retain required events, or retrieve logs the carrier does not keep remotely | None paired; a missing required data element is logged as its own event | App or firmware version; provider support |
| Data transfer | ELD stays in unconfirmed mode through three consecutive monitoring checks | A transfer-mechanism check fails (tested at least every 7 days) | Run the test transfer; connectivity settings |
Unidentified driving has its own threshold. The ELD records a data diagnostic event when more than 30 minutes of driving in 24 hours is logged to the Unidentified Driver profile. The indicator stays on for the current 24-hour period and the following 7 days, and it clears when unidentified driving across the current period and the previous 7 days drops to 15 minutes or less.
The ELD shows two separate indicators. One malfunction indicator serves all drivers and must be lit whenever a malfunction is active and visible from the normal driving position. A separate data diagnostic indicator shows active events for the logged-in driver only, and a lit malfunction indicator is the trigger for the paper-log steps later in this guide.
The ELD's own records carry the evidence. Appendix A requires the printout to list up to 10 of the most recent malfunctions and up to 10 of the most recent data diagnostic events for the report period, so the record of what failed, and when, is on the device itself. That printout is the first thing to read before calling the provider, because it tells the provider which fault category to look at.
Common ELD Problems and How to Fix Them
Most ELD problems trace to power, the engine connection, location, time, unidentified driving, or data transfer, and each has a first check an owner-operator can run in minutes. Treat this ELD troubleshooting routine as a set of steps before a service call, not a replacement for the provider's own instructions, which § 395.34(c) tells the driver to follow.
ELD Won't Power On or Keeps Losing Power
A power fault means the ELD was not powered and fully functional within 1 minute of engine power, or lost power while the engine ran. Start with the physical path: confirm the device is fully seated in its connector, look for bent, spread, or corroded pins, and check that the cable is not pinched near the seat base or kick panel.
A loose connector that drops out for a few minutes at a time can add up to the 30-minute aggregate that sets a power malfunction before the driver notices. If the connector is sound, check supply voltage and ground at the port and inspect the circuit's fuse. HDJ's heavy-duty truck electrical troubleshooting guide covers the general diagnostic approach.
ELD Loses Its Connection to the Engine
Engine synchronization problems come from a broken link to the engine control module (ECM), the source of engine power status, vehicle motion, miles driven, and engine hours. For a vehicle of model year 2000 or later with an ECM, Appendix A requires the ELD to establish a link to the ECM when the engine is powered.
A data diagnostic event is logged when updated values cannot be obtained within 5 seconds of need, and a compliance malfunction follows once the loss exceeds 30 minutes in 24 hours. Reseat the connector first, then ask the provider whether the truck needs a specific adapter or cable. If the connection still fails, a diagnostic scan of the truck will show whether the ECM is communicating.
GPS Position Errors and Missing Location
A position fault means the ELD could not obtain a valid location. It records a data diagnostic event, with "X" in the latitude and longitude fields, when no fix is available. It records a positioning malfunction when it fails to acquire a valid position within 5 miles of the moving vehicle and 60 minutes have passed.
Location fixes depend on a clear view of the sky. For a portable ELD, 49 CFR 395.22 requires the carrier to ensure the device is mounted in a fixed position where the driver can see it from the normal driving position, so check that location services are on for the app and that nothing blocks the antenna. If the vehicle is moving at a duty-status change with no fix and the driver skips the manual location prompt, the ELD records a missing-data event.
Clock and Timing Errors
A timing malfunction means the ELD can no longer hold UTC accuracy, with an absolute deviation of no more than 10 minutes allowed. Because the ELD cross-checks itself against an external UTC source, a drifting clock is a device-level fault. It goes straight to the provider and starts the paper-log steps in the next section.
Unidentified Driving Records
When the vehicle moves with no driver logged in, the ELD assigns the driving to a single Unidentified Driver account under § 395.32(a). At the next login, the driver reviews the unassigned time the ELD presents and either takes the records that belong to the driver or marks the rest as not attributable.
The motor carrier must make sure those records are reviewed, then annotate each one to explain the unassigned time or assign it to the right driver, and keep the records for at least six months. For an owner-operator, the simplest prevention is a habit: log in before the truck moves.
Data Transfer Failures
The ELD verifies its data transfer mechanism at least every 7 days. A failed check logs a data diagnostic event, the ELD enters an unconfirmed mode and rechecks at least every 24 hours, and three consecutive failed checks set a data transfer malfunction.
Run the provider's test transfer after installing the device and after any app update, and leave the settings the transfer depends on, such as Bluetooth, mobile data, or email, unchanged until the next test passes.
Key Recommendation
Before paying for service or swapping hardware, run a three-minute reset in this order: reseat the connector, cycle the ignition and restart the ELD app, then check both indicators. If the malfunction indicator is still lit, stop troubleshooting and start the written notice and paper logs in the next section, because every hour of delay adds undocumented driving.
What to Do When Your ELD Malfunctions: Driver and Carrier Duties
When the malfunction indicator lights, ELD troubleshooting stops and 49 CFR 395.34(a) takes over. It gives the driver three duties: note the malfunction and give the motor carrier written notice within 24 hours, reconstruct the record of duty status (RODS) for the current 24-hour period and the previous 7 consecutive days, and keep preparing manual RODS until the ELD is serviced and compliant.
Whose notice, and whose clock, depends on how the owner-operator operates. An owner-operator running under their own operating authority is the motor carrier, so the notice and the repair clock are both theirs. A leased owner-operator reports to the carrier whose authority the truck runs under, and that carrier's 8-day clock applies. A free lookup of a U.S. Department of Transportation (USDOT) number shows which operating authority is active.
- Write the malfunction down. Record the date, time, location, odometer, and which indicator lit, and photograph the ELD screen. Because the carrier's 8-day clock runs from discovery or notice, whichever comes first, a dated note is proof of when it started.
- Reconstruct the previous 7 days. The driver does not need to hand-copy days the ELD can still retrieve. FMCSA's FAQ says a printed copy, or an electronic copy such as a PDF, can stand in for manual reconstruction.
- Keep paper logs on graph-grid. The in-cab ELD information packet in § 395.22(h) must hold a data transfer instruction sheet, a malfunction reporting instruction sheet, and at least 8 days of blank driver's record of duty status graph-grids.
Free DOT Status Check
Enter a USDOT number and quickly review public carrier status, operating authority and key FMCSA registration data.
The motor carrier must correct, repair, replace, or service the ELD within 8 days of discovering the malfunction or receiving the driver's notice, whichever comes first. A carrier that needs more time must notify the FMCSA Division Administrator for its principal place of business within 5 days after the driver's notice.
The extension request must be signed and include the carrier's contact information, the make, model, and serial number of each ELD, the date and location of each malfunction, and a concise statement of its good-faith repair efforts. A carrier that files a compliant request is treated as complying with the ELD requirement until FMCSA decides, provided the carrier and its drivers meet the section's other requirements. HDJ's FMCSA compliance requirements guide covers the wider set of carrier duties.
ELD Problems at Roadside Inspection
If an ELD fails during an inspection, § 395.34(b) requires the driver to give the authorized safety official the manually kept records. FMCSA's ELD data transfer FAQ adds that the driver must be able to show the ELD display or a printout when an official asks for a physical display.
ELD data reaches an inspector one of two ways, depending on the device: a telematics transfer through web services or email, or a local transfer through USB 2.0 or Bluetooth. If a transfer fails and another method is available, the officer can try it or review the display or printout instead.
If only the ELD has a connectivity problem, FMCSA notes the device may be flagged as potentially non-compliant. A driver who cannot access records for a period because of limited coverage may be cited for hours-of-service violations or for operating without an ELD.
Keep the information packet where it can be reached without unloading anything, and practice the transfer steps once. A first attempt at roadside is the wrong time to start ELD troubleshooting. HDJ's complete DOT inspection checklist covers the rest of what an inspector examines.
The penalty for operating without a required ELD is time. The Commercial Vehicle Safety Alliance (CVSA) said in its April 1, 2018 announcement of full ELD enforcement, which began April 1, 2018, that drivers of property-carrying vehicles operating without a required ELD would be placed out of service for 10 hours, after which they could continue to their destination with a paper record of duty status and a copy of the inspection report.
Hours-of-service violations also count toward the carrier's Compliance, Safety, Accountability (CSA) record, so a recurring ELD problem costs more than one inspection. HDJ's CSA score improvement strategies explain how carriers work that score down.
Revoked, Exempt, or Unregistered: When the ELD Itself Is the Problem
A device that is not on FMCSA's registered list is not a compliant ELD, no matter how well it records. Under 49 CFR 395.22(a), a carrier required to use an ELD must use one on the list, and FMCSA describes the Registered Devices list as devices that providers have registered and self-certified as compliant with the rule.
FMCSA removes devices that fail to meet the minimum requirements. As of October 2026, its removal notices dated January 13, May 20, and August 6, 2026 covered 4, 12, and 5 devices, and each gave carriers 60 days to replace a revoked device with a compliant one. Revoked devices go on a separate Revoked Devices list.
The August notice set the final deadline: FMCSA's August 6, 2026 notice told carriers to replace the revoked devices before October 6, 2026. Since that date, a carrier still using one of them is treated as operating without an ELD, and the driver can be placed out of service. Until a replacement is installed, drivers of a revoked device go back to paper logs or logging software.
⚠️ Safety Warning
Check the device against FMCSA's Registered Devices and Revoked Devices lists today, not at the next inspection. A revoked ELD does not satisfy 49 CFR 395.8(a)(1), and an officer will treat the driver as operating without an ELD.
When ELD troubleshooting fails to fix a device and it must be replaced, registration status is the first filter, and HDJ's ELD software guide for small fleets covers the other selection factors. Keep the revoked device's records, because the motor carrier must retain records of duty status for six months.
Some drivers do not need an ELD at all, and that is an exception, not a malfunction. Under 49 CFR 395.8(a)(1)(ii)(A), a driver may keep paper RODS if the vehicle is driven in a manner that requires a record of duty status on not more than 8 days in any 30-day period, in certain driveaway-towaway operations, or if the vehicle was manufactured before model year 2000, as shown in the vehicle identification number (VIN) on the registration.
How to Prevent ELD Problems on the Road
Most ELD troubleshooting can be avoided with a short, repeatable routine. These habits address the faults covered above:
- Check both indicators before moving the truck. The ELD must show a malfunction indicator and a data diagnostic indicator whenever either is active, so a lit indicator at start-up is a head start on the notice and paper-log steps.
- Inspect the connector and cable on every pre-trip. A seated connector, clean pins, and an unpinched cable cover the most common power and engine-link faults before they reach the 30-minute aggregates.
- Certify the day's logs before shutting down. FMCSA recommends certifying RODS before logging off the ELD and shutting down the engine, because skipping it can trigger codes such as unaccounted odometer changes or suspicious driving activity.
- Log in before the truck moves. That one habit keeps the Unidentified Driver profile empty and the 30-minute diagnostic threshold out of reach.
- Keep the ELD information packet complete. Replace used graph-grids so at least 8 days of blanks are always on board, and keep the transfer and malfunction instruction sheets with them.
Free Diesel Maintenance Checklist
Get HDJ's free, field-tested diesel maintenance checklist delivered instantly to your inbox — print it, laminate it, keep it in the shop.
Instant PDF • 100% Free • No Spam
Records need the same attention as hardware. A carrier keeps a backup copy of ELD records for six months on a device separate from the original data under § 395.22(i), and owner-operators should ask their provider how that backup is handled before they need it.
The same discipline applies to the paper side. Store the written malfunction notice, the repair or replacement paperwork, and the reconstructed logs together, so the file answers the questions an auditor or inspector asks without rebuilding the timeline from memory.
A fault that returns after the connector, cable, and settings checks usually belongs to the device or its adapter. At that point replacement beats repeated service calls, because the 8-day clock keeps running either way, and the registered list is the place to confirm the replacement is eligible.
Frequently Asked Questions
What is the difference between an ELD malfunction and a data diagnostic event?
A data diagnostic event flags a data inconsistency that the driver usually resolves by following the ELD provider's and carrier's instructions. A malfunction means the ELD cannot meet a technical requirement, so the driver switches to paper logs and the carrier must correct it within 8 days under 49 CFR 395.34.
What should a driver do when the ELD malfunctions?
Note the malfunction, give the motor carrier written notice within 24 hours, and reconstruct the current 24-hour period and the previous 7 consecutive days on paper. Keep manual records until the ELD is serviced and compliant, and carry the blank graph-grids from the ELD information packet.
How long does a carrier have to fix a broken ELD?
Eight days, counted from when the carrier discovers the malfunction or receives the driver's notice, whichever comes first. A carrier needing more time must notify its FMCSA Division Administrator within 5 days after the driver's notice and show good-faith repair efforts.
Can a driver be put out of service for an ELD problem?
Yes. A driver operating without a required ELD, including one using a revoked device after FMCSA's deadline, can be placed out of service. CVSA announced a 10-hour out-of-service period for property-carrying drivers when full enforcement began in 2018, after which they may continue with paper logs.
Why does my ELD show unidentified driving?
The ELD assigns movement to an Unidentified Driver account when the vehicle moves with no driver logged in. Review those records at your next login and take the ones that are yours. More than 30 minutes of unidentified driving in 24 hours triggers a data diagnostic event.
Does a truck built before 2000 need an ELD?
No. Under 49 CFR 395.8(a)(1)(ii)(A), a vehicle manufactured before model year 2000, as shown in the VIN on the registration, is excepted. A driver who needs a record of duty status on no more than 8 days in any 30-day period may also use paper logs.
The Bottom Line
ELD troubleshooting comes down to telling the two fault types apart, working to the right clock, and carrying the paperwork that proves it. A data diagnostic event gets resolved with the provider's steps. A malfunction triggers written notice within 24 hours, a seven-day reconstruction on paper logs, and a repair or replacement within 8 days.
Michael Nielsen and the HDJ editorial team will update this guide at heavydutyjournal.com as FMCSA publishes new ELD revocations and rule changes, and they re-check the thresholds above against Appendix A each time.
Pass This to a Fellow Owner-Operator
Any owner-operator running an ELD can use the 24-hour notice and 8-day repair steps before the next roadside inspection. The Heavy Duty Journal guide is free at heavydutyjournal.com.
