> 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/connect-the-hardware.md).

# Connect the Hardware

The Pickering driver supports Pickering modules installed in the following chassis types:

* **PXI chassis**
* **LXI chassis**

## PXI chassis

Connect the PXI chassis to the OPAL‑RT simulator using a **PCI‑Express (PCIe)** interface, as specified in your **System Description Document**. Ensure that all Pickering cards are properly installed in the PXI chassis before powering on the system.

## LXI chassis

Each LXI chassis must be configured with a valid IP address and port number, and both the simulator and the LXI chassis must reside on the same network in order to successfully establish network communication. Ensure that all Pickering cards are properly installed in the PXI chassis before powering on the system.

### Configure the LXI chassis

1. Connect the LXI chassis directly to a PC or laptop using a standard Ethernet cable.
2. The LXI chassis is shipped with a default IP address and port configuration.
3. Open a web browser on the PC and enter the default IP address of the LXI chassis.
4. Once the configuration interface loads, navigate to the **LAN Configuration** settings tab:

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-e18e5b64fcac25d3f46e79e76cd6bb9f4de3e345%2Fimage%20(368).png?alt=media" alt=""><figcaption></figcaption></figure>

5. In the **LAN Configuration** page, go to the **Ethernet Network Status** section to view the current network status of the chassis.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-6850bd861d66e5386a8691adacc70ddf5de38668%2Fimage%20(369).png?alt=media" alt=""><figcaption></figcaption></figure>

6. Chock the box corresponding to the desired configuration:

* **DHCP:** Automatically assigns network parameters using a DHCP server present on the network.
* **Auto‑IP:** Automatically assigns network parameters without requiring a DHCP server. This mode is typically used for direct point‑to‑point connections.
* **Manual:** Allows static configuration of network parameters. The user must manually enter each Ethernet network setting, such as IP address, subnet mask, and gateway. The **Manual** option **is recommended for real‑time applications**, as a static network configuration ensures predictable IP addressing and improves communication reliability between the simulator and the LXI chassis.

7. Click **Apply changes**.


---

# 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/connect-the-hardware.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.
