> 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/pcie-cards-and-connector-kits/connector-kits/op5969-2-optical-fiber-i-o-module.md).

# OP5969-2 Optical Fiber I/O Module

## Description

The **OP5969‑2** is an optional optical‑fiber I/O module that can be installed on select simulators and FPGA processor and I/O expansion units. It must be requested explicitly at the time of ordering; otherwise, the OP5969‑1 RS‑422 I/O module is installed by default.

The optical‑fiber I/O module connects to the rear interface of the simulator and provides **six pairs of optical‑fiber connectors**, consisting of **six inputs** and **six outputs**.

<figure><img src="https://2718581018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2B8wcgY3hASHF6RKIfKW%2Fuploads%2FNU4CnalhUrNMnSkrme2P%2Fimage.png?alt=media&amp;token=4304bc6f-9f6d-4282-9fdb-69c3c3ed5c9a" alt="" width="375"><figcaption></figcaption></figure>

## Specifications <a href="#specifications" id="specifications"></a>

<table data-header-hidden data-search="false"><thead><tr><th width="270.00006103515625"></th><th></th></tr></thead><tbody><tr><td><strong>Number of channels</strong></td><td>6 transmitters, 6 receivers</td></tr><tr><td><strong>Receiver Type</strong></td><td>AFBR-2624Z PIN diode</td></tr><tr><td><strong>Transmitter Type</strong></td><td>AFBR-1624Z 650 nm wavelength</td></tr><tr><td><strong>Connector Type</strong></td><td>Avago’s Versatile Link family</td></tr><tr><td><strong>Compatible Fiber Type</strong></td><td>Plastic Optical Fiber (POF), 650 nm</td></tr><tr><td><strong>Maximum Tx/Rx Frequency</strong></td><td>DC - 25 MHz</td></tr><tr><td><strong>Baud Rate</strong></td><td>50 Mbps</td></tr><tr><td><strong>Minimum Tx Pulse Width</strong></td><td>20 ns</td></tr><tr><td><strong>Maximum Distance</strong></td><td>50 meters</td></tr></tbody></table>

<figure><img src="https://2718581018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2B8wcgY3hASHF6RKIfKW%2Fuploads%2FGrcZRULp3XTvcChicE6N%2Fop5969-2-fiber-optic-connector-kit.webp?alt=media&amp;token=ebf169db-5cd4-4f62-802b-0b8f5d347603" alt="" width="375"><figcaption></figcaption></figure>

## General pin assignments <a href="#section-a-rs422-digital-inputs" id="section-a-rs422-digital-inputs"></a>

<table data-header-hidden><thead><tr><th width="270">OP5969-2 pin name</th><th>Signal name</th></tr></thead><tbody><tr><td><strong>RX </strong><em><strong>nn</strong></em></td><td>Channel <em>nn</em> Receiver</td></tr><tr><td><strong>TX </strong><em><strong>nn</strong></em></td><td>Channel <em>nn</em> Transmitter</td></tr></tbody></table>


---

# 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/pcie-cards-and-connector-kits/connector-kits/op5969-2-optical-fiber-i-o-module.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.
