Old or stale data from the PT30
How EZ Logs handles old events stored in a PT30 and data that stops mid-drive, so they don't turn into false driving or unidentified driving.
The PT30 stores events while no phone is connected and hands them to the app when it reconnects. That is how EZ Logs fills in driving that happened while the phone was away. Sometimes a PT30 still holds very old events, for example after sitting in a drawer for months or coming from another truck. EZ Logs protects your logs from that old data.
Old stored events are not added to the log
When the app fetches stored events from the PT30:
- Events more than 8 days old, or dated more than a day in the future (a device clock error), are not turned into log records. They don't create driving, engine power-up or unidentified driving on today's log.
- The raw data is still saved and sent to EZ Logs for the record. Nothing is deleted.
As a second safeguard, an automatic record with an implausible date is held back on the phone and never uploaded, and the EZ Logs server refuses such records too. Records you enter yourself and edits are never affected.
For admins: quarantined uploads
If a truck's ELD uploads automatic records with an implausible date, the portal shows a notification: ELD upload quarantined: implausible record time. You get at most one per vehicle and day. The records are kept aside and are not part of any driver's log. No action is usually needed. If it repeats on the same truck, check that the PT30's clock is right (it should match the app's time) and contact us.
When data stops in the middle of a drive
If the PT30 or the app stops sending vehicle data while the truck is moving (the link drops or the device goes silent), EZ Logs does not leave you in Driving forever:
- After 5 minutes without vehicle data, the app treats the truck as stopped and shows Vehicle stopped (Are you still driving?).
- If you don't answer, On duty is recorded from the time of the last data.
- The Engine synchronization data diagnostic is recorded for the gap. See No engine data.
If the Bluetooth link was lost, the app waits up to 30 minutes for the PT30's stored events before closing the drive, so real driving can still be filled in from the PT30 when it reconnects.
If your log looks wrong
- Driving you didn't do, from an old date: this should no longer happen. If you see it, don't edit it yourself. Tell your carrier so they can review it.
- Unidentified driving appears on your truck: review it under More > Edits & unidentified driving and accept only driving that was yours. See Unidentified driving.
- A drive was closed too early after a connection drop: the stored events usually fill it in after the app reconnects. If not, your carrier can propose a correction for you to approve.
Note: automatically recorded driving time cannot be shortened or changed to another status (49 CFR 395.30(c)(2)). Corrections go through the regulated edit process and keep the original record.