> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/simulation-control-monitoring-and-logging/use-hypersim-built-in-tools/monitor-signals-directly-in-the-schematic.md).

# Monitor Signals Directly in the Schematic

## Overview

The [**Monitor**](https://www.opal-rt.com/docs/hypersim/library-blocks-reference/network-tools/signal-monitoring_pas-ds-la-lib.md) block, located in the Network Tools Library, is a widget that lets you observe signal values at a low refresh rate, directly within the schematic. It supports two display modes:

* **Numeric display** — shows the current signal value
* **LED display** — a green circle if the value is within thresholds, red otherwise

## Example implementation

Let's start with the [HVAC\_500kV\_6Bus example](https://www.opal-rt.com/docs/hypersim/examples/transmission/hvac-500kv-6bus.md) model. We will add three **Monitor** blocks and configure them to display:

* The RMS voltage of **phase A** at **bus WES0**
* The RMS voltage of **phase A** at **bus WES7**
* The RMS current of **phase A** flowing through the **Di1 circuit breaker**.

{% stepper %}
{% step %}

### Add and configure Monitor blocks

Add a **Monitor** block to the schematic, then double-click the block to open its parameter dialog box. In the **Expression** field, enter the signal reference using the following syntax:

block\_name.signal\_name

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8e767d01a4bc4c82074f81963e2aee42a496788f%2Fmonitor-block-paramters-example.png?alt=media" alt="" width="505"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Start the simulation and the monitoring

Start the simulation, then in the HYPERSIM ribbon, click on **Start Monitoring**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8248f8fdde77cacb13f29869602d973f7a09230c%2Fmonitoring-menu.png?alt=media" alt=""><figcaption></figcaption></figure>

The RMS voltage value is updated each time the acquisition is triggered.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3b32aff9c52bcf86f8e6cd63266a1224434c3088%2Fmonitor-block-display.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
This functionality triggers periodic micro-acquisitions with a duration of **0.033 seconds** (two cycles at 60 Hz) every **0.5 seconds**. Depending on the number of signals being acquired, enabling this feature may affect real-time simulation performance.
{% 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://www.opal-rt.com/docs/hypersim/simulation-control-monitoring-and-logging/use-hypersim-built-in-tools/monitor-signals-directly-in-the-schematic.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.
