> 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/accessories-conditioning-modules/mapping-and-interconnection/op8681-desktop-connection-interface/system-description.md).

# System Description

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2FXFE9MaXqN8xBOhqtTtT5%2Fimage.png?alt=media&amp;token=99fca573-5aab-4176-bc11-92ab3c491354" alt="" width="375"><figcaption></figcaption></figure>

The **OP8681** is a desktop modular mapping box that provides an easily interconnected interface between standard OPAL-RT simulator DB37 connectors and user devices.

The OP8681 can provide 16 channels, divided into four sections of four channels each. Each group of four channels can be configured to use different client-side connectors (BNC, screw terminal, etc.). An LED connector module is also available for signal status monitoring.

The OP8681 is available in two models, **OP8681-1** and **OP8681-2**.

* The **OP8681-1** provides the possibility of adding additional signal conditioning between the DB37 and the connector modules. The conditioning uses OP8E00 mezzanine modules, also referred to as TypeE modules. The four OP8E00 modules of four channels can be of different type, for example, the first set of four channels could be used for ±50A current output, while the remaining channels could be isolated analog outputs.

## **OP8681 - 1 use case example**

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2FMWt1yGAiHtm5NAxo9giz%2Fimage.png?alt=media&amp;token=b83d18e4-a7b9-4916-94e9-f251e9cc6aa3" alt=""><figcaption></figcaption></figure>

* The **OP8681-2** does not use any conditioning boards and serves only as a quick connection interface between standard OPAL-RT simulator DB37 connectors and user devices.

### **OP8681 - 2 use case example**

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2FTng8lTWtZ6oiUuHWc80M%2Fimage.png?alt=media&amp;token=48172d20-fa9c-48b1-9f76-bbb623eaae5e" alt=""><figcaption></figcaption></figure>

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

* One carrier board that can accept up to 4 OP8E00 (Type E) signal conditioning mezzanine boards (OP8681-1 only)
* Four (4) top panel, accepting different connector types (BNC, 2.5A Phoenix)
* Optional LED top panels for monitoring channel activity
* DB37F connectors for quick connections to the simulator and user device (all DB37F share common pin assignments).

## Compatible OP8E00 (Type E) boards <a href="#op8681systemdescription-compatibleop8e00-typee-boards" id="op8681systemdescription-compatibleop8e00-typee-boards"></a>

The following parts are compatible with the OP5330 analog output boards used in an OPAL-RT simulator. See individual board documentation for details.

<table data-header-hidden data-search="false"><thead><tr><th width="134"></th><th width="124"></th><th></th></tr></thead><tbody><tr><td><strong>Flat cable</strong></td><td> 113-0595</td><td>Type E flat cable for passthrough</td></tr><tr><td><strong>OP8E01</strong></td><td>126-0425</td><td>Type E module, proto zone</td></tr><tr><td><strong>OP8E03</strong></td><td>126-0435</td><td>Type E module, current out mode, ±25mA to ±50mA, compliance voltage 14V</td></tr><tr><td><strong>OP8E05</strong></td><td>126-0452</td><td>Type E module, current out mode, ±100 mA, compliance voltage 16V (external power supply required)</td></tr><tr><td><strong>OP8E06</strong></td><td>126-0464</td><td>Type E module, voltage out mode 2ch isolated, 2ch standard output</td></tr><tr><td><strong>OP8E10</strong></td><td>126-0495</td><td>Type E module, 4 isolated analogs out LV (16V)</td></tr><tr><td><strong>OP8E12</strong></td><td>126-0502</td><td>Type E module, snubber, filter and pull-up/down signal</td></tr></tbody></table>

The following parts are compatible with the OP5340 analog input boards used in an OPAL-RT simulator. See individual board documentation for details.

<table data-header-hidden data-search="false"><thead><tr><th width="136"></th><th width="109"></th><th></th></tr></thead><tbody><tr><td><strong>Flat cable</strong></td><td> 113-0595</td><td>Type E flat cable for passthrough</td></tr><tr><td><strong>OP8E01</strong></td><td>126-0425</td><td>Type E module, proto zone</td></tr><tr><td><strong>OP8E02</strong></td><td>126-0426</td><td>Type E module, current input ±25 mA to ±100 mA ( 250 ohms available)</td></tr><tr><td><strong>OP8E04</strong></td><td>126-0428</td><td>Type E module,  high voltage input with buffer (to allow signal monitoring after the attenuator)</td></tr><tr><td><strong>OP8E07</strong></td><td>126-0465</td><td>Type E module, 4 voltage input isolated</td></tr><tr><td><strong>OP8E09</strong></td><td>126-0486</td><td>Type E module, 4 analogs input amplifier buffer (gain > 1)</td></tr><tr><td><strong>OP8E11</strong></td><td>126-0491</td><td>Type E module, current in 0-20 mA isolated</td></tr><tr><td><strong>OP8E12</strong></td><td>126-0502</td><td>Type E module, snubber, filter and pull-up/down signal</td></tr></tbody></table>

{% hint style="info" %}
The **OP8681** connects pin-to-pin with either an OP5330 or OP5340, therefore it is not possible to combine both input and output Type E boards in on OP8681 box.
{% endhint %}


---

# 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/accessories-conditioning-modules/mapping-and-interconnection/op8681-desktop-connection-interface/system-description.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.
