> For the complete documentation index, see [llms.txt](https://help.pd1.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pd1.sg/pd-1/mileage-check.md).

# Mileage Check

Check your vehicle mileage.

Learn how PD-1 checks vehicle mileage.

## What Mileage Check does

Mileage Check compares the **current mileage you enter** with mileage stored in vehicle modules (and optionally OEM live data).

It is a **cross-module comparison**, not a full Diagnostic scan of every system.

{% hint style="info" %}
The estimate uses the **highest** mileage found in available Engine / Transmission freeze-frame data (and OEM, if you continue). Footer tip: **Based on cross-module mileage comparison.**
{% endhint %}

## Before you start

* A vehicle profile is selected in the PD-1 app
* PD-1 is plugged in and the ignition is **ON**
* PD-1 is connected to the **phone** (not only PD-Display)
* Internet is available for vehicle match and the first data package

{% hint style="warning" %}
If PD-1 is on PD-Display, switch it to the phone when prompted. Mileage Check reads modules through the app connection.
{% endhint %}

## Run a Mileage Check

{% stepper %}
{% step %}

### Open Mileage Check

Go to the **Diagnostic** tab → **Vehicle Insights** → **Mileage Check**.

You can also add **Mileage Check** as a Home **Custom Actions** shortcut.
{% endstep %}

{% step %}

### Enter current mileage

On **Enter Current Mileage**, tap **Enter**.

Type the reading from the dashboard (in **km**), then **Confirm**.

{% hint style="info" %}
This value is used for this check only. It is not saved as the vehicle’s stored mileage.
{% endhint %}
{% endstep %}

{% step %}

### Connect PD-1 (if needed)

If PD-1 is not on the phone, complete **Connect PD-1**. Confirm **Verify Vehicle Match** if asked.

On a first scan, download the **Download Data Package** (about 2–3 minutes) and keep the app open.
{% endstep %}

{% step %}

### Wait for analysis

The overview shows **Analyze Mileage Data** (about 1 minute).

The app scans Engine and Transmission, then may read freeze-frame mileage from stored fault data.
{% endstep %}

{% step %}

### Choose OEM (optional)

When you see **Continue with OEM Check?**, choose:

* **Confirm** — initialize OEM and try to read more mileage (can take longer; dashboard warnings may appear briefly)
* **Skip** — go straight to results

{% hint style="info" %}
OEM is optional. If you skip it, or OEM finds nothing, the check still finishes with module data only.
{% endhint %}
{% endstep %}
{% endstepper %}

## Understand the result

The report always shows:

* **Current Mileage** — what you entered
* **Real Mileage Estimate** — highest km found in modules / OEM, or **Not Detected**

| Result                       | Meaning                                                                                                                             |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Mileage Verified**         | Records are consistent across available modules. Your entered mileage is not lower than the highest stored reading.                 |
| **Discrepancy Detected**     | Inconsistent mileage across modules. A stored reading is **higher** than what you entered. The **Difference** row shows the gap.    |
| **Mileage Data Unavailable** | No usable mileage could be read from the vehicle. This does **not** prove the dashboard is wrong — only that nothing was retrieved. |

**Unavailable** is common if those modules have no stored DTCs with odometer freeze-frame, and OEM was skipped or empty.

## If the check cannot run

| Situation                             | What to try                                                                             |
| ------------------------------------- | --------------------------------------------------------------------------------------- |
| Stuck on **Enter Current Mileage**    | Enter a mileage greater than 0 and tap **Confirm**                                      |
| **PD-1 Not Connected**                | Connect PD-1 to the phone; ignition ON                                                  |
| **Download Data Package** placeholder | Tap **Download Now**; keep the app open                                                 |
| **Vehicle Mismatch**                  | Switch, edit, or add the vehicle that matches the VIN                                   |
| Analysis stops mid-scan               | Stay in the app; leaving stops the check                                                |
| Estimate **Not Detected**             | Try **Confirm** on OEM Check, or retry after a drive/scan that stores freeze-frame data |

## Next steps

1. [Scan & Fault Codes](/pd-1/scan-and-fault-codes.md) — inspect modules if a discrepancy appears.
2. [Live Data](/pd-1/live-data.md) — view related parameters in real time.
3. [Vehicle Health](/pd-1/vehicle-health.md) — longer-term condition after driving with PD-Display.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.pd1.sg/pd-1/mileage-check.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.