> 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/op4512/get-started/unbox-the-simulator/mount-the-simulator-in-a-rack-optional.md).

# Mount the Simulator in a Rack (Optional)

The rack mount brackets and handles are usually not assembled to the simulator.

## Hardware list <a href="#op4610xgreceivingandverification-hardwarelist" id="op4610xgreceivingandverification-hardwarelist"></a>

The hardware for the rack mount brackets and handles is provided in a plastic bag.

* Two 110-2655 2U rack mount brackets
* Two T00-1392 pan-head Phillips black screws, 8-32 × 3/8 in.

<figure><img src="https://4286127377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgT2kDoXVJn89T4Y7NiYB%2Fuploads%2F3EXJPLgTq0XU6MI10d3N%2FOP4512-bracket.png?alt=media&amp;token=db405d59-e076-421d-9254-b8c77f7cf4da" alt="OP4512 Kit Rack mount" width="160"><figcaption></figcaption></figure>

## Installation steps <a href="#op4610xgreceivingandverification-assembling" id="op4610xgreceivingandverification-assembling"></a>

{% stepper %}
{% step %}

### Install the unit in the rack

Place the unit on a **compatible rack shelf** (not included), then secure it using the supplied holding brackets.

<figure><img src="https://4286127377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgT2kDoXVJn89T4Y7NiYB%2Fuploads%2FN81eUIiPNvtGmP2JoDQV%2Fimage-20240710-145604.png?alt=media&amp;token=a71d51f1-0fcb-47ab-a048-6c6ad81a096a" alt="OP4512 rack mount"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Grounding (recommended for rack-mounted setups) <a href="#connecting-the-ground-screw" id="connecting-the-ground-screw"></a>

* Select a short, flat braided grounding strap with ring terminals on both ends.
* Attach one ring terminal to the **ground screw** on the OP4512.
* Attach the other terminal to the rack using a **nut and lock washer**.

<figure><img src="https://content.gitbook.com/content/gT2kDoXVJn89T4Y7NiYB/blobs/TsMRM2HH8IyMKno4Q9NU/image.png" alt="" width="284"><figcaption></figcaption></figure>

{% hint style="info" %}
Proper grounding prevents electric shocks, protects against voltage spikes (e.g., lightning strikes) and improves EMI immunity by lowering noise levels and emissions.
{% endhint %}

{% hint style="info" %}
Ensure the **rear power switch** is always easily accessible for emergency shutdown.
{% endhint %}
{% 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/op4512/get-started/unbox-the-simulator/mount-the-simulator-in-a-rack-optional.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.
