Malfunctions and Data Diagnostic Events are recorded and indicated by the respective icons shown below and in the Driver Overview screen. In order to review the current status go to “Inspection/More” then to “Settings” and “Diagnostic” and “Diagnostic Events”.
Occasionally the customer will notice those icons in the upper right corner of the RoadLog device main screen.
(The color of the icons will depend on a software version).
The RoadLog ELD is required by ELD rule to monitor the function of the vehicle engine computer and the integrity of the data that it captures.
Any time there are even very minor deviations between RoadLog and the vehicle ECM, RoadLog discovers and logs those occurrences. In most of cases there is nothing to worry about, but if you notice adverse operation of the RoadLog device, those recorded events work as a baseline for the troubleshooting activities.
The list of possible malfunctions may include:
| Engine Synchronization Compliance Malfunction | ECMFail |
| Timing Compliance Malfunction | TimeFail |
| Positioning Compliance Malfunction | PositionFail |
| Data recording Compliance Malfunction | RECFail |
| Other ELD Detected Malfunction | MEMFail |
| Data transfer malfunction for the USB interface | USBFail |
| Data transfer malfunction for the Bluetooth interface | BTError |
| Power Data Diagnostic Event | PowerError |
| Engine Synchronization Data Diagnostic | ECMError |
| Missing Required Data Elements Data Diagnostic | ElemError |
| Data transfer diagnostic event for the USB interface | USBError |
| Data transfer diagnostic event for the Bluetooth interface | BTError |
| Unidentified Driving Records Data Diagnostic Event | UDAError |
| USB Communication Error Self-Diagnostic | EXTERR |
| USB Unknown File System Self-Diagnostic | FATERR |
| USB Unknown Class Self-Diagnostic | CLSERR |
Note that those notifications cannot be disabled as per ELD rule.
What to do when you notice the above icons as per § 395.22
First, look at your driver logs and make sure that all the data was recorded correctly as it happened. The recommended method is to print out last few days and notice if all the data is correctly shown on a graph grid.
Should you notice no impact on the data recorded and no impact on driver logs please continue to use RoadLog as normal.
It is important for Solo customers to immediately sync the Driver Key via the RoadLog Sync App so that all the data is transferred to the portal. Otherwise there is nothing to report.
In rare cases the driver may see that the malfunction or data diagnostic event recorded does impact the accuracy of their logs.
Examples of such cases might include times when the location of duty status change is no longer recorded (bad GPS, PositionFail) or, the device is not recording the driving time properly (engine synchronization, ECMFail).
In cases where the drivers logs are not correctly recorded by RoadLog, Please follow the guidelines below:
- Continue using RoadLog to the maximum extent possible
- Comply with § 395.34 (1), (2), and (3):
- (1). Notify the motor carrier within 24 hours
- (2). Reconstruct on paper or correct any incorrect logs within RoadLog
- (3). Continue logging on paper per § 395.8. Note that any logs printed from RoadLog which are correct can be considered to be compliant under § 395.8.
- Contact VDO tech support for assistance. VDO tech support is available at 855-ROADLOG
- Additional requirements for the Motor Carrier may be required, pursuant to § 395.34 (d)
For most up to date information on reporting and handling malfunctions and data diagnostics events please visit
https://www.fmcsa.dot.gov/hours-service/elds/electronic-logging-devices
And
