> 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/op8900-slsc-modules-overview/modules-and-fiu-description.md).

# Modules and FIU Description

## Module description

The OPAL-RT OP8900 SLSC module series helps HIL users maximize time and resources with configurable signal conditioning. It ensures the right signal level and type, with support for voltage level shifting, scaling, integrated filtering, and impedance matching.

Each module includes an onboard flexible fault insertion unit (FIU). It provides full relay control during testing and lets you apply faults to the device under test (DUT) through NI VeriStand.

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2FXOan60hv9oa9NlcIwGvv%2Fimage.png?alt=media&amp;token=ec05c843-dd64-47e1-a85a-773258ec6b93" alt=""><figcaption></figcaption></figure>

## Form factor <a href="#inlineextension-form-factor" id="inlineextension-form-factor"></a>

The SLSC boards are 144.32 mm tall (4U) by 281.9 mm deep. For detailed information see [NI white paper on SLSC architecture](https://www.ni.com/en-us/innovations/white-papers/17/using-the-slsc-architecture-to-add-additional-elements-to-the-si.html#section-425164983).

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

### Digital board (OP891x/OP892x) <a href="#digital-board-op891x-and-op892x" id="digital-board-op891x-and-op892x"></a>

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2FWxrZCpkwazJh6j8f56TW%2Fimage.png?alt=media&amp;token=b807f60d-128e-4573-b599-beab24fb1ee6" alt=""><figcaption></figcaption></figure>

### Analog board and passthrough (OP893x/OP8940) <a href="#analog-board-and-passthrough-op893x-op8940" id="analog-board-and-passthrough-op893x-op8940"></a>

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2FtIkFjJ0oNbciqhzFyfHp%2Fimage.png?alt=media&amp;token=970f8f81-b252-48c6-980e-8e84685d4b19" alt=""><figcaption></figcaption></figure>

## Fault Insertion Unit (FIU) description

### Topology <a href="#topology" id="topology"></a>

The **F**ault **I**nsertion **U**nit (FIU) section of the OP8900 boards consists of **seven relays per differential pair** of signals, for a total of 112 relays (7 relays x 16 differential pairs).

Each relay can be controlled individually.

For each group of 7 relays, the **possible faults** are:

* **Open-circuit** of the pair
* **Short-circuit** of the two signals of the pair
* Two **fault injection**, with two user-supplied reference voltages (VBusA \[VBUS-1] and VBusB \[VBUS-2]), for each signal of the pair.

{% hint style="info" %}
**VBusA = VBUS-1**\
**VBusB = VBUS-2**

VBusA and VBus are used in the software\
VBUS-1 and VBUS-2 are marked on the module faceplates
{% endhint %}

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2FIOOkdWuB6BZMvFi7QiH5%2Fimage.png?alt=media&amp;token=85f531af-c51c-408c-bfa4-ce029dfa61dd" alt=""><figcaption></figcaption></figure>

Note that this diagram only shows one channel.

## Embedded protections <a href="#embedded-protections" id="embedded-protections"></a>

The following protections are implemented:

* In the default state, all relays are open.
* All channels are updated simultaneously.
* VBusA (VBUS-1) and VBusB (VBUS-2) cannot be connected on the same channel at the same time: VBusA (VBUS-1) and VBusB (VBUS-2) cannot be shorted.
* When the **Signal +** and **Signal -** are shorted together, only one other fault is allowed for VBusA (VBUS-1) or VBusB (VBUS-2) on that channel pair.
* Relays on a channel are always open before closing any other.

{% hint style="danger" %}
The maximum **peak current per relay is 1 A**. There is **no over-current protection**.
{% endhint %}

The relay technology used in the FIU allows a higher density and has a fast response time (< 0.5ms). However, this technology is very sensitive to peak current, even for a few microseconds. It is the customer's responsibility to limit the peak current by adding the resistor on the signal or VBus based on the capacitor and cabling present on the circuit.

Even if the power supply on the VBus is limited to 0.1 A, a capacitor is present at the output and the peak current can easily > 5A before the internal current limit kicks in, creating permanent damage to the relay.

If a relay is broken in short mode, an RMA can be issued to repair the module. Please contact your[ local representative](https://www.opal-rt.com/contact-us/#offices-and-distributors) or [OPAL-RT technical support](https://www.opal-rt.com/support/).

If the customer has access to a technician with valid IPC-610 certification and experience with a rework of through-hole lead-free and no-clean soldering, OPAL-RT authorizes this technician to replace once a faulty relay.

Here is a short recap of the process:

1. Remove the SLSC module out of the SLSC chassis
2. With a basic multimeter measure the impedance between pins 1 and 4 of all 112 relays. If < 100 R, the relay needs to be changed.
3. Unsolder the faulty relay. **No-clean flux can be used**.
4. Solder a new relay: Comus International 3570-1419-054.

{% hint style="info" %}
For output signal (analog or digital), always open the load relay (relay in series of the signal) when creating faults to prevent damage on the output circuit.
{% endhint %}

{% hint style="danger" %}
Even if some protection is built-in on the output circuit to prevent damage, creating a direct fault to VBus with higher voltage can create **permanent damage**.
{% 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/ni-slsc-modules/op8900-slsc-modules-overview/modules-and-fiu-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.
