> 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/model-and-simulation/integrating-models-from-simulink-r/generating-the-export-file.md).

# Generating the Export File

## Design Rules

Some basic design rules and constraints must de followed to ensure the successful generation of the Export File from the Simulink<sup>®</sup> model.

* **Inport** and/or **Outport** blocks need to be defined at the top-level of the model. They will be the interfaces between the Simulink<sup>®</sup> model and the HYPERLAB One model.
* Signals coming from the top-level Inports and going to the top-level Outports must be **scalar**, of type **double**.
* Block parameters that need to be accessed once the Simulink model is imported into HYPERLAB must be **scalar**, of type **double**.
* Although there is no obligation to define **subsystems**, users can use them in the model.
* The Simulink model *Fixed-step size (fundamental sample time)* must match the *Simulation Time Step* defined in the HYPERLAB ONE model.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FQ9Q4gk2qRJZFMYDh9yUO%2FSimulink_Example.png?alt=media&amp;token=161036c2-e8ad-41d6-9d1b-e8a513e9a573" alt=""><figcaption></figcaption></figure>

## Analysis and Build

The **Analysis** function makes it possible to verify the model's consistency and compliance with the design rules. Warning and errors would appear on the **Diagnostic Viewer**.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FfTIHS5b3vHdkOAhxx4Qm%2FSimulink_Example_Analysis.png?alt=media&amp;token=bd2bd211-0fe3-4c24-b6de-9960a674bd1a" alt=""><figcaption></figcaption></figure>

User can then **Build** the model to generate the Export File, which is created in the *hyperlab* folder located alongside the Simulink model.&#x20;

{% hint style="info" %}
The extension of the Export File is \*.**SLXBIN**.
{% endhint %}

For instance, let's assume the Simulink model is called *basic.slx*. Building *basic.slx* generates *hyperlab/basic.slxbin*, where the *hyperlab* folder is located in the same directory as *basic.slx*.

<figure><img src="broken://files/VcEYl4sgjv2xkU61BuUq" alt="" width="375"><figcaption></figcaption></figure>

## Filter Parameters

User can select which parameters they want to access from the Export File, once imported into HYPERLAB One. By default, all accessible parameters are selected, but a more restricted set can be chosen.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FjzV9SmIqKNGva2Xv4Vb8%2FSimulink_Filter_Parameters.png?alt=media&amp;token=ac17dd80-2691-49fb-80a1-4d80417a3c93" alt=""><figcaption></figcaption></figure>


---

# 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/model-and-simulation/integrating-models-from-simulink-r/generating-the-export-file.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.
