Drive App — Driver's Guide to Diagnostic and Malfunction Events
User Guide
0 mins to read
Learn about diagnostic and malfunction events, including diagnostic codes and potential next steps, and review driver and carrier responsibilities regarding ELD malfunctions.
Driver’s Guide to Data Diagnostic and Malfunction Events for USA and Canada
Troubleshooting Data Diagnostic and Malfunction Events
1 | Press the Malfunction Notifications button or the red bar to see more details. |
|
2 | Review the Data Diagnostic Events table. When you have investigated the diagnostic data, address the issue. |
|
3 | Review the Malfunction Events table. When you have investigated the malfunction and addressed the problem, press the Clear button. |
|
4 | Review and practice the following Driver and Carrier Responsibilities applicable to your country of operation: |
|
Data Diagnostic Events
✱ NOTE: Data Diagnostic events cannot be cleared by the driver, these will auto-clear once the issue is resolved.
Diagnostic Code | Data Diagnostic Event | What should I do next? |
1 | Power data diagnostic: The ELD records a power data diagnostic event when an ELD is not powered and fully functional within one minute of the vehicle’s engine turning on, and does not remain powered for as long as the vehicle’s engine stays powered. |
|
2 | Engine synchronization data diagnostic: The ELD records an engine synchronization data diagnostic event when an ELD loses ECM connectivity to any of the required data sources (i.e. engine power status, vehicle motion status, miles driven, engine hours), and can no longer retrieve updated values for the required ELD parameters within five seconds of the request. |
|
3 | Missing required data elements data diagnostic: The ELD records a missing required data elements data diagnostic event when any required data field is missing at the time of its recording. |
|
4 | Data transfer data diagnostic: The ELD records a data transfer data diagnostic when the operation of the data transfer mechanism(s) cannot be confirmed. The ELD verifies this operation at least once every seven days. |
|
5 | Unidentified driving records data diagnostic: The ELD records an unidentified driving record diagnostic event when more than 30 minutes of driving time by an unidentified driver is recorded within a 24-hour period. When the diagnostic is recorded, the ELD turns on the data diagnostic indicator for all drivers logged into the ELD for the current 24-hour period, and the seven days that follow. |
|
6 | “Other” ELD identified diagnostic: The other ELD identified diagnostic is not supported. |
|
Malfunction Events
✱ NOTE: Malfunction events must be cleared by the driver upon identifying and resolving the issue.
Malfunction Code | Malfunction Event | What should I do next? |
P | Power data malfunction: The ELD records a power data malfunction when an ELD is not powered for a cumulative in-motion driving time of 30 minutes or more over a 24-hour period, for all drivers. | |
E | Engine synchronization compliance malfunction: The ELD records an engine synchronization compliance malfunction when ECM connectivity to any of the required data sources (i.e. engine power status, vehicle motion status, miles driven, engine hours) is lost for more than 30 minutes during a 24-hour period, for all drivers. | |
T | Timing compliance malfunction: The ELD records a timing compliance malfunction when it fails to synchronize with an external UTC source, and can no longer meet the underlying timing compliance requirement not to exceed an absolute deviation of 10 minutes at any time. | |
L | Positioning compliance malfunction: The ELD records a positioning compliance malfunction when it fails to acquire a valid position measurement within five miles of the commercial motor vehicle’s movement, after 60 minutes has elapsed. | |
R | Data recording compliance malfunction: The ELD records a data recording compliance malfunction when it can no longer record or retain required events, or retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier. | |
S | Data transfer compliance malfunction: The ELD records a data transfer compliance malfunction when the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks. | |
O | “Other” ELD identified malfunction: The other ELD identified malfunction is not supported. |
! IMPORTANT: If you lose network coverage for extended periods while logged into your ELD, you must manually enter your record of duty status (RODS) in the application. If you are not logged into the ELD you must record your RODS on paper until you are able to log back in.
Responsibilities for ELD Malfunctions (USA)
Driver’s Responsibilities for ELD Malfunctions | Carrier’s Responsibilities for ELD Malfunctions |
|
|
Responsibilities for ELD Malfunctions (Canada)
Driver’s Responsibilities for ELD Malfunctions | Carrier’s Responsibilities for ELD Malfunctions |