> 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/simulink-blocks-reference/efpgasim-library/simulink-sps-workflow/analog-out-mapping-rescaling-v2-control-panel.md).

# Analog Out Mapping Rescaling V2 Control Panel

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-fe76ec0a967272e4c1e16ed9f87bc1f8749f3a9d%2Fanalog-out-map-rescal-control%3Dpanel.png?alt=media" alt="" width="364"><figcaption></figcaption></figure>

The **Analog Out Mapping Rescaling V2 Control Panel block**, located in the **eFPGAsim/External circuit editor workflow** library, provides an interface that helps users generate the configuration data for the [**AOut Mapping & Rescalling Controller**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/efpgasim-library/simulink-sps-workflow/analog-output-mapping-and-rescaling-controller.md) block. It is used to define the source and scaling parameters of the signals driving each analog output channel controlled by the associated parent driver block.

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-4e0e7c0d015f410f74cd2e33969dcb68dd2cb8c8%2Fanalog-out-mapping-param.png?alt=media" alt=""><figcaption></figcaption></figure>

| Parameter / Button      | Description                                                                                                                                                                                                                                                               |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **AOMR Version**        | Allows to choose between the two available versions of the AOMR block. The V1 allows to configure 1 or 2 lanes: lane 1 is parallel and lane 2 is serial. The V2 version allows to configure from 1 to 8 serial lanes.                                                     |
| **Number of lanes**     | <p>This parameter allows to choose how many lanes to configure. If 0 is selected, only CPU inputs are available.<br>It depends on the number of lanes parameter selected in the General box. The CPU inputs section is always available even if 0 lanes are selected.</p> |
| **Open Mapping Table**  | Opens the Mapping Table view where the signals assignation, gain, offset, min and max can be tuned.                                                                                                                                                                       |
| **CPU Inputs - Source** | Dropdown to choose between Custom List and Unassigned. This choice enables the Signals List.                                                                                                                                                                              |
| **Signals List**        | Allows to enter the signals list going to the lane. This list has to be exhaustive and the order of the names must match the actual order of the signals in the wire                                                                                                      |

## Inputs

This block has no input.

## Outputs

| Output       | Description                                                                                                                                                    |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **To\_Aout** | <p>Connects to the Aout\_Mapping & Adjustments block.<br>It contains all the parameters (mapping, gains, offsets, maximums and minimums) of every signals.</p> |

## Characteristics and limitations

The user must ensure that the gains, offsets and saturation threshold are consistent and fit any external hardware limitations. As an example, if the bottom saturation threshold is higher than the top saturation threshold, and both thresholds are trespassed simultaneously, a constant zero will be sent as the analog output signal.

| Direct Feedthrough   | N/A |
| -------------------- | --- |
| Discrete sample time | YES |
| XHP support          | YES |
| Work offline         | NO  |


---

# 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/simulink-blocks-reference/efpgasim-library/simulink-sps-workflow/analog-out-mapping-rescaling-v2-control-panel.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.
