> 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-tyre/pairing-the-sensors.md).

# Pairing the Sensors

Pair your PD-Tyre sensors.

Pair each tyre sensor with your PD-Tyre system.

## Before you start

* Wheel sensors are installed (see [Installing PD-Tyre](/pd-tyre/installing-pd-tyre.md)).
* You noted each sensor’s **6‑character ID** and wheel position (**FL / FR / RL / RR**), if you plan to enter IDs manually.
* PD-Tyre is linked to your account and vehicle (see [Getting Started with PD-Tyre](/pd-tyre/getting-started-with-pd-tyre.md)).
* The PD-Tyre receiver box is powered on and nearby.
* Bluetooth and Location are enabled on your phone.

{% hint style="info" %}
Pairing needs a live link to PD-Tyre. If the app says **Please connect PD-Tyre first** or **TPMS box not connected**, tap **Connect TPMS** and try again.
{% endhint %}

## Connect PD-Tyre

{% stepper %}
{% step %}

### Open PD-Tyre

In **Proteus Diagnostics**, go to **Profile** → **PD-Tyre**, then open your device.
{% endstep %}

{% step %}

### Connect if needed

If the box shows disconnected, tap **Connect TPMS** and complete the Bluetooth connection.

{% hint style="info" %}
If this vehicle also uses **PD-Display**, the app may ask you to connect the display first. Live tyre data can then come through PD-Display.
{% endhint %}
{% endstep %}
{% endstepper %}

## Pair with Learn (recommended)

Use **Learn** when you want the receiver to detect the sensor on one wheel automatically.

{% stepper %}
{% step %}

### Open Sensor IDs

On the PD-Tyre detail page, open **Sensor IDs**.
{% endstep %}

{% step %}

### Choose a wheel

Tap the wheel you want to pair: **FL**, **FR**, **RL**, or **RR**.

The dialog title shows that wheel’s sensor ID (for example **FRONT LEFT**).
{% endstep %}

{% step %}

### Start Learn

Tap **Learn**.

The app listens and shows a message such as **Scan FL: trigger that tire sensor (45s)…** or **Listening FL — trigger sensor**.
{% endstep %}

{% step %}

### Trigger that wheel’s sensor only

While Learn is running, activate **only** the sensor for that wheel (use the activation method supplied with your sensors — for example a short pressure change at that valve).

Do not trigger other wheels at the same time.
{% endstep %}

{% step %}

### Confirm the ID

When Learn succeeds, the ID field fills in and you see **Learn success**.

Tap **Confirm** to write the ID to the PD-Tyre box and save it.

{% hint style="warning" %}
**Learn** detects the sensor. **Confirm** saves the binding. Always tap **Confirm** after a successful Learn.
{% endhint %}
{% endstep %}

{% step %}

### Repeat for every wheel

Repeat Learn → trigger → **Confirm** for **FR**, **RL**, and **RR**.
{% endstep %}
{% endstepper %}

## Or enter the sensor ID manually

Use this if you already recorded the 6‑character IDs from the sensor housings.

{% stepper %}
{% step %}

### Open the same Sensor IDs dialog

**Profile** → **PD-Tyre** → device → **Sensor IDs** → tap **FL / FR / RL / RR**.
{% endstep %}

{% step %}

### Enter the ID

Type the **6 hex digits** (`0–9`, `A–F`) with the on‑screen keypad, or pick an ID from history if available.

{% hint style="info" %}
If the format is wrong, the app shows **Need 6 hex digits (0-9, A-F)**.
{% endhint %}
{% endstep %}

{% step %}

### Confirm

Tap **Confirm** to bind that ID to the selected wheel.
{% endstep %}

{% step %}

### Repeat for remaining wheels

Enter and confirm the correct ID for each position.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
You can also long‑press a wheel on the Device Hub **TPMS** view to open the bind dialog and enter an ID there. For Learn with cloud save, use **Profile** → **PD-Tyre** → **Sensor IDs**.
{% endhint %}

## Check that pairing worked

{% stepper %}
{% step %}

### Review Sensor IDs

On the PD-Tyre detail page, each of **FL / FR / RL / RR** should show a 6‑character ID (not `-`).
{% endstep %}

{% step %}

### Check live data

Open **Tire Pressure Health** (or the Device Hub **TPMS** view) and confirm pressure and temperature appear for each wheel.
{% endstep %}
{% endstepper %}

## If pairing fails

| Message / issue                                               | What to try                                                                        |
| ------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **Please connect PD-Tyre first** / **TPMS box not connected** | Connect TPMS; keep the box powered and nearby                                      |
| **Bind failed, check box power**                              | Power the receiver on and reconnect                                                |
| Timeout / **no sensor heard**                                 | Retry Learn; trigger only that wheel’s sensor while scanning                       |
| **Unable to Bind Device** (at connect time)                   | Device is linked to another account — unbind it first                              |
| Sensor IDs read‑only with PD-Display                          | App may show that IDs are synced from PD-Display — edit on the display if prompted |

## Next

Review tyre pressure, temperature, and alerts in [Understanding Tyre Data](/pd-tyre/understanding-tyre-data.md).


---

# 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-tyre/pairing-the-sensors.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.