> 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/getting-started-with-pd-1.md).

# Getting Started with PD-1

Set up and connect your PD-1 device.

Set up your PD-1 device and connect the app.

## What you need

* **PD-1** OBD‑II dongle
* Compatible vehicle with an accessible OBD‑II port
* Smartphone with Bluetooth and Location Services
* **PD-1** app (App Store / Google Play, or [pd1.sg/download](https://www.pd1.sg/download))
* Internet connection (for account login, firmware, and vehicle data packages)

{% hint style="info" %}
PD-1 plugs into the vehicle’s OBD‑II port and connects to the PD-1 app over Bluetooth. When searching, the indicator light should **blink green**.
{% endhint %}

## Install PD-1 in the vehicle

Follow the in-app **Plug Guide**, or these steps:

{% stepper %}
{% step %}

### Turn off the ignition

Do not insert or remove PD-1 while the ignition is on or the engine is running.
{% endstep %}

{% step %}

### Locate the OBD‑II port

Open the driver’s side area and find the OBD port. It is usually below the steering wheel, near the driver’s seat.
{% endstep %}

{% step %}

### Insert PD-1

The OBD port is trapezoid-shaped — match the plug orientation and push PD-1 in firmly.
{% endstep %}

{% step %}

### Turn the ignition ON

Turn the key (or power) to **ON** so PD-1 can talk to the vehicle ECU.

Wait for the indicator to **blink green** — Bluetooth is ready.
{% endstep %}
{% endstepper %}

## Set up the app and connect

{% stepper %}
{% step %}

### Install and open the PD-1 app

Install the PD-1 app, then **Sign Up** or **Log In**.
{% endstep %}

{% step %}

### Enable Bluetooth and Location

Turn on Bluetooth and Location Services. The app needs Location to scan for Bluetooth devices.
{% endstep %}

{% step %}

### Connect PD-1

On Home (or **Profile** → **My OBD**), tap **Connect PD-1**.

On **Waiting to connect with PD-1**, search starts automatically — or tap **Search Device**.
{% endstep %}

{% step %}

### Select your device and connect

When your PD-1 appears, check the serial number (SN), then tap **Connect**.

Wait for **Connected Success!** / **PD-1 connected successfully!**

{% hint style="info" %}
Keep the phone close to the device. If nothing appears, confirm the green blinking light and tap **Scan** again.
{% endhint %}
{% endstep %}

{% step %}

### Upgrade if prompted

If you see **Hardware Upgrade Detected**, tap **Upgrade Now** / **Start Upgrade**.

{% hint style="warning" %}
Keep the app open, keep the engine running, and do not unplug PD-1 until the upgrade finishes (about 3–5 minutes).
{% endhint %}
{% endstep %}

{% step %}

### Add your vehicle

If you do not have a vehicle yet, create one after connect:

1. Enter **VIN / Chassis No.** (PD-1 may auto-read the VIN), or fill brand, model, and other details manually.
2. For a standard VIN, use 17 characters. Some Japanese domestic cars use a chassis number (for example `XXX-XXXXXX`).
3. If you are unsure, you can enter seventeen `0`s and select the model manually later.

{% hint style="info" %}
If VIN is not detected, choose the vehicle model manually when prompted.
{% endhint %}
{% endstep %}
{% endstepper %}

## Download data and run your first scan

{% stepper %}
{% step %}

### Open Diagnostics

Go to the **Diagnostics** page.
{% endstep %}

{% step %}

### Download the vehicle data package (first time)

On the first scan, the app may ask you to **Download Data Package** (about 2–3 minutes). Tap **Download Now** and keep the app open.
{% endstep %}

{% step %}

### Start Scan

Tap **Start Scan** and wait for the scan to finish.

When it completes, you can review fault codes, vehicle health, and other insights.
{% endstep %}
{% endstepper %}

## Optional: full Getting Started checklist in the app

For a guided end-to-end setup (connect → update → vehicle database → live data → optional PD-Display):

1. Open **Settings** → **Getting Started**, or
2. Log in with your PD-1 **Serial Number** to open Getting Started automatically.

You can skip PD-Display setup if you only use the phone for now.

## Next steps

1. [Scan & Fault Codes](/pd-1/scan-and-fault-codes.md) — diagnose your vehicle.
2. [Vehicle Health](/pd-1/vehicle-health.md) and [Live Data](/pd-1/live-data.md) — monitor ongoing condition.
3. Optionally set up [PD-Display](/pd-display/getting-started-with-pd-display.md).

Or follow the shorter flow in [PD-1 Quick Start](/getting-started/pd-1-quick-start.md).

{% hint style="info" %}
To revisit the in-app checklist later: **Settings** → **Getting Started**.
{% endhint %}


---

# 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/getting-started-with-pd-1.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.
