No engine data (engine synchronization)

What to do when the PT30 is connected but no engine data arrives, and how the engine synchronization diagnostic and malfunction E work.

For drivers and admins · Español

The ELD rule requires engine data (engine on or off, vehicle miles, engine hours, speed) to come from the truck's engine computer. The PT30 reads it from the diagnostic port and sends it to the app. If that data stops arriving while the engine is running, EZ Logs records an engine synchronization problem.

What you see

On the ELD tab:

• Connected · receiving engine data: everything is working.
• Waiting for data: the app is connected to the PT30 but has not received engine data yet. This is normal for a short time after connecting or with the engine off.

If engine data is missing while the engine is on, the status bar at the top of the app shows:

• Engine synchronization data diagnostic · you can keep driving: a data diagnostic (code 2). The app explains: Engine data from the ELD device was late. Check the device connection.
• ELD malfunction: Engine synchronization compliance · keep paper logs: a malfunction (code E). This happens when engine data has been missing for more than 30 minutes in total within 24 hours.

Fix it

1. Make sure the engine is running. With the engine off there is no engine data to send.
2. Check that the PT30 is plugged firmly into the diagnostic port. A loose connector is the most common cause.
3. On the ELD tab, check that the PT30 is connected. If not, see The PT30 won't connect.
4. If the PT30 was moved between trucks, unplug it, wait a few seconds, plug it back in and reconnect.

The diagnostic clears by itself when engine data arrives again, or when the engine is turned off. The malfunction clears the same way once engine data is back.

If you lose the connection while driving

If no vehicle data arrives for 5 minutes while the truck was moving, the app no longer keeps you in Driving. It shows Vehicle stopped (Are you still driving?) and, if you don't answer, records On duty from the time of the last data. It also records the engine synchronization diagnostic. If the Bluetooth link was lost, the app first waits up to 30 minutes for the PT30's stored events, so the real driving time can still be filled in when it reconnects.

Malfunction E: what to do

A malfunction means the ELD can't record reliably. Follow What to do now in the app:

1. Tell your carrier in writing within 24 hours (you can use Message dispatch).
2. Keep paper logs for today: use a graph-grid log until the ELD is fixed.
3. Have the previous 7 days ready for an inspector (Show 7 days).

Your carrier must repair or replace the ELD within 8 days (49 CFR 395.34). See ELD malfunctions.

For admins

• If the alerts feature is part of your account, an ELD malfunction / diagnostic alert rule can notify you.
• Repeated engine synchronization problems on one truck usually mean a faulty PT30 or diagnostic port. Swap the PT30 and check Drivers & fleet > ELD devices.