> 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/op4300/operate-the-unit/connect-cables-for-emc-compliance.md).

# Design cables for EMC Compliance

## Introduction <a href="#context" id="context"></a>

This page presents recommendations for good cabling design to ensure electromagnetic compliance (EMC) simulators, FPGA processor and I/O expansion unit, and SLSC modules. Failing to follow the recommendations might lead to energy transfer in electromagnetic interference (EMI) that can disturb the equipment in the neighbor environment.

## Cable component items <a href="#cable-component-items" id="cable-component-items"></a>

* Ferrite clamp of proper circumference
* Twisted pair wires for signal and power
* Shield

## Analog cable assembly <a href="#analog-cable-assembly" id="analog-cable-assembly"></a>

The DB37 cable used for the analog I/O must follow the recommendations:

* Data should be cabled in twisted pairs.
* Cables should have a shield around the data.
* One shield per type of I/O and direction.
* The shield should be connected to the connectors’ shell/casing at both ends.
* The shells/casings should be connected to the chassis earth ground on both equipment.
* The total cable length should be less than 3 m (9 feet).

## Digital cable assembly <a href="#digital-cable-assembly" id="digital-cable-assembly"></a>

The DB37 cable used for the digital I/O module must follow the recommendations:

* Data should be cabled in twisted pairs.
* Cables should have a shield around the data.
* One shield per type of I/O and direction.
* The shield should be connected to the connectors’ shell/casing at both ends.
* The shells/casings should be connected to the chassis earth ground on both equipment.
* The total cable length should be less than 3 m (9 feet).
* For cables connected to digital output modules, the VUser\_RTN signal should be connected to the shell/casing of the cable with a 100 nF capacitor on both ends.
* The cable should have a ferrite clamp on the digital output side.

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/8X7bvTNSxwFMtVoMYboU" alt=""><figcaption><p>Simulator/expansion unit DB37 digital output connector side</p></figcaption></figure>

{% hint style="info" %}
During **EMC certification**, OPAL-RT used 3 clamps (Laird-Signal Integrity Products #28A2913-0A2) mounted as shown above.
{% endhint %}

## Power cable assembly <a href="#power-cable-assembly" id="power-cable-assembly"></a>

The power cable used for the Vuser in digital output modules must follow the recommendations:

* Power connections should use twisted pairs.
* Cable should have a shield around the twisted pairs.
* One shield per type of I/O and direction.
* The shells/casings should be connected to the chassis earth ground on both equipment.
* The total cable length should be less than 3 m (9 feet).
* The cable should have a ferrite clamp on the digital output side.

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/J21M9udgo4zXuK0UKhSV" alt=""><figcaption><p>Power cable for Vuser</p></figcaption></figure>

{% hint style="info" %}
During **EMC certification**, OPAL-RT used a clamp (Laird-Signal Integrity Products #28A2736-0A2) mount with multiple turns as shown above.
{% 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/op4300/operate-the-unit/connect-cables-for-emc-compliance.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.
