Voltmasters Platform
DSO RTU dashboard
The DSO RTU dashboard shows, in real time, how the grid operator is currently constraining your installation through its Remote Terminal Unit, and lists every command the RTU has sent.
The DSO RTU page (Monitoring → DSO RTU) shows which limits the grid operator's RTU is imposing on your installation right now, and below that the history of every signal the RTU sent.
This page only appears for projects with a DSO RTU connection. If you don't see it in the project menu, no connection is set up for that project. See DSO RTU and RTU connection.
The live snapshot
A site under a 60 % grid injection cap and a reactive band, sent for congestion.
- Restriction banner: whether the RTU is constraining the site right now, and when the snapshot was last updated.
- Status & mode: the reactive power (Q) control mode, either a local curve or one of the remote modes, and whether an emergency stop is active for production (injection) or consumption (offtake).
- Active setpoints: the limits the RTU imposes now, as a percentage of their base. 100 % means no limitation.
The snapshot shows the most recent data from the controller. If the controller has not reported recent RTU data, the page says that nothing recent has come in.
The colour of the banner
The active setpoints
| Setpoint | Meaning |
|---|---|
| Max installation production, Max installation consumption | Installation limits: the cap on the registered assets, as a percentage of the reference power the operator registered. |
| Max grid injection (NKP), Max grid offtake (NKP) | Grid limits: the cap at the grid connection point, as a percentage of the contractual access power. |
| PV production setpoint, Battery production setpoint | A cap per production type, only for operators that steer those types separately. A dash means the RTU sends none. |
| Min reactive power (Q), Max reactive power (Q) | The reactive power band, relevant in the remote Q modes. |
| Reason active power (P), Reason reactive power (Q) | Why the operator steers: Normal, Congestion or Test. |
Installation limits versus grid limits
Installation limits cap the assets themselves. Grid limits cap what flows in or out at the grid connection point. The EMS applies both, and whichever binds first limits the installation.
RTU history
The RTU history table lists what the RTU sent, newest first:
| Column | Meaning |
|---|---|
| Time | When the controller recorded the state. |
| Type | Change when a setpoint, stop or mode changed; Heartbeat for the periodic row written while nothing changed. |
| Status | Restricted when any setpoint was below 100 %, a stop was active or a reactive power order narrowed the reactive power, otherwise No restriction. A Q band from -100 % to 100 % or a cos φ of 1 imposes nothing. |
| Emergency stop | None, Production, Consumption, or both. |
| Max production, Max consumption | The asset caps in force. |
| PV setpoint, Battery setpoint | The per-type caps, for operators that use them. |
| Q mode | The reactive control mode in force. |
| Q value | The reactive power order that came with the mode: a Q band as its lower and upper bound (for example 33% to 100%), or the cos φ target. When PV and battery get a different cos φ, both are shown. Other modes show an empty marker. |
Use the Filters to show Changes only (every command, without the heartbeats) or Restrictions only. The date range defaults to the last seven days and can cover at most 31 days.
During a certification the history is the log of the inspector's commands, and the snapshot shows what is in force right now. Commissioning and certification explains what to check per test step.
Frequently asked questions
What does an emergency stop on the dashboard mean?
An active emergency stop means the grid operator has instructed the installation to immediately stop injecting (production), consuming (offtake) or both. The EMS executes this on the connected assets and drives the configured relay outputs. See Emergency stop.
Why does the history show rows while nothing changed?
Those are heartbeat rows: the controller records the state at a fixed interval so that a long period without commands is still visibly covered. Filter on Changes only to hide them.