> 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/configure-ios/analog-digital-and-sfp-ios/s-function-workflow/multi-core-model-ios.md).

# Multi-Core Model I/Os

When a model includes electrical I/O distributed across multiple subsystems, the configuration process is similar to the standard **S-Function Workflow**. The key difference is that **each additional subsystem containing I/O** must include an **OpLnk** block.

{% stepper %}
{% step %}

### Prepare the model directory

Copy the **bitstream files** (`.bin` and `.conf`) provided with your system to the model folder.
{% endstep %}

{% step %}

### Add a single OpCtrl block

Use a single **OpCtrl** block within one computation subsystem where signals will be exchanged through I/O modules (**SM\_** or **SS\_**). The choice of subsystem is not critical. Configure the following parameters:

* **Primary Bitstream Filename** – Select the correct `.bin` file.
* **Board Type** – Identify from the bitstream filename.

All other parameters can remain at their default values **unless you are working with multiple FPGA systems or external synchronization**.
{% endstep %}

{% step %}

### Add I/O blocks to the subsystem with the **OpCtrl** block

From *RT-LAB I/O > Opal-RT > Common*, add the required I/O blocks to the subsystem containing the **OpCtrl** block, and configure the following parameters:

* **`DataOut`** / **`DataIn` port numbers** – Configure each block’s **`DataOut`** and **`DataIn`** **port numbers** according to your **System Description Document** or the `.conf` file.

By default, the **Controller Name** parameter in I/O blocks is set to 'OpCtrl', matching the default **Controller Name** in the **OpCtrl** block. This parameter is used to link I/O blocks to specific **OpCtrl** or **OpLnk** blocks when many are present. For this configuration, leave the default value unchanged.
{% endstep %}

{% step %}

### Add an **OpLnk** block

From *RT-LAB I/O > Opal-RT > Common*, add the **OpLnk** block to **another** **subsystem containing I/O**, and configure the following parameters:

* **Primary Bitstream Filename** – Select the correct `.bin` file.
* **Board Type** – Identify from the bitstream filename.

All other parameters can remain at their default values **unless you are working with multiple FPGA systems or external synchronization**.
{% endstep %}

{% step %}

### Add I/O blocks to the subsystem with the **OpLnk** block

From *RT-LAB I/O > Opal-RT > Common*, add the required I/O blocks to the subsystem containing the **OpCtrl** block, and configure the following parameters:

* By default, the **Controller Name** parameter in I/O blocks is set to 'OpCtrl'. **Change this value to 'OpLnk' to link the I/O blocks to the OpLnk block present in this subsystem.**

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

* **`DataOut`** / **`DataIn` port numbers** – Configure each block’s **`DataOut`** and **`DataIn`** **port numbers** according to your **System Description Document** or the `.conf` file.
  {% endstep %}

{% step %}

### Repeat steps 4 and 5 for **each additional subsystem containing I/O blocks**

Each additional subsystem containing I/O must include an **OpLnk** block with a unique **Controller Name** (e.g., 'OpLnk2', 'OpLnk3', etc.). All I/O blocks within that subsystem must have their **Controller Name** parameter set to match the corresponding **OpLnk** block.
{% endstep %}

{% step %}

### Save, build, load and execute the model

1. Save and run the Simulink model to confirm that everything works as expected.
2. In RT-LAB, build the model.
3. Go to the **Execution** tab and ensure that the **Real-time simulation mode** is set to **Hardware synchronized**.
4. Open the **Assignation** tab and ensure that the **XHP** box is checked (enabled).
5. Load and execute the model in RT-LAB.
   {% endstep %}
   {% endstepper %}

Refer to your simulator and/or expansion unit documentation for detailed instructions on connecting external hardware or a DUT through its I/O modules.


---

# 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/configure-ios/analog-digital-and-sfp-ios/s-function-workflow/multi-core-model-ios.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.
