> 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/configure-gate-signal-inputs.md).

# Configure Gate Signal Inputs

## Interface switch blocks

**Switch** blocks gate control signals are fully driven by external inputs. These inputs can originate from:

* <code class="expression">space.vars.cpu\_model\_veristand</code>
* Physical digital input channels

To select the external input:

1. Click the gate control signal input to open the **Deep Panel**. By default, the parameter value is provided by <code class="expression">space.vars.cpu\_model\_veristand</code>.
2. Click the **+** icon below **SOURCES** to reveal the additional options. Select **DI (Digital Input)** to add the source.
3. Multiple sources can be configured, but **only one can be active at a time**. To remove a source, hover over it and click the **trash** icon that appears.
4. Configure the **DI (Digital Input)** by selecting the I/O module and channel (**Pin**) that will drive the gate control signal, and its **Polarity**:

   * **HIGH**: The gate signal is active when the digital input is **high**.
   * **LOW**: The gate signal is active when the digital input is **low**.

   Multiple gate control signals can be assigned to the same digital input **Pin**. When doing so, ensure that the polarity of each gate signal is configured appropriately.

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

To revert to a gate control signal provided by the CPU model, select **FROM SIMULINK** (RT-LAB) or **FROM HYPERSIM** (HYPERSIM).


---

# 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/configure-gate-signal-inputs.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.
