> 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/op8666/op8666-overview/typical-use-cases.md).

# Typical Use Cases

## Controller hardware-in-the-loop applications <a href="#controller-hardware-in-the-loop-applications" id="controller-hardware-in-the-loop-applications"></a>

The OP8666 also **interfaces directly to OPAL-RT real-time simulators** through the DB37 connectors on the rear panel.

This enables a **low-cost RCP controller Hardware-In-the-Loop (HIL) solution**, which can **reduce the development time** and **increase flexibility** without investing in the hardware before finalizing the control system.

<figure><img src="https://1188700823-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqSz7qPxQbRFCsCnF5Xtl%2Fuploads%2FsSyU8WDp2lglutK3urYi%2Fimage.png?alt=media&amp;token=0fc8ebdd-2e62-438a-8f4f-c38e1b633e1c" alt="" width="563"><figcaption></figcaption></figure>

## Power electronics applications <a href="#power-electronics-applications" id="power-electronics-applications"></a>

The OP8666 is ideal for **power electronics inverters and converters control system implementation** due to its **rapid control prototyping (RCP) capability** and **high performance**.\
Therefore, it’s quite popular for research and prototyping.

In addition, the open-source MATLAB Simulink models will greatly accelerate the development cycle of power electronics converters with the help of available application examples.

**Open-source application examples** and **open-source MATLAB Simulink models** are available here: [C2000 Microcontroller Blockset - Examples](https://www.mathworks.com/help/ti-c2000/examples.html)

Furthermore, large resources are available from Texas Instruments that support the development of the F28379D ControlCARD.

Finally, due to its direct interface with the PELab from Taraz Technologies through the DB50 connectors, rapid development of power electronics systems is possible.

<figure><img src="https://1188700823-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqSz7qPxQbRFCsCnF5Xtl%2Fuploads%2FHkFOYVm88CeaOBWWHtsL%2Fimage.png?alt=media&amp;token=54233962-4a3f-480d-878a-495804987240" alt="" width="563"><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/op8666/op8666-overview/typical-use-cases.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.
