> 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/pe-add-on-simulink/model-and-simulation/add-and-configure-a-circuit-model-to-the-system-definition/measurements-section.md).

# Measurements Section

## Overview

Measurements are the output signals of the circuit model. They represent either a current or a voltage measurement and can be mapped to other components such as analog output channels, custom device channels, machines, waveforms, and more. In an electrical circuit diagram, it is recommended (but not necessary) to denote the measurements of the model with the *YXX* prefix as seen in the circuit model diagram below.

See [**Supported Circuit Editors**](https://www.opal-rt.com/docs/pe-add-on-simulink/appendix/supported-circuit-editors.md) for a list of supported Measurement components in the circuit model.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FU2zln4Q0W1uwdpjlmvbX%2Fb2a1c2f9-1ae4-4850-be28-ef16973525a3.png?alt=media&amp;token=5fea1f45-a3d6-4234-b77c-4209fb12a970" alt=""><figcaption></figcaption></figure>

## Measurements Configuration Page

In the **System Explorer** window configuration tree, expand the **Power Electronics Add-On** custom device and select **Circuit Model >> Measurements** to display this page.

After a model is successfully loaded in the **Circuit Model Section**, this page is added to the configuration tree and populated with a named list of the **Measurement** components found in the circuit model (as seen in Measurements Description).

### **Measurements Settings**

For each Measurement, the following information is available. No settings or parameters can be configured on this page.

<table><thead><tr><th width="98.79998779296875">Type</th><th>Displays the type of Measurement:</th></tr></thead><tbody><tr><td><strong>Voltage</strong></td><td>The eHS solver outputs a voltage measurement on the corresponding channel during the simulation.</td></tr><tr><td><strong>Current</strong></td><td>The eHS solver outputs a current measurement on the corresponding channel during the simulation.</td></tr></tbody></table>

## Measurements Section Channels

After a model has been loaded in the **Circuit Model Section**, the Measurements section of the configuration tree is populated with a list of custom device channels corresponding to each measurement component found in the circuit model. These channels can be connected to other VeriStand channels in the project using the VeriStand **Mapping Diagram**.

{% hint style="info" %}
For any connections made in the Mapping Diagram, the data is passed through VeriStand channels on the Real Time CPU, resulting in increased latency and slower sampling rates than the rate at which data is generated on the FPGA.
{% endhint %}

To map eHS Measurements to other FPGA-simulated components managed by the Power Electronics Add-On, use the mapping options on their respective configuration pages **Machines** and **Analog Outputs.**

To view eHS Measurements in the VeriStand Workspace UI, use the **Waveforms** feature.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2Fjmwykf1aEMHcbbAc288a%2F9a5a90de-0a4d-4773-9b63-c78fff35b657.png?alt=media&amp;token=08753075-c859-468d-a387-7a6852f9d03a" alt=""><figcaption></figcaption></figure>


---

# 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/pe-add-on-simulink/model-and-simulation/add-and-configure-a-circuit-model-to-the-system-definition/measurements-section.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.
