> 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/model-and-simulation/import-models-from-external-software-or-code/import-from-simulink-hyperlink/prerequisites-and-supported-features.md).

# Prerequisites & Supported Features

This page summarizes the prerequisites, supported features, and known limitations when importing Simulink models into HYPERSIM using Simulink Import / Hyperlink. Reviewing this information before exporting a model helps ensure a successful import and avoids unsupported configurations.

## Supported features

* MATLAB versions **R2015b to R2024a**
* MATLAB Coder license
* Simulink Coder or Embedded Coder license
* Multiple‑instance modeling (multiple instances of the same Simulink model)
* Tunable parameters
* Model confidentiality through compilation
* Multiple time‑step code generation (R2015b to R2019b only, Simulink Coder only)
* Multiple rates within a single model
* Inline S‑functions and MATLAB Function blocks
* Non‑inline S‑functions (C‑based) for:
  * Embedded Coder targets (R2015b–R2024a)
  * Simulink Coder targets (R2015b–R2024a)
* Integration of Simulink Scopes (internal variables exposed via HYPERSIM sensors)
* Exchange of standard Simulink signals with HYPERSIM
* Import of Simscape components via voltage/current measurement and injection
* Fixed‑step solvers:
  * discrete, ode1
  * ode2, ode3, ode4, ode5, ode8, ode14x (supported when a zero‑order hold with a major‑step sample time is inserted before each model output)

## Minimal prerequisites

* MATLAB license including:
  * MATLAB Coder (required for C/C++ code generation)
  * Simulink Coder
* Embedded Coder (optional, recommended for improved performance and customization of generated code)

## Unsupported functionalities

* Variable‑step solvers (only fixed‑step solvers are supported)
* External mode (replaced by tunable parameters in HYPERSIM)
* Data logging
* S‑functions implemented in `.m` files (C‑based S‑functions are supported)
* M‑functions (except when using the MATLAB Function block)
* Specialized Power Systems (SPS) library


---

# 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/model-and-simulation/import-models-from-external-software-or-code/import-from-simulink-hyperlink/prerequisites-and-supported-features.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.
