Malfunctions and data diagnostics
What the red malfunction and the data diagnostic banners mean, what each code is, and what you must do.
The ELD checks itself all the time. When something is wrong it shows a banner at the top of every screen (49 CFR 395 Appendix A, section 4.6). There are two kinds:
| Banner | Meaning | Can you keep driving on the ELD? |
|---|---|---|
| Red: ELD malfunction: ... · keep paper logs | The ELD can't record reliably. | Use paper logs until it is fixed. |
| Calm: ... · you can keep driving | A data diagnostic: a data problem the ELD noticed. | Yes. You do not need paper logs. |
Keep the malfunction instruction sheet in the truck.
If there is a malfunction
Tap the red banner. The ELD malfunction screen lists What to do now:
- Tell your carrier in writing within 24 hours. Tap Message dispatch to send a message from the app (when your carrier uses messaging).
- Keep paper logs for today: use a graph-grid log until the ELD is fixed. Write each duty status change with its time and location.
- Have the previous 7 days ready: tap Show 7 days to show or copy them for an inspector.
Tap each step to mark it done. If an officer stops you, tap Start roadside inspection to show your logs (see Roadside inspection).
This is required by 49 CFR 395.34. Your carrier must repair or replace the ELD within 8 days.
Malfunction codes
| Code | Name | Typical cause |
|---|---|---|
| P | Power compliance | The ELD was without power for 30 minutes or more of driving time in 24 hours. |
| E | Engine synchronization compliance | No engine data for 30 minutes or more in 24 hours while the engine was on. |
| T | Timing compliance | The ELD's time is off by more than 10 minutes. |
| L | Positioning compliance | No valid location for 60 minutes or more of driving in 24 hours. |
| R | Data recording compliance | The phone could not store records. |
| S | Data transfer compliance | The periodic check that records can be sent to FMCSA failed several times in a row. |
| O | Other ELD detected malfunction | Another problem the ELD detected. |
Data diagnostic codes
| Code | Name | What to do |
|---|---|---|
| 1 | Power data diagnostic | The ELD may have been unpowered while the truck moved. Check the device is plugged in and keep the app running. |
| 2 | Engine synchronization data diagnostic | Engine data from the ELD device was late. Check the device connection on the ELD tab. |
| 3 | Missing required data elements | A record is missing a required item, for example its location. Fix or annotate the record. |
| 4 | Data transfer data diagnostic | The periodic check that logs can be sent to FMCSA failed. At roadside, show your logs on the inspection screen. |
| 5 | Unidentified driving records data diagnostic | More than 30 minutes of unidentified driving. Review it in More > Edits & unidentified driving (see Unidentified driving). |
| 6 | Other ELD identified diagnostic | Another data problem, for example late device data added to the log. Review any unidentified driving it created. |
Tap the diagnostic banner to open the HOS tab, where a card explains the active diagnostic.
When they clear
Most malfunctions and diagnostics clear automatically once the problem is gone, for example when engine data arrives again, a data transfer check passes, or unidentified driving is reviewed. The banner disappears when nothing is active.
What if
- The PT30 won't connect: see PT30 won't connect.
- No engine data: see No engine data.
- The malfunction does not clear: tell your carrier and keep using paper logs. Your carrier must fix or replace the ELD within 8 days.