> 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-display/setting-up-your-dashboard.md).

# Setting Up Your Dashboard

Configure your PD-Display dashboard.

Configure your dashboard to show the data you need.

## Choose a template (in the app)

1. Open **Proteus Diagnostics**.
2. Go to the **PD-Display** tab.
3. Open **Dashboard**.
4. Select a dashboard / add a template (for example, Minimal Style Template 6).

## Arrange widgets

* **Long-press and drag** widgets on your phone — the physical PD-Display updates in real time.

## Change a sensor

1. Select a widget.
2. Tap the **edit (pencil)** icon.
3. Choose the data sensor you want (for example, Lambda B1S1).
4. Tap **Save** at the top of the screen.

{% hint style="danger" %}
Changes are not permanent until you tap **Save**.
{% endhint %}

## Adjust on the display itself

You can also customise directly on PD-Display:

* **Long-press** to adjust data position or select data.
* Use **more options** to change the data sensor for a widget.

## Optional grid layout

Long-press on the display to set up a grid layout and rearrange gauges as needed.


---

# 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-display/setting-up-your-dashboard.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.