> For the complete documentation index, see [llms.txt](https://docs.voltmasters.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voltmasters.io/dso-rtu/dashboard.md).

# DSO RTU dashboard

The **DSO RTU** dashboard shows the latest constraint snapshot the grid operator's Remote Terminal Unit (RTU) is applying to your installation: whether the site is currently restricted, which active- and reactive-power limits are in force, and whether an emergency stop is active.

{% hint style="info" %}
This dashboard is only available for projects that have a DSO RTU connection configured. If you don't see it in the project menu, no DSO RTU is configured for that project.
{% endhint %}

### What this dashboard shows

* **Restriction banner**: a clear status banner at the top tells you whether the RTU is currently constraining the site (an active emergency stop, a sub-100% power cap, or a non-normal reason code) or whether there is no active restriction. The banner also shows when the snapshot was last updated.
* **Status & mode**: the reactive-power (Q) control mode (local curve or remote setpoint) and whether an emergency stop is active for production (injection) and for consumption (offtake).
* **Active setpoints**: the limits currently imposed by the RTU, expressed as a percentage of their base power (100% means "no limit"):
  * **Max asset production / consumption** — caps relative to the installed asset power.
  * **Max grid injection / offtake (NKP)** — caps at the grid connection point.
  * **Min / max reactive power (Q)** — the reactive-power band.
  * **Reason (P) and Reason (Q)** — why active and reactive power are being constrained (Normal, Congestion or Test).

{% hint style="info" %}
The dashboard reflects the most recent data received from the RTU. When the controller has not reported recent RTU data, the dashboard shows that no recent data has been received.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/shCB31ZapVUo8S7aamiR" alt="Voltmasters EMS: DSO RTU dashboard"><figcaption><p>Voltmasters EMS: DSO RTU dashboard</p></figcaption></figure></div>

### Frequently asked questions

<details>

<summary><strong>Why don't I see the DSO RTU dashboard for my project?</strong></summary>

The dashboard only appears when a DSO RTU connection is configured for the project. If no connection is configured, the menu item is hidden. See [Overview](/dso-rtu/telecontrole.md) and [RTU connection](/dso-rtu/rtu-connection.md) for how the connection is set up.

</details>

<details>

<summary><strong>What does the restriction banner mean?</strong></summary>

The banner summarises whether the RTU is currently constraining the site. It turns red when an emergency stop is active, orange when a power limit or non-normal reason code applies, and green when there is no active restriction.

</details>

<details>

<summary><strong>What is the difference between asset limits and grid (NKP) limits?</strong></summary>

Asset limits cap power as a percentage of the installed asset power, while grid (NKP) limits cap injection or offtake at the grid connection point. The Voltmasters EMS applies the most restrictive of the two.

</details>

<details>

<summary><strong>What does an emergency stop on the dashboard mean?</strong></summary>

An active emergency stop means the grid operator has instructed the installation to stop injecting (production) and/or consuming (offtake) immediately. The EMS executes this on the connected assets. See [IO module emergency stop](/dso-rtu/io-module-emergency-stop.md) for how emergency stops are wired and triggered.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.voltmasters.io/dso-rtu/dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.