> 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/rt-lab-i-o-library/resolver-out.md).

# Resolver Out

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-8c4588eed29d2d30c44345a848662d06d055fd3d%2F7f9efb11-5d08-478d-9e47-985ec7306cd2.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Resolver Out** block, located in the **RT-LAB I/O/Opal-RT/Common** library, controls a basic **two‑pole resolver** and provides real‑time adjustment of its operating parameters. The resolver **speed**, **carrier frequency**, **carrier amplitude**, **sine and cosine amplitudes**, and **sine and cosine offsets** can be modified during execution.

The carrier signal can be generated **internally or supplied externally**. In either case, the physical Analog Output modules generate **carrier‑modulated sine and cosine signals** based on the angular rate provided by the simulation. A single Resolver Out block can control **up to two resolvers**. Availability of this functionality depends on the bitstream supplied with the system. Refer to the **System Description Document** provided with your order for connector pin assignments.

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-4da3d4a155aec7374b87fbd2f6e7d766a3cfff06%2Faff1961d-a10e-4ebc-91c8-6fd562f12158.png?alt=media" alt="" width="329"><figcaption></figcaption></figure>

<table><thead><tr><th width="194.333251953125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Controller Name</strong></td><td>Specifies the <strong>OpCtrl</strong> block this block is bound to. Enter the same <strong>Controller Name</strong> as defined in the corresponding <strong>OpCtrl</strong> block.</td></tr><tr><td><strong>DataIn port number</strong></td><td>Specifies the Analog Output module and subsection to which this block transmits signals. Subsection 1 corresponds to channels 0–7, subsection 2 corresponds to channels 8–15, and so on.<br>Configure the <strong>DataIn port number</strong> according to your <strong>System Description Document</strong> or <code>.conf</code> file.</td></tr><tr><td><strong>Slot infos</strong></td><td>Read‑only field displaying the expected physical location (Slot, Section, Subsection) of the Analog Output module derived from the selected <strong>DataIn port number</strong>. If the port number is invalid, <em>Slot 0 Module X Subsection 0</em> is displayed.</td></tr><tr><td><strong>Number of resolver signals</strong></td><td>Specifies the number of resolvers controlled by the block. This parameter determines the size of the input vectors, corresponding to the number of resolver data values transmitted at each calculation step</td></tr><tr><td><strong>Output Mode</strong></td><td><p><strong>Single‑Ended:</strong> Sine, cosine, and carrier signals are generated as single‑ended outputs referenced to ground.</p><p><strong>Differential:</strong> Sine, cosine, and carrier signals are generated as differential pairs, providing improved noise immunity.</p></td></tr><tr><td><strong>Carrier 1 Select Mode</strong></td><td><strong>Internal</strong>: The carrier wave for the <strong>first resolver</strong> in the subsection is generated by the FPGA and the <strong>Carrier Amplitude</strong> and <strong>Carrier Frequency</strong> inputs become available for run‑time control. When<br><strong>External:</strong> The carrier wave for the <strong>first resolver</strong> in the subsection is provided by an external device.</td></tr><tr><td><strong>Carrier 2 Select Mode</strong></td><td><strong>Internal</strong>: The carrier wave for the <strong>second resolver</strong> in the subsection is generated by the FPGA and the <strong>Carrier Amplitude</strong> and <strong>Carrier Frequency</strong> inputs become available for run‑time control. When<br><strong>External:</strong> The carrier wave for the <strong>second resolver</strong> in the subsection is provided by an external device.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="138.5">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Speed</strong></td><td>Inputs the rotor speed, expressed in hertz (Hz). The valid range is <strong>−20 000 Hz to +20 000 Hz</strong>. The input vector size is determined by the <strong>Number of resolver signals</strong> parameter. Use a <strong>Mux</strong> block to combine individual signals into a single input vector.</td></tr><tr><td><strong>Car.Amp</strong></td><td>Inputs the carrier amplitude, expressed in volts (V). The valid range is <strong>0 to +15 V</strong>. The input vector size is determined by the <strong>Number of resolver signals</strong> parameter. Use a <strong>Mux</strong> block to combine individual signals into a single input vector.</td></tr><tr><td><strong>Car.Freq</strong></td><td>Inputs the carrier frequency, expressed in hertz (Hz). The valid range is <strong>0 to +95 000 Hz</strong>. The input vector size is determined by the <strong>Number of resolver signals</strong> parameter. Use a <strong>Mux</strong> block to combine individual signals into a single input vector.</td></tr><tr><td><strong>Sin.Amp</strong></td><td>Inputs the sine modulated amplitude, expressed in volts (V). The valid range is <strong>0 to +15 V</strong>. The input vector size is determined by the <strong>Number of resolver signals</strong> parameter. Use a <strong>Mux</strong> block to combine individual signals into a single input vector.</td></tr><tr><td><strong>Sin.Bias</strong></td><td>Inputs the sine offset, expressed in volts (V). The valid range is <strong>-15 V to +15 V</strong>. The input vector size is determined by the <strong>Number of resolver signals</strong> parameter. Use a <strong>Mux</strong> block to combine individual signals into a single input vector.</td></tr><tr><td><strong>Cos.Amp</strong></td><td>Inputs the cosine modulated amplitude, expressed in volts (V). The valid range is <strong>0 to +15 V</strong>. The input vector size is determined by the <strong>Number of resolver signals</strong> parameter. Use a <strong>Mux</strong> block to combine individual signals into a single input vector.</td></tr><tr><td><strong>Cos.Bias</strong></td><td>Inputs the cosine offset, expressed in volts (V). The valid range is <strong>-15 V to +15 V</strong>. The input vector size is determined by the <strong>Number of resolver signals</strong> parameter. Use a <strong>Mux</strong> block to combine individual signals into a single input vector.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="102">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Status</strong></td><td><p>Outputs the block status:</p><ul><li><code>0</code>: No error.</li><li><code>-1</code>: Block not associated with an <strong>OpCtrl</strong> block (check the <strong>Controller Name</strong> parameter), or FPGA initialization failure.</li><li><code>-2</code>: Internal memory initialization failure.</li></ul></td></tr></tbody></table>

## Characteristics and limitations

<table><thead><tr><th width="247.75">Characteristic</th><th>Value</th></tr></thead><tbody><tr><td><strong>Connector pin assignments</strong></td><td>Refer to the <strong>System Description Document</strong> provided with your order, or refer to the pin assignment of the <a href="https://opal-rt-technologies.gitbook.io/opal-rt-technologies-docs/op53xx/"><strong>OP53xx series I/O module</strong></a> associated with each subsection.</td></tr><tr><td><strong>Direct Feedthrough</strong></td><td>No</td></tr><tr><td><strong>Discrete sample time</strong></td><td>Inherited</td></tr><tr><td><strong>XHP support</strong></td><td>Yes</td></tr><tr><td><strong>Work offline</strong></td><td>No</td></tr></tbody></table>


---

# 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/rt-lab-i-o-library/resolver-out.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.
