> 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/sources-section.md).

# Sources Section

## Overview

Sources are **input signals** to the eHS electrical circuit model. They are either current or voltage sources whose output signals can be be driven by custom device channels, analog inputs, signal generators, and more. In the electrical circuit model, it is recommended (but not necessary) to denote the sources of the model with the *UXX* 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 Source 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%2F6coHQm9ZRh1laPxF434R%2F61c937d3-ce68-4530-b721-fcc050595f2c.png?alt=media&amp;token=4468cb93-0c1c-422f-9fa7-166b1ef3c06a" alt=""><figcaption></figcaption></figure>

## Sources Configuration Page

In the **System Explorer** window configuration tree, expand the **Power Electronics Add-On** custom device and select **Circuit Model >> Sources** 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 **Source** components found in the circuit model. An incoming signal must be mapped to each Source to drive its voltage or current as it is simulated in the eHS solver.

### Sources Settings

For each Source, the following information and mapping options are available at edit-time.

<table><thead><tr><th width="139.7777099609375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Type</strong></td><td><strong>Voltage Source;</strong> The Source will output a voltage during the simulation. The magnitude of this voltage is determined by the magnitude of the signal mapped to the Source.<br><strong>Current Source:</strong> The Source will output a current during the simulation. The magnitude of this current is determined by the magnitude of the signal mapped to the Source.</td></tr><tr><td><strong>Group</strong></td><td>Filters the list of available elements to be mapped to the Source. The available options are defined by the selected <strong>Hardware Configuration</strong>, however it is typical to see the following options by default:<br><strong>CPU (VeriStand):</strong> VeriStand custom device channels on the CPU. If this Group is selected, the <strong>Element</strong> dropdown is populated with a single option displaying the name of the custom device channel whose value is mapped.<br><strong>Sinewaves:</strong> Sinewave outputs of the <strong>Sinewave Generators</strong>. In the <strong>Element</strong> dropdown, select the index of the Sinewave Generator whose output signal to map.<br><strong>Machine:</strong> Output channels of the <strong>Machine Model</strong>. In the <strong>Element</strong> dropdown, select the name of the channel to map.<br><strong>Analog Inputs: Analog Input</strong> channels of the PXI card. In the <strong>Element</strong> dropdown, select the index of the AI channel to map.</td></tr><tr><td><strong>Element</strong></td><td>The name or index of the signal to be mapped to the Source. The options available in this dropdown depend on the selected Group.</td></tr></tbody></table>

## Sources Section Channels

After a model has been loaded in the **Circuit Model Section**, the **Sources** section of the Configuration Tree is populated with a list of channels corresponding to each source component found in the circuit model. If a source is mapped to the **CPU (VeriStand)** Group described above, then the value of its corresponding channel defines the magnitude of the Source during the simulation. If the **CPU (VeriStand)** Group is unused, then the value of the channel does not affect the circuit simulation.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2Fop3rf6epF5Jy05yK46kW%2F8c0093ad-0707-4c46-bcd6-7841b835d8d6.png?alt=media&amp;token=c615a8de-959c-41a0-93af-ebaa4e351400" 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/sources-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.
