> 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/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **Pickering** driver is included by default with RT-LAB and does not require any additional installation.

## Hardware requirements

The Pickering driver supports compatible **Pickering modules** installed in either **PXI** **or LXI chassis**. The modules must be physically inserted into one of these chassis types depending on the selected interface. A PXI chassis is connected directly to the simulator through a **PCI‑Express** link, providing a local high‑performance hardware interface, while an LXI chassis communicates with the simulator over an **IP network**.

To verify whether such module is already included in your system, refer to your **System Description Document**. If no such module is included, review the supported **Pickering modules** below to identify suitable options for acquisition.

### Supported resistive modules

The following Pickering resistive cards are supported by the driver:

* **40‑262‑002** (18 subunits, 13 bits per channel)
* **40‑295‑121** (10 subunits, 12 bits per channel)
* **40‑295‑121** (10 subunits, 16 bits per channel)
* **40‑295‑121** (6 subunits, 24 bits per channel)
* **40‑297‑020**
* **40‑297A‑040** (6 subunits, 24 bits per channel)
* **40‑298‑050**
* **50‑295‑021** (5 subunits, 12 bits per channel)
* **50‑295‑021** (5 subunits, 16 bits per channel)
* **50‑295‑021** (10 subunits, 8 bits per channel)
* **50‑295‑021** (6 subunits, 24 bits per channel)
* **50‑295‑121** and **50‑295A‑121** (6 subunits, 24 bits per channel)
* **50‑297‑020**
* **50‑297‑041**
* **50‑298‑020**

### Supported FIU modules

The following Pickering Fault Insertion Unit (FIU) cards are supported:

* **40‑194‑002**
* **40‑195‑001**
* **40‑190B‑001**
* **40‑190B‑002**
* **40‑199‑002**
* **50‑200‑004**

### Supported relay modules

The following Pickering relay cards are supported:

* **50‑110A‑021**
* **50‑110A‑121**

### Battery simulator module requirements

The Pickering driver supports the following battery simulator card:

* **41‑752‑001**

### Unsupported and custom cards

The driver allows configuration of **custom Pickering cards** by manually specifying the card identifier and associated parameters.

{% hint style="danger" %}
Custom cards are **not officially tested or supported** by OPAL‑RT. The user is responsible for ensuring correct configuration and operation.

To request official support for an unsupported Pickering card, please contact your [**OPAL‑RT representative**](https://www.opal-rt.com/contact-us/).
{% endhint %}

## License requirements

### Simulator license

[Verify that an active RT-LAB license](https://www.opal-rt.com/docs/rt-lab/licensing-reference/simulator-license.md) with the following feature is installed on the simulator to run simulations using the Pickering driver:

| Feature Name | Required Status | Description                 |
| ------------ | --------------- | --------------------------- |
| PICKERING    | Enabled         | Pickering resistive modules |

When controlling **FIU modules**, the license must also include the following feature:

| Feature Name | Required Status | Description                         |
| ------------ | --------------- | ----------------------------------- |
| PICKERINGFIU | Enabled         | Pickering failure insertion modules |

### Workstation license

A workstation license is **not** required to run simulations in RT-LAB using the Pickering driver.


---

# 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/requirements-features-and-limitations.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.
