> 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/pickering-driver/configure-pickering.md).

# Configure Pickering

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 Pickering 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 **Pickering**. Double-click the newly created interface to begin 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-38eff4a8a02d6f6abc4287c19355b4b217113178%2FDR-rtlab-pickering-gen.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> The driver reserves a dedicated real‑time CPU core for its communication tasks.<br><strong>Unchecked:</strong> The communication system runs on core 0 alongside the operating system.</td></tr><tr><td><strong>Chassis type</strong></td><td><p><strong>PXI:</strong> When the PXI chassis type is selected, the chassis is connected to the simulator using a PCI‑Express (PCIe) interface card.</p><p><strong>LXI:</strong> When the LXI chassis type is selected, the chassis is connected to the simulator over an IP network and the following parameters must be configured:</p><ul><li><strong>IP address:</strong> Specifies the IP address of the LXI chassis network interface used to communicate with the simulator.</li><li><strong>Port</strong>: Specifies the TCP/IP port number of the LXI chassis interface on which the Pickering driver establishes the connection.</li></ul></td></tr><tr><td><strong>Enable virtual mode</strong></td><td><strong>Checked:</strong> Allows the model to execute even if the I/O interface does not match the hardware configuration. All connections are initialized, but the interface performs no communication. Useful for troubleshooting without hardware or preparing models for future systems.<br><strong>Unchecked:</strong> The interface operates normally and requires compatible hardware.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Manage Pickering cards: add, remove, rename, or reorder

In the **Folders** list, click **Cards** and use:

* **+** icon to add cards
* **–** icon to remove cards
* **Arrow** icons to reorder cards

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

{% step %}

### Configure the card(s) settings

In the **Folders** list, click a card under the **Cards** folder to configure its settings. Repeat this step for each additional card. Available configuration options vary depending on the selected **Card type**.

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

{% tabs %}
{% tab title="Resistive" %}

<table><thead><tr><th width="170">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Card type</strong></td><td>Specifies the type of Pickering card to configure.<br><strong>Resistive</strong>: Programmable resistor modules. When selected, a supported resistive card model must be chosen.</td></tr><tr><td><strong>Resistive card</strong></td><td>Specifies the selected resistive card module.</td></tr><tr><td><strong>Serial number</strong></td><td>Serial number of the Pickering programmable card. This unique identifier, available on the front panel of the module, is used to reliably identify the hardware.</td></tr><tr><td><strong>Number of subunits</strong></td><td>Displays the number of independent channels available on the card. Each subunit corresponds to one programmable resistor channel. This parameter is <strong>read‑only</strong>.</td></tr><tr><td><strong>Bits per channel</strong></td><td>Displays the number of switchable resistance elements used to program each resistor channel. This value defines the resolution of the channel and is equivalent to the number of columns in the resistance chain. This parameter is <strong>read‑only</strong>.</td></tr><tr><td><strong>Precision setting</strong></td><td>Indicates whether the selected resistive card supports precision resistance control. This parameter is <strong>read‑only</strong>.</td></tr><tr><td><strong>Minimum update rate (µs)</strong></td><td>Defines the minimum time interval, in microseconds, at which the channels of this card are updated.</td></tr></tbody></table>
{% endtab %}

{% tab title="FIU" %}

<table><thead><tr><th width="170">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Card type</strong></td><td>Specifies the type of Pickering card to configure.<br><strong>FIU</strong>: Fault Insertion Unit modules. When selected, a supported FIU card model must be chosen.</td></tr><tr><td><strong>FIU card</strong></td><td>Specifies the selected FIU card module.</td></tr><tr><td><strong>Serial number</strong></td><td>Serial number of the Pickering programmable card. This unique identifier, available on the front panel of the module, is used to reliably identify the hardware.</td></tr><tr><td><strong>Number of faulty channels</strong></td><td>Displays the total number of fault insertion channels available on the FIU card. This parameter is <strong>read‑only</strong>.</td></tr><tr><td><strong>Number of faulty buses</strong></td><td>Displays the number of fault insertion buses supported by the FIU card. This parameter is <strong>read‑only</strong>.</td></tr><tr><td><strong>Number of faulty multiplexers</strong></td><td>Displays the number of fault insertion multiplexers implemented on the FIU card. This parameter is <strong>read‑only</strong>.</td></tr><tr><td><strong>Number of faulty monitors</strong></td><td>Displays the number of fault insertion monitors available on the FIU card. This parameter is <strong>read‑only</strong>.</td></tr><tr><td><strong>Number of faulty pairs</strong></td><td>Displays the number of fault insertion channel pairs supported by the FIU card. This parameter is <strong>read‑only</strong>.</td></tr><tr><td><strong>Minimum update rate (µs)</strong></td><td>Defines the minimum time interval, in microseconds, at which the channels of this card are updated.</td></tr></tbody></table>
{% endtab %}

