> 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/op5707xg2/supplementary-operations/monitor-analog-and-digital-i-os.md).

# Monitor Analog & Digital I/Os

{% hint style="info" %}
The unit used in the **example** below is an OP5707XG simulator. The **same information** and **procedures apply to all models of the OP56xx and OP57xx series** of **simulators** and **FPGA processor and I/O expansion units**.
{% endhint %}

This unit offers quick, single-ended connections through **RJ45** and **mini BNC** connectors.\
These allow easy **external signal monitoring** using standard devices such as oscilloscopes.

## I/O Modules <a href="#i-o-modules" id="i-o-modules"></a>

These simulators and I/O expansion units can accommodate up to **eight (8) I/O modules**, also known as mezzanine boards or cards.

* **Modules** are organized into **four groups** (1 to 4).
* **Each group** includes **two sections**, labeled **A and B**.
* **Module locations** are identified as: 1A, 1B, 2A, 2B, 3A, 3B, 4A, and 4B.

## RJ45 Front Monitoring Connectors <a href="#rj45-front-monitoring-connectors" id="rj45-front-monitoring-connectors"></a>

All I/O signals routed to the **rear DB37 connectors** are **mirrored** to the **front panel RJ45 monitoring connectors**.

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/UwxpKHEcpMLD2sGqlloB" alt=""><figcaption><p>Rear and front views of an OP5707XG showing mirroring of the group 1 (red arrows), A and B sections (blue arrows)</p></figcaption></figure>

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/8a6lt5kVcBHUTfOC6ZdR" alt=""><figcaption><p>Groups 1 to 4 are identified from left to right</p></figcaption></figure>

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/bpiH2M3VNqzXyMqjYUk4" alt="" width="440"><figcaption><p>Each group has two sections: A (left) and B (right)</p></figcaption></figure>

### I/O Channel Assignments <a href="#i-o-channel-assignments" id="i-o-channel-assignments"></a>

* **Digital I/O** modules **use channels 0 to 31**, spanning **both columns** of RJ45 connectors.
* **Analog I/O** modules **use only channels 0 to 15**, located in the **first column**.

{% columns %}
{% column %}

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/gOAj6jid6sPSzTEiB2Bv" alt=""><figcaption><p><strong>Digital I/O</strong> module 1A uses channels <strong>0 to 31</strong><br></p></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/mjmKYGXEe03eb2rrHjYP" alt=""><figcaption><p><strong>Analog I/O</strong> module 1A uses only channels <strong>0 to 15</strong><br></p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
Refer to the **System Description Document** (available on the included USB key in a PDF format or in a binder with a CD-ROM with the PDF file) to verify **which I/O modules are installed** in your system and at **what location**.

If you already have the module model numbers and locations, consult the [**I/O module specifications and pin assignments**](https://opal-rt.atlassian.net/wiki/spaces/PHDGD/pages/144659930). All [**compatible modules** ](https://opal-rt.atlassian.net/wiki/spaces/PHDGD/pages/144630825)belong to the [**OP5300 Series**](https://opal-rt.atlassian.net/wiki/spaces/PHDGD/pages/144659930).
{% endhint %}

## Monitoring Interface <a href="#monitoring-interface" id="monitoring-interface"></a>

The monitoring interface is located in the **bottom right corner** of the **OPAL-RT unit**. It includes:

* Four (4) **RJ45 connectors**
* Four (4) **mini BNC sockets** below each RJ45 connector

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/24pzAd2MHqCKRQNoM8hz" alt=""><figcaption><p>Monitoring interface</p></figcaption></figure>

**Each RJ45 connector on the front panel** can be **linked** via a n**etwork cable** to the **monitoring interface**.\
Every **cable carries** up to **4 I/O signals**, which are **accessible** through the **mini BNC sockets** labeled **A**, **B**, **C**, **D**.

{% hint style="info" %}
Total monitoring capacity: **16 individual I/O signals**.
{% endhint %}

<div data-with-frame="true"><figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/Bqhzn3ijNmI2tIkV03JW" alt="" width="375"><figcaption><p>Four RJ45 connectors with four mini BNC sockets each</p></figcaption></figure></div>

## Connecting Cables to Monitor I/O Signals <a href="#connecting-cables-to-monitor-i-o-signals" id="connecting-cables-to-monitor-i-o-signals"></a>

Your unit’s **starter kit** includes:

* **Four** (4) short **network cables** (2 ft – **red**, **green**, **black**, **white**)
* **Four** (4) **BNC to mini BNC coaxial cables** (6 ft, 75 ohms)

{% columns %}
{% column %}

<div data-with-frame="true"><figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/P2s6ldAOMZqFHsPp5hAM" alt=""><figcaption><p>Network cables</p></figcaption></figure></div>
{% endcolumn %}

{% column %}

<div data-with-frame="true"><figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/69TuHAR4DCUv9iv5pO3R" alt="" width="160"><figcaption><p>BNC to mini BNC coaxial cables</p></figcaption></figure></div>
{% endcolumn %}
{% endcolumns %}

{% hint style="danger" %}
Only connect cables from the upper section of the front panel to the lower monitoring interface. **Other connections may damage the equipment.**
{% endhint %}

## Example <a href="#example" id="example"></a>

As an example, let's **monitor channel 5 from I/O module 2B**

1. **Identify the front RJ45 connector** linked to **channel 5** of the **2B module** (or group 2B).
   * Find **group 2**.
   * Find **section B** in **group 2**.
   * Find the **RJ45 connector** that includes **channel 5**.

<div data-with-frame="true"><figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/tmhaMEcLDfTfqWMvyaW5" alt=""><figcaption></figcaption></figure></div>

2. **Connect one end of the network cable** (e.g., green) to this connector and the other end to an available RJ45 port on the monitoring interface.\ <br>

<div data-with-frame="true"><figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/1xCaVgjHP740qZEu373R" alt="" width="563"><figcaption><p><em>Connecting the RJ45 monitoring connector to the first RJ45 connector of the monitoring terminal</em></p></figcaption></figure></div>

3. On the monitoring interface, **locate** the **mini BNC socket labeled B** (channel 5).\
   The mini **BNC channel mapping** of our example is as follows:

{% columns %}
{% column %}
A = Channel 4\
B = Channel 5\
C = Channel 6\
D = Channel 7
{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

4. Plug **one end** of a **BNC to mini BNC cable** into **socket B**, and the **other end** into the **oscilloscope** or other **monitoring device**.

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/5XrdSmVJO0rNYs4QRPmT" alt=""><figcaption><p>I/O signal monitoring using an oscilloscope</p></figcaption></figure>

{% hint style="info" %}
**Signal Gain Adjustment**

The **monitoring interface** applies a **gain factor of 0.1**, so **external devices** (e.g., oscilloscopes) must apply a gain of 10 to restore correct signal levels and ensure accurate readings.
{% 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/op5707xg2/supplementary-operations/monitor-analog-and-digital-i-os.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.
