> 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/hypersim/examples/i-o-interfaces/muse.md).

# MuSE

## Description

The **MuSE** example is located in **File > Open an Example File > IO Interfaces**

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d0f2909fdf39bc201dd17c33df96ab16bfc6a5b6%2Fexamples-muse.png?alt=media" alt=""><figcaption></figcaption></figure>

## Hardware Setup

### Required Materials

Here is a list of what is required to execute this example project:

* OP4510V2 chassis, as the central system
* OP4520 chassis, as a remote system
* 1 optical fiber cables
* 2 duplex SFP transceivers
* 6 DB37 loopback cables
* 1 Ethernet cable to establish communication between the central and the host

### Tested Configuration

This example project has been tested with the following configuration:

#### Optical Fiber Cable

* **Connector:** LC to LC
* **Fiber mode:** Multimode 62.5/125 μm
* **Jacket color:** Orange
* **Wavelength:** 850/1300 nm
* **Fiber type:** Duplex

#### Optical Transceiver

* **Wavelength:** 850 nm
* **Connector:** LC duplex optical connector
* **Fiber mode:** Multimode
* **Fiber type:** Duplex
* **Coding color:** Black color coded bale clasp

## Model Preparation and Configuration

1. In the OPAL-RT Board interface set the Board ID of the central OP4510V2 and the remote OP4520 according to your hardware setup.
2. Program the bitstream of the central OP4510V2 and the remote OP4520 using Hypersim's flash utility.
3. Compile the model.
4. Load the model.
5. Verify that the OPAL-RT Board interface is loaded.
6. Verify that OPAL-RT Board enumerates the remote OP4520.
7. Verify that all connections have been properly made.
8. Execute the model.

> **Note:** For more details about the OPAL-RT Board configuration, please refer to the OPAL-RT Board interface documentation. In Hypersim, click on **Help → Help Center**. In the window that appears, navigate to **Hypersim I/O Block Library Reference Guide → Opal-RT → OPAL-RT Board → OPAL-RT Board overview**.

## Master Subsystem

The master subsystem contains 2 subsystems: OP4510V2 central IOs and OP4520 remote IOs.

### Subsystem Overview

#### OP4510V2 Central IOs Subsystem

* Analog Inputs and Outputs
* Static Digital Inputs and Outputs
* PWM Inputs and Outputs
* Event detector (TSDIn) and event generator (TSDOut)

#### OP4520 Remote IOs Subsystem

* Advanced Analog Inputs and Outputs
* Static Digital Inputs and Outputs
* PWM Inputs and Outputs
* Event detector (TSDIn) and event generator (TSDOut)

## Console Subsystem

The console subsystem allows the user to modify the parameters of each outputted signal of the 2 subsystems: OP4510V2 Central IO's and OP4520 Remote IO's.

### Analog Out

The amplitude and the waveform type of each analog out signal can be modified. By default, a sine wave with an amplitude of 16 V is created for each channel.

### Static Digital Out

The binary value of each static digital out signal can be modified. By default, the value of each channel is '0'.

### PWM Out

The frequency and the duty cycle of each PWM out signal can be modified. By default, the frequency is a value between 1 KHz and 8 kHz and the duty cycle is a value between 0.1 and 0.8 for each channel.

### Event Generator (TSDOut)

The transitions (events) that will occur and the timestamp at which they will occur in the next time step. By default there are 4 events per channel as follows:

| Channel | Event 1                   | Event 2                    | Event 3                   | Event 4                    |
| ------- | ------------------------- | -------------------------- | ------------------------- | -------------------------- |
| Ch0     | Rising edge at 0.35 \* Ts | Falling edge at 0.45 \* Ts | Rising edge at 0.55 \* Ts | Falling edge at 0.65 \* Ts |
| Ch1     | Rising edge at 0 \* Ts    | Falling edge at 0.1 \* Ts  | Rising edge at 0.2 \* Ts  | Falling edge at 0.3 \* Ts  |
| Ch2     | Rising edge at 0.05 \* Ts | Falling edge at 0.15 \* Ts | Rising edge at 0.25 \* Ts | Falling edge at 0.35 \* Ts |
| Ch3     | Rising edge at 0.1 \* Ts  | Falling edge at 0.2 \* Ts  | Rising edge at 0.3 \* Ts  | Falling edge at 0.4 \* Ts  |
| Ch4     | Rising edge at 0.15 \* Ts | Falling edge at 0.25 \* Ts | Rising edge at 0.35 \* Ts | Falling edge at 0.45 \* Ts |
| Ch5     | Rising edge at 0.2 \* Ts  | Falling edge at 0.3 \* Ts  | Rising edge at 0.4 \* Ts  | Falling edge at 0.5 \* Ts  |
| Ch6     | Rising edge at 0.25 \* Ts | Falling edge at 0.35 \* Ts | Rising edge at 0.45 \* Ts | Falling edge at 0.55 \* Ts |
| Ch7     | Rising edge at 0.3 \* Ts  | Falling edge at 0.4 \* Ts  | Rising edge at 0.5 \* Ts  | Falling edge at 0.6 \* Ts  |

> **Note:** If loopback cables are connected on the I/O cards, the console subsystem also allows the user to visualize the signals received on each analog input, static digital input, PWM input and event detector channel.

## Interface Configuration

The OPAL-RT Board interface configuration is done entirely via Hypersim's GUI, under the I/Os section of the example project.

## Connecting the Interface and the Model

Connections between the interface and the model are also done entirely via Hypersim's GUI.

## Testing the Model

Once the bitstream has been programmed at least once from Hypersim for the central and the remote, the interface has been configured and the model has been compiled, loaded on the target and ran, the parameters of the outputted signals can be modified and the received signal(s) of each I/O channel can be visualized in the console subsystem.


---

# 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/hypersim/examples/i-o-interfaces/muse.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.
