> 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/op5360-description.md).

# OP5360 Description

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FEfoHV00LTjohDEC8IrR0%2FOP5360-board.jpg?alt=media&amp;token=e57f81f4-6756-4691-8243-e48a6df7e3b5" alt="OP5360" width="563"><figcaption></figcaption></figure>

The **OP5360** is a **digital output module** designed for OPAL-RT simulators and expansion units. It features multiple **push-pull digital output** channels compatible with **5–30 V output range**, providing reliable and high-speed signals  for real-time simulation and hardware-in-the-loop (HIL) applications.&#x20;

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.
* 5 to 15V (OP5360-1) or 5 to 30V (OP5360-3) output range&#x20;
* Load current up to 50 mA DC per output sink, or source with no trip action
* Over-voltage and reverse-voltage supply protection
* Short-circuit current limitation
* Operating frequency : DC - 500 kHz

{% hint style="danger" %}

### Legacy product

Please note that we no longer sell the **OP5360-2**.\
The **OP5360-3** is a direct replacement of OP5360-2 without the need to change the bitstream.
{% endhint %}

## Channel architecture

The schematic below represents the electrical circuit of one channel.

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FLm5q1fLVHYver5nijDim%2FOP5360_architecture.png?alt=media&amp;token=4e6a6889-75bc-4362-acd9-9f2b4d489688" alt="OP5352 architecture"><figcaption></figcaption></figure>

The output is referenced to the Vref voltage supplied by the user via a dedicated input pin on the DB37F connector of the chassis in which the module is installed.&#x20;

Each bank of 16 channels can be referenced to a different voltage level.

Two consecutive outputs (for example DOUT\_0 and DOUT\_1, DOUT\_2 and DOUT\_3) may be connected in parallel for double current capability.&#x20;

Use of a damping circuit (a serial resistor-capacitor circuit tied to the GND as close as possible to the unit under test) may be necessary to minimize ringing and over/undershoot depending on the distance between the simulator and the unit under test. The following parameters are usually a good starting point for the RC values: R=150 Ω, C = 100 pF.

## Typical use cases <a href="#typical-use-cases" id="typical-use-cases"></a>

The characteristics of the module make it suitable in simulations of applications such as:

* MOSFET and IGBT switching
* Switch-mode power supplies
* DC-to-DC converters
* Motor control, solar power (photovoltaics)


---

# 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/op5360-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.
