> 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/op8120/op812x-mscc-conditioning-modules/op8124-voltage-amplifier-150-v-1-ma-4-channels-legacy.md).

# OP8124 Voltage Amplifier 150 V - 1 mA - 4 channels (Legacy)

{% hint style="danger" %}
**This is a legacy product** compatible with the **OP8121 Gen 1 chassis** only.\
Please contact your [**local sales representative**](https://www.opal-rt.com/contact-us/#offices-and-distributors) for more information.
{% endhint %}

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

The **OP8124 MSCC** module converts four standard ±16 Vpeak voltages into four high-voltage outputs up to 150 V<sub>rms</sub>/1 mA<sub>rms</sub>.

## Features <a href="#features" id="features"></a>

* LED fault indicators.
* Current and thermal protection
* Front screw terminal connectors
* Easy installation (in chassis).

The OP8124 module requires external power of ±24 Vdc @ 250 mAdc and 12 Vdc @ 275 mAdc that is included with the OP8120 chassis.

## Applications <a href="#applications" id="applications"></a>

* Excitation voltage (grid, electrical machine, etc.) emulation
* High-voltage amplifier

## OP8124 interface <a href="#op8124-interface" id="op8124-interface"></a>

<figure><img src="https://content.gitbook.com/content/re3d8M3OpCkdPOndYEMH/blobs/NGH6yegArQrvTykqoJyX/image.png" alt=""><figcaption><p>OP8124 Interface</p></figcaption></figure>

### Status LED table <a href="#status-led-table" id="status-led-table"></a>

Each channel has two LEDs, one <mark style="color:red;">**red**</mark> and one <mark style="color:$success;">**green**</mark>. The following table explains what the channel status is, according to the LED conditions.

<figure><img src="https://content.gitbook.com/content/re3d8M3OpCkdPOndYEMH/blobs/ZK6CxRvUo8nsd7rZKtyK/image.png" alt=""><figcaption></figcaption></figure>

| <mark style="color:$success;">**Green LED**</mark> | <mark style="color:red;">**Red LED**</mark> | **Status** |
| -------------------------------------------------- | ------------------------------------------- | ---------- |
| <mark style="color:$success;">On</mark>            | Off                                         | Activated  |
| <mark style="color:$success;">On</mark>            | <mark style="color:red;">On</mark>          | Fault      |

### Power LED description <a href="#power-led-description" id="power-led-description"></a>

**Each module has 2 power LEDs:**

* When the left LED is on, it indicates that the internal ±15 Vdc power is functioning properly.
* When the right LED is on, it indicates that the ±24 Vdc power is functioning properly.

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

### General specifications <a href="#general-specifications" id="general-specifications"></a>

| **Product name**                                                     | OP8124 Signal Conditioning Module          |
| -------------------------------------------------------------------- | ------------------------------------------ |
| **Part number**                                                      | 126-0421                                   |
| <p><strong>Power supply</strong><br>(provided by OP8120 chassis)</p> | <p>±24 Vdc @ 250 mA<br>12 Vdc @ 275 mA</p> |
| **Protection**                                                       | Current and thermal protection             |
| **Dimensions**                                                       | 23.43 × 10 × 5 cm (9.22” × 3.94” × 1.96”)  |

### Analog inputs <a href="#analog-inputs" id="analog-inputs"></a>

| **Connectors**                       | DB37             |
| ------------------------------------ | ---------------- |
| **Coupling**                         | AC, differential |
| **Differential input voltage range** | ±16 V            |
| **Differential input resistance**    | 20 kΩ            |

### Analog outputs <a href="#analog-outputs" id="analog-outputs"></a>

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Connectors</strong></td><td>Screw terminals</td></tr><tr><td><strong>Coupling</strong></td><td>DC, referenced to its HVGND</td></tr><tr><td><strong>Voltage range</strong></td><td>±150 Vrms<br>Gain: 21.5 ±1% at no load</td></tr><tr><td><strong>Max current</strong></td><td>1 mA RMS</td></tr><tr><td><strong>Output impedance</strong></td><td>4860 ±10%</td></tr><tr><td><strong>Operating frequency range</strong></td><td>40 Hz - 8.5 kHz (at -3 dB)</td></tr><tr><td><strong>Phase shift</strong></td><td>≤100° at full load (at -3 dB)</td></tr><tr><td><strong>Voltage regulation</strong></td><td>9.2% at full load</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/op8120/op812x-mscc-conditioning-modules/op8124-voltage-amplifier-150-v-1-ma-4-channels-legacy.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.
