Review Saved OBD2 Diagnostic Reports

Reports you can revisit

OBD CAN can save completed reports from supported diagnostic and vehicle tests. Depending on the test, a report may include fault-code results, vehicle information, monitor status, sensor or test values, and the timestamp. Examples include OBD2 scans, UDS module scans, emissions prechecks, readiness and supported Mode 05/06 checks, battery tests, acceleration tests, oxygen-sensor tests, and noise reports. A history screen is offered by the relevant test page; not every live screen or every activity automatically creates a report.

Open a report after a test

1. Sign in before opening a test’s saved-history view. The history action is available from report-capable test pages.
2. Run a supported check while connected to a compatible BLE OBD2 adapter, and wait for the app to finish and save its report.
3. Return to the same test area and tap its history control. Reports are listed by test type and date; scroll down to load older entries.
4. Open a report to review its saved contents. Select records using the history screen’s selection controls and confirm before deleting them.

Saved report details are snapshots from the time of that test. Reopening a report displays recorded results; it does not reconnect to the car, refresh live values, or rerun the diagnostic.

Example: preserve an intermittent fault

Suppose an engine warning appears briefly, then disappears before a workshop visit. While connected and when safe, run the relevant scan, save its report with the date and codes, and reopen it from that test’s history later. Export or copy the available report details to share with a repair professional, then ask them to compare it with current symptoms and vehicle tests. A saved code does not prove the fault is still active, identify its cause, or establish that the vehicle is safe to drive.

How to read results

Check the test name, vehicle/module context, timestamp, and any incomplete status. A missing result is not a normal result. Vehicle support, module responses, adapter behavior, and protocol differences affect the report. Clearing a code does not repair its cause; readiness does not guarantee an emissions inspection pass.

Where history is stored

Reports are local files stored on the device by account. Sign-in is required to open history, but reviewing a saved report needs no vehicle connection. Reports are not cloud-synchronized and will not appear on another device just because you sign in there. Retain the device and app data to keep them.

Frequently asked questions

Can I read a saved report without the adapter?

Yes. Once saved, a report can be reviewed without connecting to the vehicle, but the history view requires sign-in.

Why is a report missing?

The test may not save that report type, the test may not have completed or saved successfully, or you may be signed into a different account. Check the relevant test’s history and account.

Will a report follow me to another phone?

No. History is local and not cloud-synchronized.