> 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/op1400pr/supplementary-operations/op1400pr-nn-ui-block.md).

# OP1400PR-nn UI Block

### Description <a href="#description" id="description"></a>

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2Fh6fiasxK0q5ShhdWXmG5%2FOP1400PR-60%20block.png?alt=media&amp;token=952703f6-b2b3-40b1-8bb4-79dff0eaabad" alt="" width="268"><figcaption></figcaption></figure>

The **OP1400 Prime UI** **block** provides a **unified user interface (**[**UI**](#user-content-fn-1)[^1]**)** to configure the OP1400PR test benches.

{% hint style="danger" %}
This block is **already configured for your system**. Normally you don't have to modify any parameters.
{% endhint %}

The block is part of the **project file provided with your system** on a **USB key**. It is located in the **Test\_models/rtlab\_project** **folder**.

* The file is a **compressed zip file** with the **model of your test bench** in it, in the form of “**OP1400PR\_*****00*****.zip**” where “*00*” is the model number (10, 20, 30, or 60).
* The file name can also include the **project number** as a **prefix** in the form of “CC123456” where “123456” is your project number.
* The file name can also include an **eHS generation number** as a **suffix** in the form of “Gen4” or “Gen5”
* Example of a project file name: CC123456\_**OP1400PR\_60**\_Gen4

To **use your test bench** you need to load the test bench project file in RT-LAB.

* Import the project as explained here: [Import Your Integration Project in RT-LAB](https://www.opal-rt.com/docs/rt-lab/get-started/run-your-integration-project/import-your-integration-project-in-rt-lab).

To **edit the OP1400PR-nn UI block**:

* In RT-LAB, find the model and edit it. MATLAB opens.
* In MATLAB, open Simulink.
* In Simulink, open the model.
* In the model, edit the **OP1400PR\_00 block**.

## Overview

All test bench variants share a **common UI layout** and configuration workflow.

The **test bench-specific configuration** settings are discussed in their respective sections separately.&#x20;

This section describes the **features** and **settings** that are **common** across all **test benches**.

{% hint style="info" %}
For **example purposes** we will use the UI Block Parameters for an **OP1400PR-60 test bench**. Refer to all test bench models here: [Description and Components](https://www.opal-rt.com/docs/op1400pr/op1400pr-overview/description-and-components.md#op1400pr-phil-test-bench-models)
{% endhint %}

## UI layout and navigation <a href="#ui-layout-and-navigation" id="ui-layout-and-navigation"></a>

The OP1400PR UI is organized into a **fixed parameters side bar** on the **left** and **multiple tabs** on the **right**. Each **tab** represents a **specific configuration category**.

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FmnwsClNcMTN03yFQSbTf%2Fimage.png?alt=media&amp;token=c203074b-30ce-42ef-8b39-306cf0f47752" alt=""><figcaption></figcaption></figure>

### <mark style="background-color:green;">Common section and tabs</mark> <a href="#common-section-and-tabs" id="common-section-and-tabs"></a>

1. <mark style="background-color:green;">Sidebar for</mark> <mark style="background-color:green;"></mark><mark style="background-color:green;">**Parameters**</mark>&#x20;
2. <mark style="background-color:green;">**OP8110-3**</mark> <mark style="background-color:green;"></mark><mark style="background-color:green;">or</mark> <mark style="background-color:green;"></mark><mark style="background-color:green;">**OP8110-6**</mark> <mark style="background-color:green;"></mark><mark style="background-color:green;">(OP8110 amplifier settings tab - number and amplifier model depend on the test bench model)</mark>
3. <mark style="background-color:green;">Interface Driver</mark>
4. <mark style="background-color:green;">Firmware Features</mark>

## Mask parameters <a href="#sidebar-for-parameters" id="sidebar-for-parameters"></a>

### Parameters

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2Fb2FqkDC4D5M9x4RDivu0%2Fimage.png?alt=media&amp;token=47581f6d-d304-4278-89c1-3af345083f66" alt="" width="306"><figcaption></figcaption></figure>

<table><thead><tr><th width="223.6666259765625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Parallel Operation</strong><br></td><td><p>These parameters are related to the <a href="https://www.opal-rt.com/docs/op1400pr/op1400pr-overview/description-and-components.md#op1400pr-phil-test-bench-models">test bench model</a>.</p><ul><li><p><strong>LP Busbar</strong> check box:</p><ul><li><p><strong>Check</strong> if an <a href="https://www.opal-rt.com/docs/op1400pr/op1400pr-overview/description-and-components/lp-bus-bar-module.md"><strong>LP bus bar module</strong></a> is <strong>present</strong>.</p><ul><li>If checked, select the bus bar configuration type: <strong>AC</strong> or <strong>DC</strong></li></ul></li><li><strong>Uncheck</strong> if <strong>no LP bus bar</strong> module is present.</li></ul></li><li><p><strong>HP Busbar</strong> check box:</p><ul><li><p><strong>Check</strong> if an <a href="https://www.opal-rt.com/docs/op1400pr/op1400pr-overview/description-and-components/hp-bus-bar-modules.md"><strong>HP bus bar module</strong></a> is <strong>present</strong>.</p><ul><li>If <strong>checked</strong>, select the bus bar configuration type: <strong>AC</strong> or <strong>DC</strong></li></ul></li><li><strong>Uncheck</strong> if <strong>no HP bus bar module is present</strong>.</li></ul></li></ul></td></tr><tr><td><strong>Configuration-01</strong></td><td><p>This parameter is <strong>available</strong> only if <strong>at least one bus bar</strong> (LP or HP) is <strong>checked</strong>. If none is checked it will display <strong>N/A</strong> (not available).</p><ul><li><p><strong>BusBar</strong> field:</p><ul><li>If <strong>one bus bar box</strong> is checked, <strong>LP</strong> or <strong>HP</strong> will be displayed in this field depending on the selected bus bar.</li><li>If the <strong>two bus bar boxes</strong> are checked, <strong>HP will be displayed</strong> in this field. <strong>LP</strong> will be displayed i<strong>n the Configuration-02 BusBar field</strong>.</li></ul></li><li><strong>Config</strong> drop-down menu: Select the appropriate choice according to your system hardware configuration.</li></ul></td></tr><tr><td><strong>Configuration-02</strong></td><td><p>This parameter is <strong>available only if the two bus bar boxes (LP and HP) are checked</strong>.</p><ul><li><p><strong>BusBar</strong> field:</p><ul><li>If one or none of the BusBar boxes is checked, it will display <strong>N/A</strong> (not available).</li><li>If the <strong>two bus bar boxes</strong> are checked, <strong>LP</strong> will be displayed in this field. HP will be displayed in the Configuration-01 BusBar field.</li></ul></li><li><strong>Config</strong> drop-down menu: Select the appropriate choice according to your system hardware configuration.</li></ul></td></tr><tr><td><strong>Reference Input</strong></td><td><p><strong>Select</strong> the <strong>type of reference input</strong> in the drop-down menu:</p><p></p><ul><li><strong>Internal :</strong> The UI has an <strong>internal signal generation block</strong> that provides <strong>three-phase signals</strong> to the <strong>amplifier groups</strong>. Based on the predefined configuration selected, these signals are automatically routed to the respective amplifier groups.</li><li><strong>External :</strong> <strong>Users can provide reference signals from the RT-LAB model</strong> (CPU-based) to the respective amplifier groups, using the input ports provided on the UI. When <strong>external reference</strong> is selected, the <strong>UI displays the signal names on the input port</strong> for which references are supposed to be provided.</li></ul><p><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FW8VIB880vHFK5yHUP7Ng%2Fimage.png?alt=media&amp;token=a05e70d0-0377-4001-974d-63a3344b4fe0" alt="" data-size="original"></p></td></tr><tr><td><strong>Driver Interface</strong></td><td><p>The <strong>OP1400PR-60</strong> UI supports both<sup>*</sup> <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/analog-digital-and-sfp-ios/s-function-workflow"><strong>S-function</strong></a> (s-Fun) and <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/analog-digital-and-sfp-ios/opal-rt-board-workflow?select=message,advanced,node,dab,cap"><strong>OPAL-RT Board</strong></a> (RT-LAB v2025.4+) driver interfaces. The settings for the respective interface are shown in <strong>Interface Driver tab</strong> details.</p><p></p><p>* <strong>Note</strong>: All <strong>client models</strong> are delivered in the <strong>S-Function workflow</strong> with <strong>RT-LAB</strong>, <strong>except for the following scenarios</strong>:</p><ul><li>The client model uses a <strong>simulator</strong> that contains an <strong>Artix-7 FPGA</strong> (exclusive to the OPAL-RT Board workflow).</li><li>The client model uses a <strong>MuSE</strong> <strong>connection</strong> (exclusive to the OPAL-RT Board workflow).</li><li>The client <strong>model</strong> is in <strong>HYPERSIM</strong> (exclusive to the OPAL-RT Board workflow).</li></ul></td></tr><tr><td><strong>Amplifier</strong></td><td><p>Depending on the test bench model, the <strong>available amplifiers and their groups</strong> are liste in this section.</p><p></p><ul><li><strong>Check</strong> or <strong>uncheck</strong> a <strong>group checkbox</strong> to <strong>enable</strong> or <strong>disable</strong> the group.</li></ul></td></tr></tbody></table>

### Tabs <a href="#amplifiers" id="amplifiers"></a>

{% tabs %}
{% tab title="#n OP8110-# (amplifiers)" %}

#### #n OP8110-# tabs

There are as many **amplifier tabs** as there are amplifiers in the test bench. They are numburered #1, #2 or #3 followed by the amplifier model number: OP8110-3 or OP8110-6.

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FZBLV194LHQjvr1g1qr7j%2Fimage.png?alt=media&amp;token=8b3b8586-5df2-4dbf-81c0-a7bece35ab01" alt="" width="563"><figcaption></figcaption></figure>

**Global parameters**

Depending on the amplifier model, one or two GROUP MODE parameter are displayed in this section.

The **GROUP MODE parameter** define the **operating mode** of each **amplifier group**, where **GROUP 1** consists of the **first three amplifier outputs (L1, L2, L3)** and **GROUP 2** consists of the **last three (L4, L5, L6)**.

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FamPoMipxupumsu9FX3xN%2Fimage.png?alt=media&amp;token=bd27058a-2636-491a-988e-7743aa8ba7d5" alt="" width="563"><figcaption></figcaption></figure>

For each group, **select the amplifier group mode** in the drop down list.

* **INDEPENDENT:** In this mode **each amplifier output operates independently**; each can be **enabled** or **disabled individually** and given a **reference voltage** which it will output with respect to its associated neutral terminal (e.g., L1 to N1, L2 to N2, and L3 to N3).
* **DIFFERENTIAL:** In this mode **the first two leg outputs** of **each corresponding group** **(L1 and L2** for **group 1,** or **L4 and L5** for **group 2**) operate together to **generate a differential voltage** either (**AC** or **DC**).
  * For example, in differential mode, a reference of 100 V<sub>DC</sub> given to amplifier #1 will produce an output voltage of 100 V<sub>DC</sub> measured across amplifier outputs L1 and L2.
  * If **DIFFERENTIAL** is seclectd, select the type of current: **AC** or **DC**

**Group parameters**

Depending on the amplifier model, **one or two sections** are displayed

* **OP8110-3**
  * GROUP1\_PARAMETERS
* **OP8110-6**
  * GROUP1\_PARAMETERS
  * GROUP2\_PARAMETERS
* **Set** the **group parameters** for **each groups**.

<table><thead><tr><th width="253">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Enable Mode Using</strong></td><td><p>This parameter sets the <strong>enabling/disabling mode</strong> for <strong>each group</strong> of <strong>each OP8110 amplifier</strong> present in the test bench.</p><p></p><ul><li><strong>GUI OUTPUT ENABLE</strong>: The <strong>amplifier group output</strong> is enabled and disabled from the <a href="https://www.opal-rt.com/docs/op1400pr/operate-the-test-bench/control-and-monitor-the-test-bench.md#main-panel-menu"><strong>Dashboards Panel</strong></a>.</li><li><p><strong>MODEL OUTPUT ENABLE</strong>: The <strong>amplifier group output</strong> is <strong>enabled</strong> and <strong>disabled</strong> from the <strong>model through the “Amp#_Ctrl” input</strong> of the <strong>block</strong> (# is the amplifier number: 1, 2 or 3).<br><br>These signals are sent to the "A<strong>mp#_Ctrl</strong>" port.</p><ul><li><strong>ResetAll</strong>: Reset amplifier signal.</li><li><strong>ExternalFault</strong>: External fault trigger signal.</li><li><strong>EnableG1DCBus</strong>: Signal to <strong>enable</strong> or <strong>disable</strong> the <strong>group 1 DC bus</strong>.</li><li><strong>EnableG2DCBus</strong>: Signal to <strong>enable</strong> or <strong>disable</strong> the <strong>group 2 DC bus</strong> (OP8110-6 amplifier model only).</li><li><strong>L1_En</strong>, <strong>L2_En</strong>, <strong>L3_En</strong>: Signals to <strong>enable</strong> or <strong>disable individual lines</strong> L1, L2, and L3.</li><li><strong>L4_En</strong>, <strong>L5_En</strong>, <strong>L5_En</strong>: Signals to <strong>enable</strong> or <strong>disable individual lines</strong> L4, L5, and L6 (OP8110-6 amplifier model only).</li></ul></li></ul><p>The signals that are supposed to be fed to the amplifier control input are shown in the figures below.</p><p></p><p>Note that the <strong>signal names and the sequence</strong> are <strong>fixed</strong>; they should <strong>match exactly</strong> as shown in the figures below.</p><p></p><p>Signal names and sequence for OP8110-3 amplifier.</p><p><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FC6P0kjWpmJK9c9D0XlfD%2Fimage.png?alt=media&amp;token=3c6cd88c-0d9a-47ab-889c-225f6b0c2939" alt="" data-size="original"><br></p><p>Signal names and sequence for OP8110-6 amplifier.<br><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FY9Uff2HFtDCVgy88dDxz%2Fimage.png?alt=media&amp;token=331cfd05-9b2b-44fa-9a48-6831f0dff316" alt="" data-size="original"></p></td></tr><tr><td><strong>Control Mode</strong></td><td><p>This parameter defines whether the amplifier operates in <strong>VOLTAGE</strong> <strong>control mode</strong> or <strong>CURRENT control mode</strong> (the control mode specified here refers to the inherent FPGA-based control mode of the amplifier).</p><p></p><ul><li><strong>VOLTAGE</strong>: In voltage control mode, the output voltage of the amplifier is regulated to its reference.</li><li><strong>CURRENT</strong>: In current control mode, the output current is regulated to its reference current value.</li></ul><p><strong>Differential mode</strong> (see GROUP MODE parameter above) <strong>only supports inherent FPGA voltage control mode</strong> whereas <strong>independent mode supports both the inherent FPGA voltage and current control modes</strong>.<br><br>However, it is possible to implement <strong>CPU-based current</strong> control <strong>when operating in differential mode</strong>.</p></td></tr><tr><td><strong>Bypass Output Inductance of</strong></td><td><ul><li><strong>Check</strong> a box to <strong>bypass the 75 µH output inductance</strong> of the <strong>respective amplifier output</strong>.</li><li><p><strong>Uncheck</strong> a box to insert this inductance.</p><ul><li><strong>This box should always be unchecked</strong> (i.e., inductance inserted) when <strong>connecting</strong> to a <strong>capacitive load</strong> or an <strong>active</strong> load.</li></ul></li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="InterfaceDriver" %}

#### InterfaceDriver tab <a href="#s-function-driver-interface" id="s-function-driver-interface"></a>

**S-function driver interface**

This are the [**S-function**](https://www.opal-rt.com/docs/rt-lab/configure-ios/analog-digital-and-sfp-ios?select=message,advanced,node,dab,cap#s-function-workflow) driver interface parameters. This panel is editable only if "**sfun**" is selected as the **Driver Interface** in the [**Parameters**](#parameters) (left side bar).

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FLOtqgYJjuNgkUXOtESQw%2Fimage.png?alt=media&amp;token=8fbef5ae-4a44-402a-a51e-c4ff45220219" alt="" width="563"><figcaption></figcaption></figure>

When using the **S-function driver interface**, the user must **configure the port numbers** used to **exchange data with the amplifiers**.

The OP1400PR uses **three port types**:

* **DataIn** transfers data from the RT-LAB model to the FPGA, including SFP In data, reference source signals, FPGA references, and harmonic data.
* **DataOut** transfers SFP Out data.
* **LoadIn** transfers configuration data, specifically amplifier offsets and eHS amplifier gains.

<table data-search="false"><thead><tr><th>Field name</th><th>Port type</th><th>Data width (DWords)</th><th>Port No.*</th></tr></thead><tbody><tr><td colspan="4"><strong>General parameters</strong></td></tr><tr><td><strong>Controler</strong></td><td colspan="3"><strong>'OpCtrl'</strong></td></tr><tr><td><strong>Offset Data Port</strong></td><td>LoadIn</td><td>28</td><td>28</td></tr><tr><td><strong>eHS Amp Gain</strong></td><td>LoadIn</td><td>102</td><td>29</td></tr><tr><td colspan="4"><strong>Amplifier-## parameters</strong><br>There are as many Amplifier-## sections as there are amplifiers on the test bench.</td></tr><tr><td><strong>SFP In Port No.</strong></td><td>DataIn</td><td>25</td><td>13, 14, 15.</td></tr><tr><td><strong>SFP Out</strong></td><td>DataOut</td><td>25</td><td>44, 45, 46.</td></tr><tr><td><strong>Ref. Source, FPGA Ref., Harmonics</strong></td><td>DataIn</td><td>90</td><td>47, 48, 49</td></tr><tr><td></td><td></td><td></td><td></td></tr></tbody></table>

**Opal Board driver interface**

If the Opal Board driver interface is used, each port is provided with the identifiers as shown in the figure.

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FSXm4FFSGgXGDI2d9yyx4%2Fimage.png?alt=media&amp;token=48f60700-9fca-4cf8-a6fa-b807f12811d7" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Firmware Features" %}

#### Firmware Features <a href="#firmware-features" id="firmware-features"></a>

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FAKpBgagVUKrXY0AYbeKo%2Fimage.png?alt=media&amp;token=e34b4a43-5f71-4008-b260-b882b9bd182c" alt=""><figcaption></figcaption></figure>

**Enable CPU Reference Signal Resolution**

* In a typical control setup, reference waveforms are generated in the **CPU** at the configured **CPU step-time (sample time)**.
* When generating **high-frequency reference signals**, the CPU update rate may not provide sufficient time resolution, resulting in reduced waveform fidelity (quantization effect between discrete CPU samples).
* The **CPU reference signal resolution** feature improves the effective reference resolution by performing **interpolation inside the FPGA** between two consecutive CPU reference samples.
* Technical operation
  * CPU generates reference values at: **Tcpu = CPU step-time**.
  * FPGA receives two consecutive CPU reference samples: **Ref\[k]** and **Ref\[k+1]**.
  * FPGA interpolates intermediate reference points at the FPGA step-time, generating a higher resolution reference output. This provides a **smoother and more accurate waveform**, **especially for higher frequency references**, without requiring a reduction in CPU step-time.
* Enable/Disable Behavior
  * This feature can be enabled or disabled either from this tab or **during runtime** from the **Dashboard** (Main Panel > [FW Features tab](https://www.opal-rt.com/docs/op1400pr/operate-the-test-bench/control-and-monitor-the-test-bench.md#fw_features-tab)).

**Enable Data Recording**

* The **Data Recording** feature enables high-resolution capture of amplifier measurement data directly in the FPGA for post-fault analysis and troubleshooting.
* Technical operation
  * Amplifier measurement **signals are sampled in the FPGA** at a **fixed rate** of **1.25 µs**
  * Recorded data is transferred **from FPGA to CPU**
  * Data **recording** is **automatically triggered** upon **AC output fault** or **global fault**.
* Before building the model, the user must
  * **Enable** the **Data Recording feature** in the **OP1400PR UI** (this tab).
  * Provide the required **Data Out port numbers** for transferring recorded data to the CPU.

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FoylZzIsnsu9MjxgVawli%2Fimage.png?alt=media&amp;token=abba2a00-9785-4f4a-8c40-18f428fa36f5" alt="" width="518"><figcaption><p>Only displays when Enable Data Recording is checked</p></figcaption></figure>

**Harmonic Injection**

* <mark style="background-color:yellow;">The</mark> <mark style="background-color:yellow;"></mark><mark style="background-color:yellow;">**Harmonic Injection**</mark> <mark style="background-color:yellow;">**feature**</mark> <mark style="background-color:yellow;"></mark><mark style="background-color:yellow;">allows the user to superimpose harmonic components onto the three-phase reference signals.</mark>
* <mark style="background-color:yellow;">Technical operation</mark>
  * <mark style="background-color:yellow;">Up to</mark> <mark style="background-color:yellow;"></mark><mark style="background-color:yellow;">**six (6) harmonic components**</mark> <mark style="background-color:yellow;"></mark><mark style="background-color:yellow;">can be added.</mark>
  * <mark style="background-color:yellow;">Harmonics are applied to the</mark> <mark style="background-color:yellow;"></mark><mark style="background-color:yellow;">**three-phase reference signals**</mark>
  * <mark style="background-color:yellow;">Harmonic configuration is maintained separately for each group (Group1 and Group2)</mark>
  * <mark style="background-color:yellow;">Users can Enable/Disable</mark> <mark style="background-color:yellow;"></mark><mark style="background-color:yellow;">**from the Prime UI or from the dashboard during runtime.**</mark>

| **Feature**                    | **Purpose**                                                  | **Where it runs**           | **Can enable during runtime?** | **Requires model rebuild?** |
| ------------------------------ | ------------------------------------------------------------ | --------------------------- | ------------------------------ | --------------------------- |
| **CPU Resolution Improvement** | Improve reference waveform resolution at high frequency      | FPGA interpolation          | Yes                            | No                          |
| **Data Recording**             | Capture amplifier measurements at 1.25 µs for fault analysis | FPGA capture + CPU transfer | No                             | Yes                         |
| **Harmonics Injection**        | Add up to 6 harmonics to 3-phase references per group        | Firmware/FPGA               | Yes                            | No                          |
| {% endtab %}                   |                                                              |                             |                                |                             |
| {% endtabs %}                  |                                                              |                             |                                |                             |

## <mark style="background-color:yellow;">Test Bench Specific Settings</mark> <a href="#test-bench-specific-settings" id="test-bench-specific-settings"></a>

<mark style="background-color:yellow;">OP1400PR-60 UI</mark>![OP1400PR\_60 UI and Mask.png](blob:https://opal-rt.atlassian.net/8d81a4a1-dccc-4f76-8990-da97311c40a5#media-blob-url=true\&id=369d8fdb-74a9-44f7-8970-4287a3749899\&collection=contentId-2390491137\&contextId=2390491137\&mimeType=image%2Fpng\&name=OP1400PR_60%20UI%20and%20Mask.png\&size=296053\&width=503\&height=260\&alt=OP1400PR_60%20UI%20and%20Mask.png\&clientId=61bad431-3370-4657-80b2-d23f748dc0c2)*<mark style="background-color:yellow;">OP1400PR-60 User Interface block and its mask</mark>*

### <mark style="background-color:yellow;">**Parallel Operation**</mark> <a href="#parallel-operation.1" id="parallel-operation.1"></a>

<mark style="background-color:yellow;">When both LP and HP busbars are selected the first configuration is set to HP busbar and the second one to the LP bus bar.</mark>

### <mark style="background-color:yellow;">**Predefined configuration selection**</mark> <a href="#predefined-configuration-selection" id="predefined-configuration-selection"></a>

<mark style="background-color:yellow;">OP1400PR-60 UI allows you to set two predefined configurations based on the available LP/HP busbar with the test bench. The set of predefined configurations supported in second is based on the predefined configuration selected on the first. The maximum power allowed with two configurations will not exceed 30 kW.</mark>

#### <mark style="background-color:yellow;">**Configuration-1**</mark> <a href="#configuration-1" id="configuration-1"></a>

| **AC**                                                                                         | **DC**                                                                  |
| ---------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| <p>None<br>10kW120V<br>15kW120V<br>20kW120V<br>25kW120V<br>30kW120V<br>10kW240V<br>20kW240</p> | <p>None<br>10kW400V<br>15kW400V<br>20kW400V<br>25kW400V<br>30kW400V</p> |

#### <mark style="background-color:yellow;">**Configuration-2**</mark> <a href="#configuration-2" id="configuration-2"></a>

| **Config-01**                                                            | **10kW120V/400V**                               | **15kW120V/400V**                   | **20kW120V/400V**       | **25kW120V/400V** | **30kW120V/400V** | **10kW240V**                                                                            | **20kW240V** |
| ------------------------------------------------------------------------ | ----------------------------------------------- | ----------------------------------- | ----------------------- | ----------------- | ----------------- | --------------------------------------------------------------------------------------- | ------------ |
| <p><strong>Config-02 Listed (AC)</strong><br><strong>(120V)</strong></p> | <p>None<br>10kW120V<br>15kW120V<br>20kW120V</p> | <p>None<br>10kW120V<br>15kW120V</p> | <p>None<br>10kW120V</p> | None              | None              | <p>None<br>(if second busbar selected)</p><p>10kW240V<br>(Only one busbar selected)</p> | None         |
| <p><strong>Config-02 Listed (DC)</strong><br><strong>(400V)</strong></p> | <p>None<br>10kW400V<br>15kW400V<br>20kW400V</p> | <p>None<br>10kW400V<br>15kW400V</p> | <p>None<br>10kW400V</p> | None              | None              | N/A                                                                                     | N/A          |

&#x20;

[^1]: User interface


---

# 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/op1400pr/supplementary-operations/op1400pr-nn-ui-block.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.
