Key Takeaways
- Appendix A, Table 4 lists seven standardized malfunction codes (P, E, T, L, R, S, O) and six data diagnostic codes (1-6). A provider may also show its own explanatory message.
- A data diagnostic event signals an inconsistency to investigate. A malfunction triggers the driver notice and carrier repair rules in 49 CFR 395.34 and FMCSA guidance; paper or other compliant manual records are needed when the fault prevents accurate hours-of-service recording or presentation.
- The driver must note a malfunction and give the carrier written notice within 24 hours. When required records are unavailable, reconstruct the current 24-hour period and previous seven consecutive days unless the records are already held or retrievable.
- The carrier must correct the malfunction within eight days of discovering it or receiving driver notice, whichever is earlier. A carrier seeking more time must request an extension from the appropriate FMCSA Division Administrator within five days after driver notice.
- A failed roadside transfer alone does not prove a data-transfer compliance malfunction. Check the device’s supported transfer option and make the records available by display or printout when appropriate.
- An ELD removed from FMCSA’s registered list is a separate issue. Check the registered ELD list and the specific FMCSA removal notice for its replacement deadline.
| Table of Contents |
|---|
| What a Malfunction Code Means |
| Malfunction and Diagnostic Codes |
| Driver Response Steps |
| Carrier Obligations |
| Reducing Malfunction Risk |
| ELD vs. Paper Log Period |
| Questions to Ask |
| FAQs |
Introduction
An ELD can show a data diagnostic event, a compliance malfunction, or a manufacturer-specific message. Those are not interchangeable. The code and the condition behind it determine what the driver and carrier need to do, and a single warning does not automatically require paper logs, a citation, or an out-of-service order.
This guide explains the federal code set, the difference between an inconsistency and a malfunction, the driver and carrier steps in 49 CFR 395.34, and how to handle a failed data transfer. For device-specific display and troubleshooting instructions, use the installed ELD’s current manual or contact the provider. Geosavi’s ELD overview explains the available platform at a high level. Geosavi customers can reach Geosavi support; support does not replace the driver’s or carrier’s regulatory responsibilities.
What Does an ELD Malfunction Code Mean?
An ELD records a standardized malfunction or data diagnostic code when its required self-monitoring detects a specified condition. Appendix A to Subpart B of Part 395, Table 4 defines the codes; the device’s screen may use additional words or symbols. Confirm the actual code and device status before treating a general app or connectivity message as a federal malfunction.
A data diagnostic event identifies a data inconsistency. Under § 395.34(c), the driver follows the carrier’s and ELD provider’s recommendations to resolve it and reviews and certifies the record as required. A malfunction requires the driver to note it and notify the carrier in writing within 24 hours, and it starts the carrier’s repair clock. Whether manual records are needed depends on whether the malfunction prevents accurate recording or presentation of hours-of-service data; FMCSA distinguishes that situation from a fault that does not impair the records.
A revoked or removed ELD is different from a device malfunction. If FMCSA removes a model from the registered list, follow its particular removal notice and deadline. Do not assume a blanket 60-day period or use the eight-day malfunction rule to decide how long a removed device may remain in service.
What Are the Six ELD Malfunction Types?
The federal table contains seven malfunction codes and six data diagnostic codes. The letters below identify malfunctions; a provider-specific message can help troubleshoot but does not replace the standardized code. Thresholds and descriptions come from Appendix A, sections 4.6 and Table 4.
P – Power compliance
The ELD detects a power-related problem that understates in-motion driving time by 30 minutes or more over a 24-hour period across driver profiles. A shorter or potential power problem can first produce diagnostic code 1.
E – Engine synchronization compliance
This malfunction occurs when connectivity to a required engine data source is lost for more than 30 minutes in a 24-hour period, aggregated across profiles. Diagnostic code 2 can appear earlier when required updated values cannot be acquired within the specified interval. Investigate the connection without assuming a particular cable is the cause.
T – Timing compliance
The ELD must keep its time within 10 minutes of UTC. A timing malfunction is recorded when it can no longer meet that requirement.
L – Positioning compliance
The ELD records this malfunction when it cannot obtain a valid position within five miles of vehicle movement for more than 60 cumulative minutes over 24 hours. A temporary GPS gap alone does not establish the malfunction.
R – Data recording compliance
This code applies when the ELD can no longer record or retain required events, or retrieve required logs not otherwise cataloged remotely by the carrier. A missing required field can instead produce diagnostic code 3.
S – Data transfer compliance
The ELD checks its supported transfer mechanism at least once every seven days. An unconfirmed check creates diagnostic code 4; if the ELD remains unconfirmed through the next three consecutive checks, conducted at least daily, it records an S malfunction. This is not a count of three failed roadside attempts.
O – Other ELD-detected malfunction
This code covers another ELD-detected malfunction under the standard. Ask the provider what the device’s accompanying message means.
Data diagnostic codes 1-6
The standardized diagnostics are 1 power, 2 engine synchronization, 3 missing required data elements, 4 data transfer, 5 unidentified driving records, and 6 other ELD-identified diagnostic event. These are diagnostic codes, not additional malfunction types. For roadside transfer methods, see our ELD data-transfer guide.
What Must the Driver Do When an ELD Malfunction Code Appears?
First identify whether the device reports a diagnostic or a malfunction. For a diagnostic, follow the carrier’s and provider’s instructions to resolve the inconsistency and check the affected records. For a malfunction, note the condition and give the motor carrier written notice within 24 hours under § 395.34(a)(1). A call to support can help troubleshoot, but it does not replace the required carrier notice.
If the malfunction prevents accurate recording or presentation of hours-of-service data, reconstruct the current 24-hour period and previous seven consecutive days on compliant graph-grid records unless those records are already in the driver’s possession or retrievable from the ELD. Then continue preparing compliant manual records until the ELD is repaired or replaced. Do not invent a paper record for time already accurately recorded. Our ELD shift guide covers routine record review and certification. At roadside, make the required current and previous seven days of records available, using retrievable ELD data and reconstructed records as applicable. See FMCSA’s malfunction guidance.
A failed electronic transfer by itself does not prove that records are missing or that an S malfunction has occurred. The officer may use another available method or inspect the ELD display or printout. Follow the installed device’s data-transfer instructions and FMCSA’s transfer guidance. Under the July 22, 2026 final rule, the ELD user manual no longer has to be kept in the cab, but the data-transfer and malfunction instruction sheets and a supply of blank graph-grid records sufficient for at least eight days remain required under § 395.22(h).
What Are the Carrier’s Obligations After a Malfunction Is Reported?
The motor carrier must correct, repair, replace, or service a malfunctioning ELD within eight days of discovering the condition or receiving the driver’s notice, whichever happens first, under § 395.34(d)(1). Arrange a functioning, registered ELD and ensure the driver keeps compliant records while an impairing malfunction remains unresolved. Reassigning a driver to a properly equipped vehicle may allow that driver to work, but it does not by itself repair the malfunctioning device.
If additional repair time is necessary, the carrier must notify the FMCSA Division Administrator for the State of its principal place of business within five days after the driver notifies the carrier under § 395.34(d)(2). The signed request must identify the carrier representative and affected ELDs, state when and where the malfunction was reported, and describe good-faith repair efforts and why more time is needed. An extension is not automatic; follow FMCSA’s determination. FMCSA’s FAQ summarizes the required contents.
Keep the driver’s notice, troubleshooting details, and accurate duty-status records under applicable carrier procedures. Do not apply ELD editing provisions in § 395.30 to paper logs as though they were ELD edits. A malfunction code alone does not establish a citation, SMS consequence, or out-of-service result; an officer evaluates the actual records and circumstances.
How Can Your Fleet Reduce the Risk of ELD Malfunction Codes?
Check the condition behind the code before replacing hardware. Record the standardized code, any provider message, the time, the affected vehicle and driver, and whether duty-status data remains accurate and accessible. Follow the installed device’s instructions and involve the carrier and provider as appropriate; do not clear an alert merely to hide it.
Inspect the power supply and engine-data connection when those systems are implicated, and test the transfer option supported by the actual ELD. A compliant device supports either the complete telematics option (web services and email) or the complete local option (USB 2.0 and Bluetooth); it need not support all four. A roadside transfer problem may be related to coverage or equipment rather than an ELD malfunction. Our ELD installation checklist can help organize device setup, but use current provider instructions for model-specific troubleshooting.
How Does ELD Compliance Change When a Malfunction Occurs?
| Situation | Driver response | Carrier response |
|---|---|---|
| Data diagnostic event | Review the record and follow carrier/provider instructions to resolve the inconsistency. | Help investigate and monitor the event; do not assume an eight-day repair clock applies. |
| Malfunction, HOS data still accurate and available | Note the malfunction and notify the carrier in writing within 24 hours; confirm record accuracy. | Correct the malfunction within eight days of discovery or notice, whichever is earlier. |
| Malfunction impairs HOS recording or presentation | Give written notice; reconstruct unavailable current-day and prior-seven-day records as required, then keep compliant manual records until service is restored. | Arrange repair/replacement and ensure the driver maintains compliant records; request an extension on time if necessary. |
| Electronic transfer fails at roadside | Follow device instructions; make required records available by another supported method or display/printout when appropriate. | Investigate the issue; a single failed transfer is not automatically an S malfunction. |
What Should You Ask Before and During an ELD Malfunction?
How do I know whether the alert is a malfunction or a diagnostic event?
Check the standardized code and device indicator. P, E, T, L, R, S, and O are malfunction codes; 1 through 6 are diagnostic codes. A provider may add its own text. Use the device’s instructions to interpret the display, and verify whether hours-of-service data remains accurate and available.
Is a revoked ELD the same as a malfunction?
No. A malfunction is a device condition addressed under § 395.34. A device removed from the FMCSA registered ELD list is subject to its specific removal notice and replacement deadline. Do not assume the malfunction repair period applies to a removed device.
Does a code disappear after repair?
The ELD must record detection and clearing of malfunction and diagnostic events under Appendix A. The current display can change when a problem is resolved, but a historical event is not automatically erased. A recorded event alone is not proof of a violation.
What must remain in the cab?
Under § 395.22(h), the packet must include the device-specific data-transfer instruction sheet, malfunction reporting and recordkeeping instruction sheet, and enough blank graph-grid records for at least eight days. The separate requirement to carry the ELD user manual was rescinded effective July 22, 2026. See the FMCSA final rule.
Can a malfunction automatically place a driver out of service?
No automatic outcome follows from a code alone. The officer evaluates the applicable rules, available records, and any actual violations under current enforcement criteria. Do not promise that paper logs, a support ticket, or a repaired device guarantees a particular inspection result.
Must the carrier report every malfunction to FMCSA?
The routine rule requires driver notice to the carrier and carrier correction; it does not create a general FMCSA filing for every malfunction. A carrier seeking more repair time must send a signed extension request to the proper FMCSA Division Administrator within five days after driver notice.
What if the device is replaced on day three?
Keep accurate records for the period when HOS data could not be recorded or presented by the ELD. A new functioning device does not erase records already required. Carriers retain required RODS and supporting documents for at least six months from receipt under § 395.8(k)(1).
When should we consider changing ELD providers?
Investigate recurring faults using the device’s documented codes, maintenance history, and provider response. Check the exact model’s status on the FMCSA list. A registered device malfunction and an FMCSA removal notice require different decisions; avoid assuming a universal replacement grace period.
Common Questions About ELD Malfunction Codes
About ELD Malfunction Codes and Compliance
What is an ELD malfunction code?
It is a standardized code recorded when an ELD detects a specified compliance malfunction. Appendix A, Table 4 lists P, E, T, L, R, S, and O. Provider messages may add detail but are not substitutes for the standard code.
Is a malfunction the same as a data diagnostic event?
No. Diagnostic codes 1-6 identify data inconsistencies to investigate under carrier and provider instructions. A malfunction requires written driver notice to the carrier within 24 hours and carrier correction under § 395.34. Manual records are needed when the malfunction prevents accurate HOS recording or presentation.
What are the seven standardized malfunction codes?
P is power, E engine synchronization, T timing, L positioning, R data recording, S data transfer, and O other ELD-detected malfunction. Diagnostic codes 1-6 are a separate set.
How long can a driver use manual records after an impairing malfunction?
Use compliant manual records until the ELD is repaired or replaced. The carrier normally must correct the malfunction within eight days of discovery or driver notice, whichever is earlier. An extension requires a timely request to the appropriate FMCSA Division Administrator and is not automatic.
Does a malfunction code automatically affect a carrier’s CSA data?
No. The code itself is not an SMS measure. A documented roadside violation may affect the carrier’s Hours-of-Service Compliance BASIC under FMCSA’s methodology, but the outcome depends on what the officer finds and records.
What records must a driver make available at roadside?
The driver must be able to present the current day and previous seven days of required duty-status records. Use available ELD records and reconstructed or manual records as applicable. A failed transfer may be addressed through another supported method or the device’s display or printout; follow FMCSA’s transfer guidance.
About Carrier Obligations and Device Replacement
What must a carrier do within eight days?
Correct, repair, replace, or service the malfunctioning ELD within eight days of discovering the condition or receiving driver notice, whichever is earlier. If more time is needed, submit a signed extension request within five days after driver notice to the FMCSA Division Administrator for the State of the carrier’s principal place of business.
Can a carrier treat paper records as ELD edits?
No. Paper RODS are not ELD records to edit under § 395.30. Drivers and carriers should keep accurate, legible original records and follow the applicable paper-record and retention rules.
What if an engine-data problem triggers the malfunction?
Check the recorded code, affected HOS data, and provider instructions. An engine synchronization malfunction can arise when required data sources are unavailable beyond the Appendix A threshold; the physical cause cannot be assumed from the code alone.
How long must malfunction-period RODS be retained?
The motor carrier retains required records of duty status and supporting documents for at least six months from the date of receipt under § 395.8(k)(1).
When should a fleet replace rather than repair an ELD?
A carrier can choose repair or replacement that restores compliance within the applicable period. If FMCSA has removed the model from the registered list, follow that model’s removal notice and replacement deadline instead of the malfunction procedure.
Conclusion
An ELD alert is a starting point for diagnosis, not an automatic citation or a universal instruction to switch to paper. Identify the standardized code, determine whether records remain accurate and available, and follow the distinct steps for a diagnostic event or a malfunction. For a malfunction, the driver provides written notice within 24 hours and the carrier corrects the device within eight days of discovery or notice, whichever comes first. Manual records are necessary when the fault impairs accurate HOS recording or presentation, with earlier records reconstructed when they are not already available.
Keep device-specific instructions accessible, check the registered ELD list separately from malfunction status, and use Geosavi support for questions about your installed device. For help evaluating an ELD setup, contact Geosavi or call (800) 261-4361.