> 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/accessories-conditioning-modules/mapping-and-interconnection/op8710-high-voltage-solid-state-relay-box/system-description.md).

# System Description

## Description <a href="#description" id="description"></a>

The **OP870 High Voltage Interface Panel** (HVIP) can provide digital signals of up to 250 VDC to external equipment and provides up to 16 such signals.

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2FUNDgIRbibT6UxBef2Ah1%2Fimage.png?alt=media&amp;token=a7b26014-7bdc-4bd5-8472-17942945d877" alt=""><figcaption><p><em>OP8710 Front panel</em></p></figcaption></figure>

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2FGbRrE7Khf0lRh7lBE3Me%2Fimage.png?alt=media&amp;token=0eb990c4-55db-49da-8f7c-37dfe023fa5e" alt=""><figcaption><p><em>OP8710 Rear panel</em></p></figcaption></figure>

OPAL-RT's digital outputs control the relay switch located between the +VDC and +LOAD connections.

The HVIP uses 8 Brentek International dual channel solid-state output modules for the 16 output channels.\
Each output module can switch up to **250 mA** at **250 VAC/VDC**.\
The module is operated using an **active-low signal** provided by the OPAL-RT simulator.

The module output contact is **closed when 0 volts** are applied to the control input.\
When the module contact is closed, **the relay status LED is ON**.\
If no connection is made to the control input, then the module contact is open.

The DB37 connector uses the same pinout as the **OP5600 and OP5700 families of chassis**.

{% hint style="danger" %}
When making connections between the HVIP and the external equipment, ensure that the **+VDC voltage supply is turned OFF**.
{% endhint %}

## Typical application diagram <a href="#typical-application-diagram" id="typical-application-diagram"></a>

{% hint style="danger" %}
**NOTE** that the **OP8710** is equipped with a **watchdog**.
{% endhint %}

The watchdog **receives synchro pulses from the target’s FPGA**, which is in turn **what drives the relays** (with the 24 V power received through the watchdog).\
**If the watchdog stops receiving the synchro signal** for any reason (this indicates that the model has reset, crashed, etc.), **it cuts the 24 V at source**, and this in turn **opens all the relays**.

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2FsNLMaBL9pWHV6P4v5IUW%2Fimage.png?alt=media&amp;token=8256c053-b688-4ae4-81d6-0262308493dd" alt=""><figcaption></figcaption></figure>

## Watch dog signal conversion <a href="#watch-dog-signal-conversion" id="watch-dog-signal-conversion"></a>

The **OP8710 watch dog** uses an **electrical signal** from a **copper wire**. **If your target is recent**, it may **only have fiber-optic synchronization**.\
In this case, you may use the **OP5966 RTSI Signal Converter module** between the target and the OP8710 High Voltage Solid State Relay Box to convert the synchro signal from copper to fiber-optic

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2FAALKN6zmrk6bkkN7LmZf%2Fimage.png?alt=media&amp;token=ed681882-51ed-46e6-b32b-06d5a5540f69" 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/accessories-conditioning-modules/mapping-and-interconnection/op8710-high-voltage-solid-state-relay-box/system-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.
