> 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/library-blocks-reference/network-tools/signal-monitoring_pas-ds-la-lib.md).

# Monitor

## Description

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

The **Monitor** block, located in the **Network Tools** library, monitors signal values at a low refresh rate. It supports two display modes: a digital display showing the current value, and an LED indicator that is green when the value is within thresholds and red otherwise.

{% hint style="danger" %}

### **Compatibility with older versions**

Using monitors displayed as LED in versions older than 2021.3 may cause a crash of the HyperWorks process. Workaround: deactivate the option in the new version, save the model, then reopen it in the older version.
{% endhint %}

The API may help editing multiple monitors at the same time:

{% code overflow="wrap" lineNumbers="true" %}

```python
HyWorksApi.setComponentParameter("Mon1", "led", "false")
```

{% endcode %}

## Mask parameters

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

<table data-search="false"><thead><tr><th width="200">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Title</strong></td><td>Name of the value displayed in the schematic.</td></tr><tr><td><strong>Expression</strong></td><td><p>Expression to monitor.</p><ul><li><p>To monitor a signal use the following syntax:</p><ul><li><em>bloc_name.signal_name:</em> BUS1.Va</li><li><em>subsystem_name.bloc_name.signal_name:</em> Machnies.SM1.Pref</li></ul></li><li>Basic mathematical operations are supported.</li><li>Operations on multiple signals are supported, for example: <em>bloc_name1.signal1</em> + (<em>bloc_name2.signal_name</em>)*2</li><li>Unlike expressions in other components, no “=” is required at the beginning.</li></ul></td></tr><tr><td><strong>Unit</strong></td><td>Unit of the value displayed in the schematic.</td></tr><tr><td><strong>Result displayed as</strong></td><td><p>Filters the value displayed, in addition to the expression:</p><ul><li><strong>last</strong>: Last value obtained from the simulation</li><li><strong>rms</strong>: RMS value of the signal</li><li><strong>avg</strong>: Average value of the signal</li><li><strong>min</strong>: Minimum value of the signal</li><li><strong>max</strong>: Maximum value of the signal</li></ul></td></tr><tr><td><strong>Minimum threshold</strong></td><td>In the Monitoring Overview GUI, the scope and table become red when the value is out of range.</td></tr><tr><td><strong>Maximum threshold</strong></td><td>In the Monitoring Overview GUI, the scope and table become red when the value is out of range.</td></tr><tr><td><strong>Hide value and unit</strong></td><td>Hides the value and unit in the schematic for a lighter LED-style display.</td></tr><tr><td><strong>Display as LED</strong></td><td>Replaces the image in the schematic with a fillable circle.</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.


---

# 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/library-blocks-reference/network-tools/signal-monitoring_pas-ds-la-lib.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.
