> 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-output-modules/op5352-description.md).

# OP5352 Description

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FhoAoa1ETns4r2M2ykBma%2FOP5352_board.jpg?alt=media&amp;token=cc55b840-3a71-439a-91ff-0204891e38f8" alt="OP5352 board " width="563"><figcaption></figcaption></figure>

The **OP5352** is a **digital output module** designed for OPAL-RT simulators and expansion units. It features multiple output single-ended channels at **5 V (CMOS/TTL)** or **3.3 V (LVTTL)** logic levels, offering reliable and high-speed signals  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 channels grouped into **2 banks** of **16 channels** each.
* Voltage output for each bank is configurable for either 5V (CMOS/TTL Logic ) or 3.3V (LVTTL)
* Signals of each bank are made available to the user at one DB37F connector of the chassis
* Galvanically isolated to real environment signals

## Channel architecture

Each channel implements the circuit shown below:

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2F9jOsAIbpoLheg4Zh1jmx%2FOP5352_architecture.png?alt=media&amp;token=678993df-4b5f-4eca-9cd1-ebb762ff1502" alt="OP5352 architecture" width="563"><figcaption></figcaption></figure>

Each group of 16 channels can be configured for 5V or 3.3V operation, using the jumpers P3 and P4:

{% columns %}
{% column width="66.66666666666666%" %}

| <p><strong>Jumper P3</strong><br>CH00-15 (VIN\_ISO1)</p> | <p>Place jumper over pins 2 and 3 to obtain +5V.</p><p></p><p>Place jumper over pins 1 and 2 to obtain 3V3</p> |
| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| <p><strong>Jumper P4</strong><br>CH16-31 (VIN\_ISO2)</p> | <p>Place jumper over pins 1 and 2 to obtain +3V3.</p><p>Place jumper over pins 2 and 3 to obtain 5V</p>        |
| {% endcolumn %}                                          |                                                                                                                |

{% column width="33.33333333333334%" %}

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FAU8qOmHAc3r9zPfCq0eV%2Fjumper.png?alt=media&amp;token=3fa1951e-9317-4e15-8a3c-49bde6f7ecf6" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

In addition, OPAL-RT provides a DB37 to DB37 prototype board (OP8320-4 - Transmission Line Termination Kit), which, when inserted in the cabling going from the simulator to the external device, allows tuning the impedance of the lines, so the signal quality is optimized. This helps to remove ringing, over or undershoots which can cause false triggering, stair-stepping, delays and loss of noise margin.

{% hint style="danger" %}

### TTL signals are not recommended for long-distance data transmission.&#x20;

We recommend using this board with **cable lengths no longer than 1.5 meters** (5 ft). When using longer lengths, OPAL-RT recommends terminating the lines to avoid over/undershoots or using alternative transmissions, such as differential mode (e.g: LVDS OP5355-3, RS422 OP5356-5 \[5V] or OP5355-3 \[3V3]).
{% 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-output-modules/op5352-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.
