> 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/rt-lab/configure-ios/communication-protocol-ios/diane-rtdp/configure-diane.md).

# Configure DIANE

When working with communication protocols, it is recommended to begin by configuring the protocol through the **I/O Interfaces** section in RT-LAB before proceeding with other steps.

## Configure the DIANE I/O interface

{% stepper %}
{% step %}

### Add a new I/O interface

In RT-LAB Project Explorer, right-click **I/O Interfaces**, select **New I/O Interface**, and choose **DIANE**. Double-click the newly created interface to begin configuration.
{% endstep %}

{% step %}

### Launch DIANE Importer

From the **DIANE I/O Interface**, click **DIANE Importer** to launch the import wizard.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-4834272a8ba3391c88e56f609a30bcd190965e01%2FDR-rtlab-diane.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select the XML configuration file

Browse to the XML configuration file to be loaded.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-8427f58cf2b65f2646c4f489ba9f9e500e6cf954%2FDR-rtlab-diane2.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select producers

If the XML file is valid, the table is automatically populated with the list of detected **Producers**. Enable the required **Producers**, choose the desired operating mode (**Transmission**, **Reception**, or **Both**), and update the IP addresses and port numbers as needed. Fields highlighted in yellow are editable.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-14b83b59c07a92c872f9c3724ec692301ed93a8e%2FDR-rtlab-diane3.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure messages

Click **Next** to view the list of messages associated with each **Producer**. The message sampling rate can be configured by adjusting the **Number of series** field.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-308ae037e6b7fe4c695ee7fca8a33d6c5f532e5d%2FDR-rtlab-diane3-1.png?alt=media" alt=""><figcaption></figcaption></figure>

Click **Next** once again to see the parameters for the messages.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-b09f976725e9af22789a2f11d4dd975e557f97e2%2FDR-rtlab-diane4.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Finish the import

Click **Finish** to close the wizard and return to the DIANE configuration.
{% endstep %}

{% step %}

### Configure the general settings

In the **Folders** list, click **General** and configure the general settings.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-4c8ebb4bd53631814dae21b939fd65fd7e1a95f8%2FDR-rtlab-diane5.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="165">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Use an RT core for asynchronous computation</strong></td><td><strong>Checked:</strong> Reserves a dedicated real-time CPU core for its communication.<br><strong>Unchecked:</strong> Defaults to core 0.</td></tr><tr><td><strong>Diane transmitter timeout (ns)</strong></td><td>Specifies how long the transmitter has to send the entire datagram. If the timeout is too short and transmission does not complete in time, bit 6 of the datagram status field is raised to indicate a timeout condition.</td></tr><tr><td><strong>Enable virtual mode</strong></td><td><strong>Checked:</strong> Allows the model to run even if the I/O interface is not compatible with the hardware configuration. Connections are initialized, but the interface performs no actions.<br><strong>Unchecked:</strong> Troubleshoot without hardware or prepare a model for a future hardware platform.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Configure advanced parameters

In the **Folders** list, click **Advanced parameters** and configure the advanced parameters.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-4d6a42f7f3072607759ee28852ef5a644923c9d3%2FDR-rtlab-diane6.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="190">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Inter‑process FIFO depth (Transmitter)</strong></td><td>Defines the size of the FIFO buffer used by the transmitter to retain outgoing data. A larger depth may be required when the model timestep is very small to prevent data loss. If the configured depth is insufficient for the selected timestep, a warning is issued at execution time and the <strong>Saturated</strong> data point is set to <code>1</code>.</td></tr><tr><td><strong>Inter‑process FIFO depth (Receiver)</strong></td><td>Defines the size of the FIFO buffer used by the receiver to retain incoming data. A larger depth may be beneficial when operating with very small model timesteps. If the configured depth is insufficient, a warning is issued during reset.</td></tr><tr><td><strong>Transmitter network interface</strong></td><td>Specifies the network interface used by the transmitter. If set to <strong>ANY</strong>, the interface selection is ignored and the system automatically chooses an available interface.</td></tr><tr><td><strong>Receiver network interface</strong></td><td>Specifies the network interface used by the receiver. If set to <strong>ANY</strong>, the interface selection is ignored and the system automatically chooses an available interface.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Save the configuration

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-44bd03ce3c41f8ba5c990b61c29b38c9b80ae5f2%2FDR-rtlab-save.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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/rt-lab/configure-ios/communication-protocol-ios/diane-rtdp/configure-diane.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.
