> 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/ehs/model-in-schematic-editor/configure-the-ehs-circuit-interfaces.md).

# Configure the eHS Circuit Interfaces

The eHS circuit model exchanges information with <code class="expression">space.vars.cpu\_model\_veristand</code> and/or an external device under test (DUT) through **sources**, **measurements**, **machine signals**, and **switch gate signals**. These interfaces are configured directly in the Schematic Editor.

<figure><img src="https://3212678799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FABuoXNYgvaoO7wIe3bfO%2Fuploads%2Fgit-blob-41368e792b9b253ac7776326d41d7b7550ed7f60%2Fse-ehs-interfaces.png?alt=media" alt=""><figcaption></figcaption></figure>

To configure an interface, select the corresponding block in the circuit and open its **Parameters** panel. The available interface options depend on the block type. Refer to the appropriate section for detailed configuration instructions.

Once the interfaces have been configured, save the circuit model by selecting **File > Save**. The updated interface configuration will be applied the next time the circuit is loaded.

{% hint style="info" %}

#### I/O Channel Assignment Rules

When configuring I/O channels in Schematic Editor:

**Input channels**

* Multiple block parameters and signals can be driven by the same **analog input**, **SFP input**, or **digital input** channel.
* Sharing an input channel allows the same external signal to drive multiple parameters or signals simultaneously.

**Output channels**

* Each **analog output** or **SFP output** channel can be assigned to only one block parameter or signal.
* Schematic Editor prevents assigning the same analog or SFP output channel to multiple block parameters or signals. If a channel is already in use, a warning message is displayed.
  {% endhint %}

{% hint style="info" %}

#### Interaction with <code class="expression">space.vars.cpu\_model\_veristand</code>

When I/O channels are configured for both the Schematic Editor circuit model and <code class="expression">space.vars.cpu\_model\_veristand</code>:

**Input channels**

* Multiple signals, whether originating from the Schematic Editor circuit model or <code class="expression">space.vars.cpu\_model\_veristand</code>, can be driven by the same analog input, SFP input, or digital input channel.

**Output channels**

* Analog output and SFP output channels are shared hardware resources.
* **Each output channel should be driven by only one source across the entire simulation**, including both the Schematic Editor circuit model and <code class="expression">space.vars.cpu\_model\_veristand</code>.
* If the same analog or SFP output channel is assigned in both the Schematic Editor circuit model and <code class="expression">space.vars.cpu\_model\_veristand</code>, the resulting behavior depends on the simulation platform, workflow, firmware, and I/O configuration. **Ensure that each output channel is assigned to a single source only.**
* When an analog output channel belonging to a given subsection (group of 8 channels) is assigned in the Schematic Editor circuit model, **the entire subsection is reserved by the Schematic Editor**. As a result, none of the eight channels in that subsection can be used by <code class="expression">space.vars.cpu\_model\_veristand</code>.
  {% 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/ehs/model-in-schematic-editor/configure-the-ehs-circuit-interfaces.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.
