> 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/accessories-conditioning-modules/mapping-and-interconnection/pickering-pxi-chassis.md).

# Pickering PXI Chassis

<figure><img src="https://609051844-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGba4ytXQss1VNonuRAzM%2Fuploads%2FuL2XHEe9trxmbGwCgt3j%2Fimage.png?alt=media&amp;token=b323eacf-d730-436f-82a8-15273adb3909" alt="" width="320"><figcaption></figcaption></figure>

The [**following Pickering PXI chassis**](https://www.pickeringtest.com/en-us/products/pxi/chassis-instrumentation/pxi-chassis) have been tested with OPAL-RT platforms:

| Description                         | Information                                                                                             | Part Numbers                                          |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| **14-slot, 3U, 350W Chassis**       | [**Product web page**](https://www.pickeringtest.com/en-us/product/14-slot-3u-350w-pxi-chassis/)        | OPAL-RT P/N: **T00-1245** (Pickering P/N: 40-914-001) |
| **8-slot, 3U, 350W**                | [**Product web page**](https://www.pickeringtest.com/en-us/product/8-slot-pxi-chassis)                  | OPAL-RT P/N: **T00-5129** (Pickering P/N: 40-922-001) |
| **8-slot, 3U, 350W, low-noise fan** | [**Product web page**](https://www.pickeringtest.com/en-us/product/8-slot-3u-pxi-chassis-low-noise-fan) | OPAL-RT P/N: **T00-5138** (Pickering P/N: 40-908-001) |

These chassis can be integrated with OPAL-RT simulators using a PCIe to PXI remote control interface, and are typically used to integrate fault insertion cards in real-time simulation systems, **such as:**

| Description                       | Information                                                                                                             | Part Numbers                                           |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| **PXI Single Bus 74 channels 2A** | [**Product web page**](https://www.pickeringtest.com/en-us/product/single-bus-74-ch-2a-fault-insert-switch-40-190b-001) | OPAL-RT P/N: **T00-4245** (Pickering P/N: 40-190B-001) |
| **PXI Dual Bus 74 channels 2A**   | [**Product web page**](https://www.pickeringtest.com/en-us/product/dual-bus-74-chan-2a-fault-insert-switch-40-190b-002) | OPAL-RT P/N: **T00-4232** (Pickering P/N: 40-190B-002) |
| **PXI Dual Bus 10 channels 10A**  | [**Product web page**](https://www.pickeringtest.com/en-us/product/10a-fault-insertion-switch-10-chan-2-bus)            | OPAL-RT P/N: **T00-4233** (Pickering P/N: 40-199-002)  |

A series of **resistor modules** are also compatible with these chassis and supported with OPAL-RT platforms.


---

# 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/accessories-conditioning-modules/mapping-and-interconnection/pickering-pxi-chassis.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.
