> 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/live-data.md).

# Live Data

View real-time vehicle data.

View and understand your vehicle's live data.

## What Live Data is

**Live Data** shows real-time values from your vehicle through PD-1 — for example RPM, temperatures, voltages, and other PIDs.

There are two tabs:

| Tab                   | What it is                                                           |
| --------------------- | -------------------------------------------------------------------- |
| **Live Data** (Basic) | Standardized basic diagnostic data available on most vehicles        |
| **OEM Live Data**     | Manufacturer-specific advanced data — more detailed, model-dependent |

{% hint style="info" %}
Start with **Basic Live Data**. Use **OEM Live Data** when Basic cannot be read, or when a feature needs OEM parameters. You can initialize OEM later from **Settings → Toolbox**.
{% endhint %}

## Before you start

* PD-1 is plugged in and the ignition is **ON**
* PD-1 is connected to the **phone** (Mobile App), not only to PD-Display
* A vehicle profile is selected
* Bluetooth and Location are enabled

{% hint style="warning" %}
PD-1 can only connect to one host at a time. If it is on PD-Display, switch it to the phone before using Live Data Panel.
{% endhint %}

## Open Live Data

{% stepper %}
{% step %}

### Go to Home

Open the **Home** tab in the PD-1 app.
{% endstep %}

{% step %}

### Open Live Data Panel

Tap **Live Data Panel** (shown when PD-1 is connected or vehicle data is available).
{% endstep %}

{% step %}

### Choose a tab

Use **Live Data** for Basic parameters, or **OEM Live Data** for OEM parameters.
{% endstep %}
{% endstepper %}

Optional: from the ⋮ menu open **PD-Display Dashboard** to view skins/widgets (when you have access).

## Initialize and scan

### Basic Live Data

{% stepper %}
{% step %}

### Initialize

If you see **Initialize Basic Data to start monitoring**, tap **Start**.

Wait for **LiveData initialized successfully.**
{% endstep %}

{% step %}

### Scan (optional but useful)

Run **Scan Basic Live Data** from **Settings → Toolbox**, or during Getting Started.

Scanning discovers available parameters and supports features that need a Basic data source (for example some display templates).
{% endstep %}
{% endstepper %}

### OEM Live Data

{% stepper %}
{% step %}

### Download the vehicle data package

OEM needs a vehicle database. Use **Download Vehicle Data Package** in **Settings → Toolbox** if you have not already.
{% endstep %}

{% step %}

### Read the Important Notice

The first OEM init shows **Important Notice**: reading OEM data may temporarily light dashboard warnings. Tap **Continue** only if you accept that risk.
{% endstep %}

{% step %}

### Initialize OEM

On the OEM tab, tap **Start** if you see **Initialize OEM Data to start monitoring**.

Wait for **OEMLiveData initialized successfully.**
{% endstep %}

{% step %}

### First OEM scan

The first OEM scan may show **First OEM Scan Required** — downloading and processing a large package (can take much longer than Basic; later scans are faster). Keep the app open.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Redo init or scan anytime from **Settings → Toolbox**: Initialize basic / OEM live data, Scan Basic / OEM Live Data, Download Vehicle Data Package.
{% endhint %}

## Use the Live Data grid

{% stepper %}
{% step %}

### Watch live values

Each tile shows a parameter name, value, and unit. Values update while PD-1 stays connected.
{% endstep %}

{% step %}

### Change layout size

Toggle **Large** (fewer, bigger tiles) or **Small** (denser grid).
{% endstep %}

{% step %}

### Edit parameters

Long-press the grid (tip: **This is a data sample, long press to edit parameters...**):

1. Remove tiles you do not need
2. Tap **+** / **Add Data** to open **Select Data**
3. Search and select parameters, then confirm
4. Drag to reorder while editing
   {% endstep %}

{% step %}

### Set warnings (optional)

Open ⋮ → **Live Data warning setting**.

Set **Min** / **Max** (and related fields) so out-of-range tiles can highlight in red.
{% endstep %}
{% endstepper %}

On **OEM Live Data**, if the grid is empty you will see **No OEM Data Added** — tap **Add Data** to pick OEM parameters.

## Live Data AI Analysis (Basic tab)

On the Basic tab, ⋮ → **Live Data AI Analysis**:

1. Tap **Start Recording** to capture screen data while values update
2. Drive or run the vehicle as needed
3. Stop recording and open the **Data Report** from history when available

{% hint style="info" %}
AI Analysis needs PD-1 connected to the phone. It is available from the Basic Live Data menu, not the OEM tab.
{% endhint %}

## Phone vs PD-Display

| Goal                            | What to do                                                                                                            |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| View Live Data in the app       | Connect PD-1 to **Mobile App**, open **Live Data Panel**                                                              |
| View gauges on the screen       | Switch PD-1 to **PD-Display** (see [Getting Started with PD-Display](/pd-display/getting-started-with-pd-display.md)) |
| Use in-app PD-Display Dashboard | Open ⋮ → **PD-Display Dashboard**; connect PD-1 to the phone if prompted                                              |

If you see **Connect PD1 to view live data**, reconnect PD-1 to the phone.

## If Live Data will not start

| Situation                    | What to try                                                          |
| ---------------------------- | -------------------------------------------------------------------- |
| **PD-1 Not Connected**       | Tap **Connect PD-1**; ignition ON; green blinking light              |
| Connected to PD-Display only | **Switch Connection** to Mobile App                                  |
| Basic empty / not monitoring | Initialize Basic Data, then add parameters                           |
| OEM blocked / empty          | Download vehicle package → accept notice → Initialize OEM → Add Data |
| First OEM very slow          | Keep app open; allow the large package download to finish            |
| Values freeze / disconnect   | Stay near the device; reconnect PD-1; avoid leaving mid-init         |
| Need a clean redo            | **Settings → Toolbox** — clear/download package, re-init, re-scan    |

## Next steps

1. [Scan & Fault Codes](/pd-1/scan-and-fault-codes.md) — diagnose stored faults.
2. [Vehicle Health](/pd-1/vehicle-health.md) — longer-term insights from PD-Display driving samples.
3. [Getting Started with PD-Display](/pd-display/getting-started-with-pd-display.md) — show live gauges on the screen.


---

# 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/live-data.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.