> 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/first-steps/integrate-ehs-into-rt-lab-and-hypersim-models/prepare-an-rt-lab-model/auto-configure-opctrl-oplnk-blocks.md).

# Auto-configure OpCtrl/OpLnk Blocks

The **eHS\_SE\_SFunction\_Drivers** block and the associated **OpCtrl** (or **OpLnk**) block must be configured consistently to ensure that the correct FPGA firmware is loaded at runtime.

The **OpCtrl** (or **OpLnk**) block can be configured automatically to match the eHS circuit configuration:

1. Right-click the **eHS\_SE\_SFunction\_Drivers** block.
2. Select **eHS > Settings**.

The following options are available:

* **OpCtrl Name**\
  Specifies the name of the **OpCtrl** block to link to. This must match exactly to ensure proper synchronization with the S-Function driver.
* **Auto-configure OpCtrl/OpLnk Block**

  When **checked**, the OpCtrl **Primary Bitstream** is automatically set based on the configuration defined in the Schematic Editor.\
  When **unchecked**, the OpCtrl **Primary Bitstream** must be configured manually.

In most applications, a model contains **one eHS block and one OpCtrl block**. In multi-unit configurations, such as a simulator connected to one or more expansion units, each unit that uses eHS and/or I/O resources must have its own **OpCtrl** block linked to the corresponding **eHS\_SE\_SFunction\_Drivers** block.


---

# 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/first-steps/integrate-ehs-into-rt-lab-and-hypersim-models/prepare-an-rt-lab-model/auto-configure-opctrl-oplnk-blocks.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.
