Troubleshooting Malfunctions and Diagnostic Issues

Viewing Malfunctions and Diagnostic Events

If you are experiencing any malfunctions or diagnostic issues, the indicators in the lower right corner of the HOS Status screen turns red or orange, respectively. The indicators remain colored until the malfunction or diagnostic has been resolved. A banner in the matching color displays in the lower part of the screen. The banner displays every time a new malfunction or diagnostic event occurs. It also displays after you sign in, if the malfunction or diagnostic event is still active. Tap the banner or the diagnostic indicators to open the Indicators screen. This screen lists information about all malfunctions and diagnostic events that are currently applicable.
 

     
 

When using WorkPlan as an AOBRD the single diagnostic event "AOBRD Sensor Failure" is supported. It is raised when there is no GPS signal. The malfunctions and diagnostic events described below are applicable to the ELD version only.

Identifying Malfunctions and Required Actions (ELD Only)

The table below describes the possible malfunction codes:

Malfunction

Description

Power compliance malfunction

There has been a hardware power issue or possible tampering with the unit that is installed in your vehicle. The recorded engine on and off events do not match between the mobile device and the vehicle unit. Possibly the vehicle has been operated with the hardware unit unplugged. This issue has lasted for 30 minutes or more over a 24-hour period.

Engine synchronization compliance malfunction

The mobile device has lost connectivity to the vehicle unit for 30 minutes or more during a 24-hour period. During this time the data on engine power status, vehicle motion status, miles driven, and engine hours could not be accessed.

Timing compliance malfunction

There was a discrepancy of more than 5 minutes between the hardware unit time and mobile device time, or between mobile device time and server time. Where server time represents an accurate external UTC source.

Positioning compliance malfunction

The vehicle has traveled 5 miles without valid GPS data being obtained, and a cumulative 60 minutes over a 24 hour period has elapsed from such times. Check your GPS aerial.

Data recording compliance malfunction

The mobile device is unable to properly record required data, because insufficient storage space is available on the device. The mobile device can no longer record new events and you might lose events that have not been uploaded yet.

Data transfer compliance malfunction

The automatic data transfer check that is done once within each 24-hour period has failed 3 times consecutively. This means that you might have issues if you try to transfer your data. The most common cause for data transfer failures is missing data, such as carrier names, DOT numbers, and driver details.

 

These are the required actions for all malfunctions:

1.Note the type of malfunction and provide written notice of the malfunction to your motor carrier within 24 hours.
2.Ensure that you have an accurate record of duty status (RODS) for the current 24-hour period and the previous 7 consecutive days. This can be either in form of records from the ELD or RODS on compliant graph-grid paper. If necessary, manually reconstruct the RODS for any missing period.
3.Continue to manually prepare compliant RODS on graph-grid paper until the ELD is serviced and back in compliance.

Identifying Diagnostic Events and Required Actions (ELD Only)

The table below describes the possible diagnostic events:

Diagnostic event

Description

Power data diagnostic event

There has been a hardware issue with the unit that is installed in your vehicle. Possible causes are:

•The hardware unit has lost power during operation.
•The hardware unit has become unplugged.
•The hardware unit did not start up within 6 minutes of the engine being turned on.

If this issue leads to an aggregated in-motion driving time understatement of 30 minutes or more over a 24-hour period across all drivers using this vehicle, including unidentified drivers, a power compliance malfunction will be raised.

Engine synchronization data diagnostic event

The hardware unit has lost connectivity to the vehicle's ECM for at least 5 seconds. During this time the data on engine power status, vehicle motion status, miles driven, and engine hours could no longer be accessed. If the connection is lost for 30 minutes or more during a 24-hour period, an engine synchronization compliance malfunction will be raised.

Missing required data elements data diagnostic event

Some data for an HOS event is missing. For example, if you have been prompted for a manual location and you have not provided it.

Data transfer data diagnostic event

The automatic data transfer check has failed and now the check will be performed once within each 24-hour period. If this check fails more than 3 consecutive times, a data transfer malfunction will be raised. This means that you might have issues if you try to transfer your data. The most common cause for data transfer failures is missing data, such as carrier names, DOT numbers, and driver details.

Unidentified driving records data diagnostic event

The vehicle has had 30 minutes or more of driving within a 24-hour period that is not assigned to a driver.