> 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/op53xx/digital-bidirectional-modules/op5367-3-description.md).

# OP5367-3 Description

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FxVSnKkEBhhAU4vf7b7qb%2FOP5367-3.jpg?alt=media&amp;token=4f7de36d-f836-4b21-9fcc-1eb043ec7e18" alt="OP5367-3 board " width="563"><figcaption></figcaption></figure>

The **OP5367-3** is a flexible **Digital Input/Output module** designed for OPAL-RT simulators and expansion units. It features **16 high-impedance Digital Input channels** and **16 Digital Output channels** supporting **logic levels of 5 V (CMOS/TTL)** or **3.3 V (LVTTL)**, providing reliable and high-speed signal interfacing for real-time simulation and hardware-in-the-loop (HIL) applications.

For compatibility information, refer to the [Hardware Platforms Compatibility](https://www.opal-rt.com/docs/op53xx/overview/hardware-platforms-compatibility.md) table.

## Key features

* 32 configurable input/output channels grouped in 4 banks of 8 channels.
* The 32 output channels are configurable for either 5 V ±10% (CMOS/TTL Logic ) or 3.3 V (LVTTL).
* Digital Input programmable threshold 0-42 V per bank
* Digital Output TTL  with max output current: 32 mA/ch or 800 mA total combined
* Low latency < 20 ns, High resolution of 10 ns with 100 MHz FPGA.
* Galvanically isolation to real environment signals provides protection to the simulator from damaging voltages.

## Input channel architecture

* Programmable Vih and Vil on all the range per group of 8
* Zin > 100 kΩ

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FYn1q4EyRWs9rozB0qeg0%2FOP5367-input.png?alt=media&amp;token=df2ede56-af90-4d3b-b717-2e64a4037bd8" alt="OP5367 input architecture"><figcaption></figcaption></figure>

## Output channel architecture

* Single Ended Output voltage, selected by DIP switch, for all output, 3.3 V / 5.0 V (LVTTL, TTL)
* Short Circuit Protection&#x20;
* Protection ±50 V DC/AC, for all channels at the same time
* Theoretical timing resolution: 10 ns for FPGA at 100 MHz

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FXITE4Q0KBNMpGywltECS%2FOP5367-output_schem.png?alt=media&amp;token=2cc1a347-fa12-4922-846e-de12555ef7a1" alt="OP5367-3 output"><figcaption></figcaption></figure>

See the location of the dip switch in the picture below to select the output voltage for +3.3 V (LVTTL) or +5.0 V (TTL) operation.

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FniFFZpcCkXSFChAVkcXK%2FOP5367_switch_voltage.png?alt=media&amp;token=7aff88de-cff4-49b8-8039-36841179b8ae" alt="" width="563"><figcaption></figcaption></figure>

## Typical use cases

The OP5367-3 is ideal for interfacing with devices operating at low voltage.

{% hint style="danger" %}

### TTL signals are not recommended for long-distance data transmission

We recommend using this board with cable lengths no longer than 1.5 meters (5 ft).
{% 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/op53xx/digital-bidirectional-modules/op5367-3-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.