{% tab title="Relay" %}

<table><thead><tr><th width="170">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Card type</strong></td><td>Specifies the type of Pickering card to configure.<br><strong>Relay</strong>: Relay modules. When selected, a supported relay card model must be chosen.</td></tr><tr><td><strong>Relay card</strong></td><td>Specifies the selected relay card module.</td></tr><tr><td><strong>Serial number</strong></td><td>Serial number of the Pickering programmable card. This unique identifier, available on the front panel of the module, is used to reliably identify the hardware.</td></tr><tr><td><strong>Minimum update rate (µs)</strong></td><td>Defines the minimum time interval, in microseconds, at which the channels of this card are updated.</td></tr><tr><td><strong>Number of channels</strong></td><td>Displays the total number of channels available on the relay card. This parameter is <strong>read‑only</strong>.</td></tr></tbody></table>
{% endtab %}

{% tab title="Battery simulator" %}

<table><thead><tr><th width="170">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Card type</strong></td><td>Specifies the type of Pickering card to configure.<br><strong>Battery simulator</strong>: Battery simulator modules. When selected, the <strong>41‑752 Battery Simulator</strong> card is used by default.</td></tr><tr><td><strong>Serial number</strong></td><td>Serial number of the Pickering programmable card. This unique identifier, available on the front panel of the module, is used to reliably identify the hardware.</td></tr><tr><td><strong>Battery simulator card</strong></td><td>Specifies the selected battery simulator card module.</td></tr><tr><td><strong>Number of channels</strong></td><td>Displays the total number of channels available on the battery simulator card. This parameter is <strong>read‑only</strong>.</td></tr><tr><td><strong>Minimum update rate (µs)</strong></td><td>Defines the minimum time interval, in microseconds, at which the channels of this card are updated.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Configure the card(s) channel/subunit parameters

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

1. Use:

* **+** icon to add channel(s) / subunit(s)
* **–** icon to remove channel(s) / subunit(s)
* **Arrow** icons to reorder channel(s) / subunit(s)

2. Change parameters as desired. Available configuration options vary depending on the selected **Card type:**

{% tabs %}
{% tab title="Resistive" %}

<table data-header-hidden><thead><tr><th width="145"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>User‑defined name of the channel or subunit. This name is used to identify the channel within the configuration and the model.</td></tr><tr><td><strong>Index</strong></td><td>Numerical index identifying the channel or subunit within the card.</td></tr><tr><td><strong>Default value</strong></td><td>Default state applied to this channel before simulation start and each time the model is reset.</td></tr><tr><td><strong>Gain</strong></td><td>Gain factor applied to the resistive value provided by the model before it is programmed into the hardware.</td></tr><tr><td><strong>Offset</strong></td><td>Offset value applied to the resistive value provided by the model to compensate or adjust the effective resistance.</td></tr><tr><td><strong>Max bits</strong></td><td>Maximum number of switchable bits used to represent the resistor for this channel. This value reflects the hardware limitations of the channel.</td></tr></tbody></table>
{% endtab %}

{% tab title="FIU" %}

<table data-header-hidden><thead><tr><th width="145"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>User‑defined name of the channel or subunit. This name is used to identify the channel within the configuration and the model.</td></tr><tr><td><strong>Index</strong></td><td>Numerical index identifying the channel or subunit within the card.</td></tr><tr><td><strong>Default value</strong></td><td>Default state applied to this channel before simulation start and each time the model is reset.</td></tr><tr><td><strong>Type</strong></td><td>Specifies the FIU channel type. Supported options are:<br><strong>Channel</strong> – Standard signal channel<br><strong>Fault</strong> – Fault injection channel<br><strong>Monitor</strong> – Monitor channel used for observation</td></tr></tbody></table>
{% endtab %}

{% tab title="Relay" %}

<table data-header-hidden><thead><tr><th width="145"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>User‑defined name of the channel or subunit. This name is used to identify the channel within the configuration and the model.</td></tr><tr><td><strong>Index</strong></td><td>Numerical index identifying the channel or subunit within the card.</td></tr><tr><td><strong>Default value</strong></td><td>Default state applied to this channel before simulation start and each time the model is reset.</td></tr></tbody></table>
{% endtab %}

{% tab title="Battery simulator" %}

<table data-header-hidden><thead><tr><th width="145"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>User‑defined name of the channel or subunit. This name is used to identify the channel within the configuration and the model.</td></tr><tr><td><strong>Index</strong></td><td>Numerical index identifying the channel or subunit within the card.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}
{% 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/pickering-driver/configure-pickering.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.
