> 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/vehicle-health.md).

# Vehicle Health

Understand your vehicle health insights.

Understand the health insights for your vehicle.

## What Vehicle Health is

Vehicle Health turns real driving samples from **PD-Display** into an overall **Health Index** and theme-by-theme status (electrical, thermal, and more).

It is different from a one-off Diagnostic scan:

|             | Diagnostic scan                | Vehicle Health                      |
| ----------- | ------------------------------ | ----------------------------------- |
| Main goal   | Find and clear fault codes now | Track condition over several drives |
| Data source | PD-1 ↔ phone (live OBD scan)   | PD-Display samples → app sync       |
| Typical use | Check engine light / codes     | Ongoing health after normal driving |

{% hint style="info" %}
Vehicle Health needs a **PD-Display** linked to the same vehicle. Driving with the display connected builds the samples; the PD-1 app syncs and analyses them.
{% endhint %}

## Before you start

* A vehicle profile is selected in the PD-1 app
* PD-1 and PD-Display are set up for that vehicle
* PD-Display stays powered and connected while you drive
* Internet is available when you sync in the app

{% hint style="info" %}
Some accounts see **Vehicle Health early access** first. Tap **Apply for access** and wait until access is approved before the full dashboard unlocks.
{% endhint %}

## Open Vehicle Health and sync

{% stepper %}
{% step %}

### Open Health

In the PD-1 app, open the **Health** tab. The screen title is **Vehicle Health**.
{% endstep %}

{% step %}

### Connect PD-Display (if needed)

If you see **Connect PD-Display**, complete display setup and bind the same vehicle used in the app.
{% endstep %}

{% step %}

### Drive with PD-Display connected

Use the car normally. PD-Display collects samples in the background.
{% endstep %}

{% step %}

### Sync with PD-Display

Tap **Sync** or **Sync with PD-Display**.

The app shows **AI Health Analysis** while it uploads samples and updates your assessment.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The vehicle on PD-Display must match the vehicle selected in the app. If they differ, switch or rebind before syncing.
{% endhint %}

## Vehicle Health Journey

Until enough driving samples are collected, you will see **Vehicle Health Journey**.

Progress is based on **effective collection days** (useful drives that produce samples), not only calendar days.

Typical unlock path (petrol / hybrid):

1. Current operating readings
2. 12V battery & charging check
3. Cooling & warm-up assessment
4. Fuel mixture & combustion status
5. Core systems cross-check
6. Repeat-condition verification
7. **Vehicle Health Index**

EV journeys use EV-focused steps (for example 12V system voltage and thermal-loop checks) instead of combustion.

When the journey is complete, the **Health Index** becomes available. Keep PD-Display connected and sync regularly so the index stays fresh.

## Health Index

The **Health Index** is a 0–100 score from recent analysis (about a **7-day window**).

| Pill                  | Meaning                                             |
| --------------------- | --------------------------------------------------- |
| **Not Enough Data**   | Journey not complete, or samples are still building |
| **In good condition** | Latest analysis looks healthy overall               |
| **Needs Attention**   | At least one theme needs a closer look              |
| **Elevated Risk**     | One or more themes show elevated risk               |

You may also see:

* **Primary constraint: {theme}** — the theme most limiting the index
* **Index +N / −N since last sync** — how the score moved after a sync
* **Looking good overall** — no active concerns from the latest analysis
* **Worth a look** + **Review {theme}** — open the theme that needs attention

If analysis is stale, the app may show **Sync to refresh analysis**, **Analysis is N days old**, or **Needs PD-Display sync**.

## Themes

Tap a theme card for charts, verdict, and next steps.

### Petrol / hybrid

| Theme               | What it reflects                        |
| ------------------- | --------------------------------------- |
| **Electrical**      | Charging / 12V behaviour while driving  |
| **Thermal**         | Coolant temperature after warm-up       |
| **Combustion**      | Fuel trim / mixture stability           |
| **Fault Status**    | Fault signals that may need a code scan |
| **Usage Intensity** | How hard the vehicle is being driven    |
| **Trip**            | Mileage and runtime context             |

### EV

| Theme                 | What it reflects                                               |
| --------------------- | -------------------------------------------------------------- |
| **Electrical**        | 12V system / pack health signals (as available)                |
| **Thermal**           | Thermal-loop temperature                                       |
| **Electrical Alerts** | DC-DC / 12V-style alerts (instead of classic MIL fault status) |
| **Driving Intensity** | High-demand driving share                                      |
| **Trip**              | Mileage and runtime context                                    |

Combustion is usually not shown for pure EV.

## Status colours

| Status              | Meaning                                                     |
| ------------------- | ----------------------------------------------------------- |
| **Normal**          | Within a healthy band for that theme                        |
| **Needs attention** | Outside the normal band — review and follow next steps      |
| **Risk**            | Higher concern — act sooner; consider a shop if it persists |
| **Calibrating**     | Not enough valid samples yet for a firm verdict             |

{% hint style="info" %}
Short spikes alone usually do not set status. The analysis looks for sustained patterns across valid PD-Display samples.
{% endhint %}

## What to do next

On a theme in **Needs attention** or **Risk**, open **What to do next**.

Common in-app checklists:

* **Check charging while driving**
* **Check coolant on a warm drive**
* **Check 12V while driving** (EV)
* **Check thermal loop on a drive** (EV)
* **Follow the quick check**

Typical pattern:

1. Drive normally for about 15–20 minutes
2. Keep PD-Display connected
3. Sync after the drive
4. Recheck the theme

You may also see **Find a nearby shop** or a **Related service** reminder. Theme detail also includes **How we measure** for how that check works.

| Footer                                | Meaning                                               |
| ------------------------------------- | ----------------------------------------------------- |
| **No action needed.**                 | Latest verdict looks fine                             |
| **Re-sync to confirm.**               | Refresh samples before deciding                       |
| **Looked normal when last analyzed.** | Last result was normal; sync again for a current view |

## Tips

1. Sync after several normal drives — one short trip is often not enough.
2. For thermal checks, judge after the engine (or thermal loop) is fully warm.
3. If **Fault Status** / **Electrical Alerts** points to an active fault, also run a Diagnostic scan (see [Scan & Fault Codes](/pd-1/scan-and-fault-codes.md)).
4. If the index falls after a sync, open the highlighted theme first.

## Next steps

1. [Live Data](/pd-1/live-data.md) — watch related sensors in real time.
2. [Scan & Fault Codes](/pd-1/scan-and-fault-codes.md) — investigate active fault signals.
3. [Getting Started with PD-Display](/pd-display/getting-started-with-pd-display.md) — if the display is not set up yet.


---

# 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/vehicle-health.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.