> 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-in.md).

# Resolver In

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-c25f6c5f6c8d214684231647cb89bdd5ec513f35%2F0414ad70-b736-42dc-87e0-b8fb91a51fcf.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Resolver In** block, located in the **RT-LAB I/O/Opal-RT/Common** library, acquires and demodulates resolver feedback signals to compute the **rotor angle and speed** of a **two‑pole resolver**.

The block processes **carrier‑modulated sine and cosine signals** acquired from Analog Input modules and extracts position and speed information in real time. The demodulation process can use an **internally generated carrier** or an **external carrier input**, depending on the selected configuration. A single Resolver In block can process signals for **up to two resolvers**, with vectorized inputs and outputs. 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-f75c37c445e9689493d69b40702307592180b2d7%2F8a1e7479-7659-464a-a69d-59227ffd5112.png?alt=media" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="General" %}

<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>DataOut port number</strong></td><td>Specifies the Analog Input module and subsection from which this block acquires signals. Subsection 1 corresponds to channels 0–7, subsection 2 corresponds to channels 8–15, and so on.<br>Configure the <strong>DataOut 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 Input module derived from the selected <strong>DataOut 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>Calibration mode</strong></td><td><p><strong>Checked:</strong> Exposes the Resolver In block mask parameters as block inputs, allowing these parameters to be adjusted <strong>during execution</strong>.</p><p><strong>Unchecked:</strong> Resolver parameters remain configurable only through the block mask and <strong>cannot be modified at runtime</strong>.</p></td></tr></tbody></table>
{% endtab %}

{% tab title="Filtering Parameters" %}

<table><thead><tr><th width="213.083251953125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Damping factor (Ksi)</strong></td><td>Specifies the filter damping factor.</td></tr><tr><td><strong>Natural Frequency (w0)</strong></td><td>Specifies the filter natural frequency, expressed in hertz (Hz).</td></tr></tbody></table>

When **Number of resolver signals** is **2**, the value must be provided as a **1×2 vector** (e.g., **\[1 1]**).
{% endtab %}

{% tab title="Carrier Generation" %}

<table><thead><tr><th width="176.833251953125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Use internal carrier for demodulation</strong></td><td><p><strong>Checked:</strong> The Resolver In block generates its <strong>own carrier signal</strong> for demodulation.</p><p><strong>Unchecked:</strong> The Resolver In block uses an <strong>external carrier signal</strong> for demodulation.</p></td></tr><tr><td><strong>Internal Carrier Delay</strong></td><td>Specifies the delay applied to the internal carrier relative to the resolver sine and cosine signals. The value is expressed in <strong>seconds</strong> and must be between <strong>0 and 20e-6 s</strong>.</td></tr><tr><td><strong>Internal Carrier Frequency</strong></td><td>Specifies the carrier frequency, expressed in hertz (Hz). The valid range is <strong>0.01 to +90 000 Hz</strong>.</td></tr><tr><td><strong>Internal Carrier Amplitude</strong></td><td>Specifies the amplitude of the carrier signal generated by the Resolver In block. The value is expressed in volts and must be in the range <strong>0 to 16 V</strong>, with a <strong>resolution of 1 mV</strong>.</td></tr><tr><td><strong>Internal Carrier Offset</strong></td><td>Specifies the offset of the carrier signal generated by the Resolver In block. The value is expressed in volts and must be in the range <strong>-16 V to 16 V</strong>, with a <strong>resolution of 1 mV</strong>.</td></tr></tbody></table>

When **Number of resolver signals** is **2**, the value must be provided as a **1×2 vector** (e.g., **\[1 1]**).
{% endtab %}

{% tab title="Resolver Signals adjustments" %}

<table><thead><tr><th width="149.333251953125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>External Carrier Amplitude</strong></td><td><em>Visible only when <strong>Use internal carrier for demodulation</strong> is <strong>unchecked</strong>.</em><br>Specifies the amplitude of the external carrier signal expected by the Resolver In block. The value is expressed in volts and must be in the range <strong>0 to 16 V</strong>, with a <strong>resolution of 1 mV</strong>.</td></tr><tr><td><strong>External Carrier Offset</strong></td><td><em>Visible only when <strong>Use internal carrier for demodulation</strong> is <strong>unchecked</strong>.</em><br>Specifies the offset of the external carrier signal expected by the Resolver In block. The value is expressed in volts and must be in the range <strong>-16 V to 16 V</strong>, with a <strong>resolution of 1 mV</strong>.</td></tr><tr><td><strong>Sine Amplitude</strong></td><td>Specifies the amplitude of the resolved sine signal. The value is expressed in volts and must be in the range <strong>0 to 16 V</strong>, with a <strong>resolution of 1 mV</strong>.</td></tr><tr><td><strong>Sine offset</strong></td><td>Specifies the offset of the resolved sine signal. The value is expressed in volts and must be in the range <strong>-16 V to 16 V</strong>, with a <strong>resolution of 1 mV</strong>.</td></tr><tr><td><strong>Cosine Amplitude</strong></td><td>Specifies the amplitude of the resolved cosine signal. The value is expressed in volts and must be in the range <strong>0 to 16 V</strong>, with a <strong>resolution of 1 mV</strong>.</td></tr><tr><td><strong>Cosine offset</strong></td><td>Specifies the offset of the resolved cosine signal. The value is expressed in volts and must be in the range <strong>-16 V to 16 V</strong>, with a <strong>resolution of 1 mV</strong>.</td></tr></tbody></table>

When **Number of resolver signals** is **2**, the value must be provided as a **1×2 vector** (e.g., **\[1 1]**).
{% endtab %}
{% endtabs %}

## Inputs

This block has no inputs by default.

When **Calibration mode** is **checked**, the block mask parameters are exposed as block inputs, allowing them to be adjusted during execution. If the **Number of resolver signals** parameter is set to **2**, the block input ports expect **vectors of size 2**, with one element per resolver. Use a **Mux** block to combine individual signals into a single input vector.

## Outputs

<table><thead><tr><th width="102">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Angle</strong></td><td>Outputs the resolver angle, expressed in degrees, with 16‑bit precision. The valid range is <strong>0 to 360 degrees</strong>. The output vector size is determined by the <strong>Number of resolver signals</strong> parameter. Use a <strong>Demux</strong> block to access individual resolver angle signals.</td></tr><tr><td><strong>Speed</strong></td><td>Outputs the resolver speed, expressed in hertz (Hz). The output vector size is determined by the <strong>Number of resolver signalss</strong> parameter. Use a <strong>Demux</strong> block to access individual resolver speed signals.</td></tr><tr><td><strong>Car_Pu</strong></td><td><em>Visible only when <strong>Calibration mode</strong> is <strong>checked</strong>.</em><br>Outputs the scaled carrier waveform. When the <strong>Carrier Amplitude</strong> and <strong>Offset</strong> parameters are correctly tuned, the output represents the calibrated carrier signal.</td></tr><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>: Data reception timeout, typically caused by model synchronization issues.</li><li><code>-3</code>: Data reception error: fewer data received than expected. Missing values are replaced with <code>0</code>.</li><li><code>-4</code>: Data reception error: more data received than expected. Extra values are discarded.</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-in.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.
