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

# OP5330 Description

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FzWUKLcpQmxb13SP4QXYr%2Fimage.png?alt=media&amp;token=653e9590-0341-4f48-ad47-b2fb998e1a93" alt="" width="563"><figcaption></figcaption></figure>

The **OP5330** is a high-precision analog output module designed for OPAL-RT simulators and expansion units. It provides multiple single-ended channels with configurable sampling rates and output voltage ranges, making it suitable for a wide range of real-time simulation and hardware-in-the-loop (HIL) applications. The voltage range applies to all channels and can be configured via software. The **OP5330-1** variant supports higher current output, making it ideal for long cable runs, while the **OP5330-3** is optimized for shorter connections or lower current 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

* 16 single-ended analog output channels sampled simultaneously at 1 MSPS, or 8 single-ended analog output channels sampled simultaneously at 2 MSPS
* 16-bit resolution
* Configurable voltage range: ±5 V, ±10 V, ±16 V (default)
* Maximum current per channel: 35 mA (OP5330-1), 15 mA (OP5330-3)
* Factory-calibrated for each voltage range
* OP5330-1K2 variant optimized for traveling wave applications (±4 V output for lower signal/noise ratio)

## Channel architecture

Each channel of the OP5330 module consists of three stages:

1. **Calibration Stage:** Gain DAC and offset DAC apply factory-stored calibration values from onboard EEPROM.
2. **Signal Stage:** Signal DAC converts the simulation output data and combines it with the calibration gain via an operational amplifier.
3. **Output Stage:** Operational amplifier integrates the signal with the calibration offset to produce the final Analog Output.

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2Fz9gqhuueYBIJS3Xe89Jf%2Fimage.png?alt=media&amp;token=1e6fe035-aef6-4140-a2a4-d90f77bae3cf" alt=""><figcaption></figcaption></figure>

* The module uses **8 dual-channel 16-bit DACs**, providing:
  * 16 channels at 1 MSPS (total throughput: 16 MSPS)
  * 8 channels at 2 MSPS (total throughput: 16 MSPS)

## OP5350-1 variants&#x20;

<table><thead><tr><th width="140.4000244140625">Vendor Part #</th><th> Description</th></tr></thead><tbody><tr><td><strong>OP5330-1K1</strong></td><td>Analog output card 16 channels, 1 MSPS, 16 bits, 35mA, ±16 V</td></tr><tr><td><strong>OP5330-1K2</strong></td><td>Analog output card 16 channels, 1 MSPS, 16 bits, 35mA, ±4 V</td></tr><tr><td><strong>OP5330-1K3</strong></td><td>Analog output card 16 channels, 1 MSPS, 16 bits, 15mA, ±16 V</td></tr></tbody></table>

## Typical use case

The OP5330 is typically used to deliver analog signals to **ECUs or external devices** during HIL simulations:

* Analog Outputs (up to 15 mA or 35 mA) feed into the ECU under test.
* Signals are processed by external signal conditioning or measurement equipment.

<figure><img src="https://2047776775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgkXB7sd4eT4qhErY15uu%2Fuploads%2FbRArRngeP2ZIli6pV0zO%2Fimage.png?alt=media&amp;token=eb1155c6-1d25-478f-8a9c-27b3974b69eb" alt=""><figcaption></figcaption></figure>


---

# 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/analog-output-modules/op5330-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.
