> 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/rt-lab/simulink-blocks-reference/efpgasim-library/opal-rt-schematic-editor-workflow/ehs_se_opalboards_drivers.md).

# eHS\_SE\_OpalBoards\_Drivers

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-d9dbe51006a0483ce721c9e52c618320fe702f81%2FeHS_SE_OPALboard_block.png?alt=media" alt="" width="176"><figcaption></figcaption></figure>

The **eHS\_SE\_OpalBoards\_Drivers** block, located in the **eFPGAsim** library, allows you to create, edit, configure, and run an FPGA-based circuit using the OPAL-RT Schematic Editor. It supports FPGA-based simulation workflows and enables predefined parameter sets to switch test cases during simulation.

## Mask parameters

This block has no parameters.

## Inputs

<table><thead><tr><th width="175.81817626953125">Input</th><th>Description</th></tr></thead><tbody><tr><td>Controlled sources</td><td>Drives the controlled current and controlled voltage sources defined in the Schematic Editor circuit.</td></tr><tr><td>Switches</td><td>Controls the switches defined in the Schematic Editor circuit.</td></tr><tr><td>Parameter set id</td><td>Available only when additional parameter sets are defined in the Schematic Editor. Allows changing the active parameter set during real-time simulation.</td></tr><tr><td>Reset</td><td>Available only when the <strong>Reset Pin</strong> option in the Schematic Editor Solver Settings is enabled. Resets eHS outputs and machine outputs to 0.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="176.72723388671875">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Dynamically generated outputs</strong></td><td>Real-time measurement values placed in the Schematic Editor circuit. Voltage and current measurements are averaged over a workstation model time step using a moving average function on the FPGA, except for measurements from machine blocks, which are zero-hold sampled.</td></tr></tbody></table>

## Characteristics and limitations

<table><thead><tr><th width="234.90911865234375">Characteristic</th><th>Value</th></tr></thead><tbody><tr><td>Workflow model source</td><td>File-centric workflow based on the <code>.ehs3</code> file</td></tr><tr><td>Model synchronization</td><td>The <code>[yourModel].ehs3</code> file must be available in the MATLAB path to ensure proper synchronization.</td></tr><tr><td>Measurement behavior</td><td>Voltage and current measurements are averaged over one workstation model time step, except for machine block measurements.</td></tr><tr><td>Protected block usage</td><td>Protected blocks can be used without the OPAL-RT Schematic Editor installed and do not allow circuit or parameter modification.</td></tr></tbody></table>


---

# 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/rt-lab/simulink-blocks-reference/efpgasim-library/opal-rt-schematic-editor-workflow/ehs_se_opalboards_drivers.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.
