> 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/hardware-interface.md).

# Hardware Interface

## Face plate <a href="#face-plate" id="face-plate"></a>

The face plate provides two **HDB44 connectors** (J1, J2), one **4-pin Molex connector** (J3, if present), and wo **LEDs**.

{% columns %}
{% column %}

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2FPs7GKxR8GZevQnaMnNEF%2Fimage.png?alt=media&amp;token=11c1e46a-975b-4868-99a0-b7f7c2346a69" alt="" width="130"><figcaption><p>OP8926-F</p></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="https://2438675663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrYR5dUDCbEE35IWamogp%2Fuploads%2FvOk5yfyjTZ4WZXUB6I0u%2Fimage.png?alt=media&amp;token=e5c4c05c-9a43-4e60-ae1f-7725be98c86a" alt="" width="130"><figcaption><p>OP8926-N</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

## J1 and J2 connectors <a href="#j1-j2-connectors" id="j1-j2-connectors"></a>

The 32 digital I/O signals are routed to both J1 and J2 connectors. This allows, for example, splitting the input and output signals into two different cables.

If the harnessing uses only one connector, it is recommended to use J2.

See the page [Pin Assignment](https://www.opal-rt.com/docs/ni-slsc-modules/digital-bidirectional-modules/op8910-description/pin-assignment.md).

### J1-J2 recommended mating connector <a href="#j1-j2-recommended-mating-connector" id="j1-j2-recommended-mating-connector"></a>

| Manufacturer | Part number     | Description                    |
| ------------ | --------------- | ------------------------------ |
| Norcomp      | 180-044-173L000 | D-SUB Housings                 |
| Norcomp      | 180-001-170L001 | Crimps for 24 to 26 wire gauge |
| Norcomp      | 979-025-030R121 |                                |

## J3 connector <a href="#j3-connector" id="j3-connector"></a>

J3 is used to connect the two external reference voltages for fault insertion.&#x20;

### J3 mating connector with crimps <a href="#j3-mating-connector-with-crimps" id="j3-mating-connector-with-crimps"></a>

| Manufacturer | Part number        | Description                    |
| ------------ | ------------------ | ------------------------------ |
| Molex        | 538-172258-1004    | Headers and Wire Housings      |
| Molex        | 538-172253-3023-LP | Crimps for 16 to 18 wire gauge |

## LEDs definition <a href="#leds-definition" id="leds-definition"></a>

<table><thead><tr><th valign="middle">LED Name</th><th>LED Behavior</th><th>Definition of Behavior</th></tr></thead><tbody><tr><td valign="middle">Power (<strong>PWR</strong>)</td><td>Off</td><td>No power present on module (from SLSC Interface nor external power)</td></tr><tr><td valign="middle">Power solid <mark style="color:$success;"><strong>green</strong></mark></td><td>Power good state</td><td></td></tr><tr><td valign="middle">Power blinking <mark style="color:red;"><strong>red</strong></mark></td><td>Module fault state</td><td></td></tr><tr><td valign="middle">Ready (<strong>RDY</strong>)</td><td>Off</td><td>Module is not powered or in Rdy/Rst# is driven low by the chassis.</td></tr><tr><td valign="middle">Ready solid <mark style="color:$success;"><strong>green</strong></mark></td><td>Module in default configuration, recognized by the chassis and ready to configure (the Rdy/Rst# signal has been pulled high by the chassis.)</td><td></td></tr><tr><td valign="middle">Ready linking <mark style="color:$warning;"><strong>amber</strong></mark></td><td>Module is active (in a non-default configuration or communicating<br>with the chassis).</td><td></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/hardware-interface.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.
