> 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/ni-slsc-modules/digital-bidirectional-modules/op8926-description.md).

# OP8926 Description

32-channel digital input and output (DIO) conditioning module with optional fault insertion unit (FIU).

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2FtV6SxYPVyBMcjntk52P2%2Fimage.png?alt=media&amp;token=4a546f6d-0433-45c6-9757-82c5bddd494c" alt=""><figcaption></figcaption></figure>

The **OP8926** SLSC module is a **32 high-speed digital input and output** module with an optional fault insertion unit (FIU).

## Key features <a href="#key-features" id="key-features"></a>

* Signal conditioning and FIU on a single board.
* Low latency < 90 ns, high resolution of 130 ns
* Digital In: Programmable threshold 0-30 V
* Digital Out maximum current: 50 mA per channel (550 mA per Vuse&#x72;**\***)
* Fault insertions unit FIU as an option

\* For more information about the use of **Vuser** and **Vrtn** please refer to this article in the OPAL-RT knowledge base : [Powering DB37 Boards for Digital Output Modules](https://portal.opal-rt.com/Knowledge-Base/Article/?id=3bb5144d-9356-ef11-bfe3-002248b1d264).

## Module architecture <a href="#board-architecture" id="board-architecture"></a>

The module features a combination of 32 input and output channels and a set of relays adding fault insertion capability for each signal.

The general layout of the board is as follows, with the **front interface connectors** on the **left** and the **SLSC backplane connectors** on the **right**.

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2FoERSVr6gqxnAmzTCFPzt%2Fimage.png?alt=media&amp;token=322f25e1-370c-496f-8130-39bcf1cbed2e" alt=""><figcaption></figcaption></figure>

\
The input/output conditioning is managed by the OPAL-RT [OP5369](https://www.opal-rt.com/docs/op53xx/digital-bidirectional-modules/op5369-description.md) I/O module.

A CPLD (Complex Programmable Logic Device) is used to configure the fault insertion unit (FIU) section and the OP5369 module.  It is responsible for the communication of the SLSC module within the NI environment for identification, error reporting, etc. It also receives configuration from the software and applies it to the FIU and to some of the I/Os.

The [FIU specification and topology](https://www.opal-rt.com/docs/ni-slsc-modules/op8900-slsc-modules-overview/modules-and-fiu-description.md#fault-insertion-unit-fiu-description) are common to all OP8900 boards.

## Input channel architecture <a href="#input-channel-architecture" id="input-channel-architecture"></a>

### Technical specifications <a href="#technical-specifications" id="technical-specifications"></a>

* Voltage range 0-30 V
* Protection ±50 VDC et ±50 VAC
* Zin > 100kOhm
* Programmable Vih and Vil on each bank 120 mV step  from  0 V to 30 V

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2F0AIEsOKesEdO4OD43UDr%2Fimage.png?alt=media&amp;token=723c7a2f-763d-49c8-bd7b-b4d5b8b30ef0" alt=""><figcaption></figcaption></figure>

## Output channel architecture <a href="#output-channel-architecture" id="output-channel-architecture"></a>

### Technical specifications <a href="#technical-specifications" id="technical-specifications"></a>

* Single-Ended Output Voltage 5-24 V, external Vuser
* An internal 4.5 V Vuser is available, Imax 300 mA, for banks 1 and 2, and 300 mA for banks 3 and 4.
* Short circuit protection output
* Current 50 mA per channel and 350 mA per Vuser
* Initial value: Low

{% hint style="info" %}
For more information about the use of **Vuser** and **Vrtn** please refer to this article in the OPAL-RT knowledge base : [Powering DB37 Boards for Digital Output Modules](https://portal.opal-rt.com/Knowledge-Base/Article/?id=3bb5144d-9356-ef11-bfe3-002248b1d264).
{% endhint %}

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2FBFlPTJVR2Y0jNzqcGPCR%2Fimage.png?alt=media&amp;token=74829441-98ff-4378-9238-f111ff5b8234" alt=""><figcaption></figcaption></figure>

## Available configurations <a href="#op8910-configurations" id="op8910-configurations"></a>

Two assemblies of the OP8910 are available with or without the FIU section populated.

<table><thead><tr><th width="140">Vendor Part #</th><th width="228.6666259765625">Description</th><th width="108.666748046875">Digital In/out</th><th>Digital Out Type</th><th>FIU</th></tr></thead><tbody><tr><td><strong>OP8926-F</strong></td><td><p><strong>32 Dout FET with FIU SLSC Conditioning Board</strong></p><p>32-channel configurable in or out in groups of 8</p></td><td>32</td><td>FET</td><td>32 single-ended FIU</td></tr><tr><td><strong>OP8926-N</strong></td><td><p><strong>32 Dout FET SLSC Conditioning Board</strong></p><p>32-channel configurable in or out in groups of 8</p></td><td>32</td><td>FET</td><td>N/A</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/ni-slsc-modules/digital-bidirectional-modules/op8926-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.
