Error Codes Explained
Error Code 1: Power data diagnostic error
How is it triggered?
This diagnostic code indicates a problem with the initialization of the device. This is caused by faulty HW or a glitch in the memory system during the initialization stage (when the LED is red for 90 seconds)
How to clear it?
Disconnect and Connect the device again, forcing a re-initialization
Things to Check/Verify
Check if the connection of the device and the truck is solid, and that the battery of the truck is fine. If the problem persists replace the device.
Error Code 2: Engine synchronization data diagnostic error
How is it triggered?
This code indicates that the vehicle is moving without a correct data connection to the truck engine (CAN/J1708). The movement is detected by the internal accelerometer in the EZ-ELD device.
How to clear it?
This Diagnostic code is cleared when the data connection with the truck is re-established
Things to Check/Verify
Check engine gauges and the LED of the device to make sure that the vehicle is compatible with the device. Two blinks on the LED indicates that the device is not able to establish communications with the vehicle.
Check if the engine gauges are updating correctly, and in regular intervals, without jumps and if the data matches the vehicle instruments
Check that the device is firmly locked on the diag. connector or well fixed on the truck dashboard. Make sure the vehicle is not parked near sources of vibration which can cause false accelerometer reads.
Error Code 3: Missing required data elements data diagnostic error
How is it triggered?
This code indicates that mandatory data is unavailable during the HOS event recording. Examples: odometer, GPS information, Engine hours etc. It can be caused by poor GPS signal, missing data on the CAN bus and by using the ”no device’ mode to adjust the logs, as engine data is not available without a device connected.
How to clear it?
It is disabled automatically when the data becomes available again.
Things to Check/Verify
Verify if GPS is working properly (Track and Trace can be used for that); reposition the device with the extension cable for better sensitivity and check the LED: 1 blink indicates no GPS signal, two blinks indicate no CAN connection.
Error Code 4: Data transfer data diagnostic error
How is it triggered?
The Data transfer data diagnostic error will be logged during the login process when our app is connected to the internet but can’t reach our ELD servers.
How to clear it?
This error will be cleared when your ELD can reach our central ELD servers during the next login process.
Things to Check/Verify
This issue occurs when the phone indicates a valid internet connection but the internet is not functioning. This can happen when the data plan was fully consumed, is expired or not responding. It can also happen if the EZ-ELD servers are not functioning.
Things to try: use airplane mode to force the App into offline operation, connect to Wifi, test the web browser of the phone to verify the internet is working.
Error Code 5: Unidentified driving records data diagnostic error
How is it triggered?
The Unidentified driving records data diagnostic error will be logged when the current vehicle has more than 30 minutes of driving time under the unidentified driver profile.
How to clear it?
The Unidentified driving records data diagnostic error will be cleared when the current vehicle has less than 15 minutes of driving time under the unidentified driver profile.
Things to Check/Verify
The user needs to assume Unidentified Events until less than 15 minutes worth of them remain. After that log out and log in again.
To assume events under the unidentified driver profile: In the App, go to “Previous Logs” and tap on the “Unidentified” tab. On this section, you will be able to see all events under the unidentified driver profile for the current vehicle. Tap the “check” icon to assume its respecitve event record (Internet connection required).
Error Code 6: Other ELD identified diagnostic error
How is it triggered?
Not caused by the EZ ELD system. It’s simply a provision of the law for additional Manufacturer specific / custom error codes.