> 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/op5707xg2/supplementary-operations/change-the-chassis-index.md).

# Change the Chassis Index

When multiple OPAL-RT simulators and FPGA processor and I/O expansion units are connected together, each unit must be assigned a **unique chassis index**. This section explains how to set the chassis index, when required, using the onboard DIP switch.

{% hint style="danger" %}
For **multi-unit orders**, chassis indexes are **already properly assigned** and specified in the **System Description Document** provided with your system.&#x20;

For **single-unit orders**, the chassis index is set to the **default value of 00**. If additional units are added later, you **must change** the chassis index of each new unit to a **unique value** to prevent address conflicts and communication errors.
{% endhint %}

{% hint style="danger" %}
The **chassis index DIP switch** is situated **within the OP5707XG2 simulator**. In the event that the chassis index requires modification at the customer site, it should be **undertaken by or under the supervision and instructions of an OPAL-RT certified field engineer**.
{% endhint %}

{% stepper %}
{% step %}

### Turn off the unit and disconnect the power cord

{% endstep %}

{% step %}

### Remove the top cover of the unit

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/dchR8rshMrP2gQ5Djy20" alt="" width="563"><figcaption><p>Remove 6 screws (3 per side) on OP56xx/OP57xx units</p></figcaption></figure>

1. Remove the 6 screws (3 on each side of the unit).
2. Use a flat, rigid tool (e.g., flat-headed screwdriver) to lift the top cover.
   {% endstep %}

{% step %}

### Set the chassis index

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/zjrNdWY42IkjZrNQNtW1" alt="" width="563"><figcaption><p>Top view of the carrier board for OP56xx/OP57xx units</p></figcaption></figure>

The chassis index is set using a **5-pin DIP switch (SW1)** located inside the unit. The switches represent the 5 bits of the chassis index in binary format.

* **Switch ON = 0**, **Switch OFF = 1**.
* For example:
  * Setting `11010` (binary) corresponds to `1A` in hexadecimal or `26` in decimal.

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/0dRyqEJ92pHtMwMA4btx" alt="" width="563"><figcaption></figcaption></figure>

* This value can range from 00 to 1F (in hexadecimal) or 0 to 31 (in decimal), allowing up to 32 unique chassis addresses.
* Unless otherwise specified in the **System Description Document** provided with your system, the **default value is 00**.
  {% endstep %}

{% step %}

### Reinstall the top cover

Reinstall the top cover and secure it with the 6 screws (3 on each side of the unit).
{% 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/op5707xg2/supplementary-operations/change-the-chassis-index.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.
