> 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/hyperlab/configure-i-os/simulator-setup.md).

# Simulator Setup

A **Simulator Setup** is a project-scoped configuration that binds a project to:

* a specific simulator
* a chosen firmware (physical I/O definition)
* a simulation mode (real-time or accelerated)
* simulation parameters (time step, stop time).

A given project can have multiple **Simulator Setups**, and the user can switch from one to another.

User can choose where to run the model through the **Simulator Setup**, which is accessible by clicking on the upper ribbon.

There is always a default **Simulator Setup** called **This PC**. When selected, the model runs locally on the user workstation. In this case, there is no need to have access to a real-time simulator.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FtbJLu6dKh2lqJaCpcRk1%2FSimulator_setup_this_PC.png?alt=media&amp;token=9310d21f-0728-4541-9d46-8f3dd7281b58" alt="" width="375"><figcaption></figcaption></figure>

Each **Simulator Setup** owns its own set of **interface connections** (wired to the firmware's IO channels), while shared connections (model-to-model, model-to-widget) remain global across all setups of a given project.

Multiple **Simulator Setups** can reference the same physical simulator with different firmware or interface connection mappings, enabling side-by-side hardware configurations within a single project.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FNwE5LFmkS8Vze9LtELTK%2FSimulator_setup_OP4300.png?alt=media&amp;token=64af0664-d49e-441e-ba8c-1a9cd91e55e1" alt=""><figcaption></figcaption></figure>

{% columns %}
{% column %}
**HIL Controller 1** uses an **OP4300** simulator, with firmware **OP4300\_2-AX-0001-X\_Y\_Z\_LOCAL-eHSx16\_Gen4\_PMSMVDQ-00-08.v3\_0\_0**, with a **real-time** simulation mode. The model signals are mapped to I/Os in a certain way such as:

* output voltage -> <mark style="color:$warning;">**Analog Out 00**</mark>
* output current -> <mark style="color:$warning;">**Analog Out 01**</mark>
* gating signal -> <mark style="color:$warning;">**Digital Input 00**</mark>
  {% endcolumn %}

{% column %}
**HIL Controller 2** uses the same parameters as above, but the model signals may be mapped to I/Os in a different way such as:

* output voltage -> <mark style="color:$warning;">**Analog Out 02**</mark>
* output current -> <mark style="color:$warning;">**Analog Out 03**</mark>
* gating signal -> <mark style="color:$warning;">**Digital Input 01**</mark>
  {% endcolumn %}
  {% endcolumns %}

This lets the user **switch easily** from one I/O configuration to another, within the **same project**.


---

# 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/hyperlab/configure-i-os/simulator-setup.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.
