> 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/op1400pr-overview/description-and-components/output-interface-module.md).

# Output Interface Module

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

The **Output Interface module** allows users to safely and conveniently interface external DUT[^1]s with the [OP8110 amplifiers](https://www.opal-rt.com/docs/op1400pr/op1400pr-overview/description-and-components/op8110-4q-power-amplifier.md).

## Key features

* **Three sets** of **three-phase** (3W+N) **interface channels** for **external DUT** connection to the [OP8110 amplifiers](https://www.opal-rt.com/docs/op1400pr/op1400pr-overview/description-and-components/op8110-4q-power-amplifier.md) inside the cabinet.
* A rear-panel **Voltage reference**/**Functional ground** banana jack for use in certain configurations to **meet the isolation requirements** of the [OP8110 amplifiers](https://www.opal-rt.com/docs/op1400pr/op1400pr-overview/description-and-components/op8110-4q-power-amplifier.md).

## Specifications <a href="#specifications" id="specifications"></a>

* Maximum steady-state current per phase/neutral line: **22 A**<sub>RMS</sub>
* Maximum voltage (line to chassis): **600 V**<sub>AC</sub> **/ 600 V**<sub>DC</sub>

## Front panel <a href="#front-and-rear-panels" id="front-and-rear-panels"></a>

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2F21P0mIVlVezs32eM8d8Y%2Fimage.png?alt=media&amp;token=7f67ba3f-e928-46dd-93a8-47e6dc4e0baa" alt=""><figcaption></figcaption></figure>

* 3 sets of banana jacks for connection to external DUT(s)
  * L1 (<mark style="color:$danger;">**red**</mark>)
  * L2 (**black**)
  * L3 (<mark style="color:blue;">**blue**</mark>)
  * N (white)

## Rear panel <a href="#functional-overview" id="functional-overview"></a>

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FC8Bhk1j0yqT8pgPhz8It%2Fimage.png?alt=media&amp;token=190bb160-e7bd-4798-9c23-ab64ec0a08d0" alt=""><figcaption></figcaption></figure>

* 3 sets of banana jacks for connection to the OP8110 amplifiers.
  * L1 (<mark style="color:$danger;">**red**</mark>)
  * L2 (**black**)
  * L3 (<mark style="color:blue;">**blue**</mark>)
  * N (white)
* Protective Earth (PE) grounding stud
* Voltage reference/Functional ground banana jack (<mark style="color:green;">green</mark>)

{% hint style="danger" %}
The **protective earth (PE)** connection of the **Device Under Test (DUT)** is the responsibility of the user.&#x20;

Operation of a DUT with exposed conductive parts without a proper **protective earth (PE) connection** may result in an **electric shock hazard**.
{% endhint %}

## Electrical schematic <a href="#electrical-schematic" id="electrical-schematic"></a>

<figure><img src="https://3155739458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzVJdfp93TWLISP6nkqTs%2Fuploads%2FmiAUBvIUx8ok248teZiC%2Fimage.png?alt=media&amp;token=c4b053a9-1467-477a-930f-2ae262a372a1" alt=""><figcaption></figcaption></figure>

[^1]: Device under test


---

# 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/op1400pr-overview/description-and-components/output-interface-module.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.
