> 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/op4815-io/operate-the-expansion-unit/power-on-and-check-status-indicators.md).

# Power ON & Check Status Indicators

## Follow the power-up sequence <a href="#power-up-sequence" id="power-up-sequence"></a>

First make sure that all cables are properly connected before powering up.

When the OP4815-IO is connected to the simulator **via PCIe**, **it must be powered ON before the simulator**. Failure to do so will prevent the simulator from detecting the OP4815-IO FPGA during boot.

## Set the rear power switch to ON

Before using the front panel controls, **ensure the rear power switch is ON**:

* At the back of the expansion unit, locate the **main power switch** near the power supply input.
* Set this switch to the **ON** position.

<figure><img src="https://content.gitbook.com/content/uNbQwgFm3KJ8huN25Ymr/blobs/szZ9i7wWiuxGy5XuzNi6/OP48XX-IO%20-%20Rear_power.jpg" alt="OP4810 back"><figcaption></figcaption></figure>

## Use the front power button

Once the rear switch is ON, use the front panel controls as follows:

* Power button
  * Press once: Power ON or shut down the expansion unit.
  * Long press: If the button is pressed for at least 4 seconds, the unit will shut down.
* LED Indicator (integrated into the button)
  * Green: Expansion unit is ON.
  * Black (unlit): Expansion unit is OFF.

<figure><img src="https://content.gitbook.com/content/uNbQwgFm3KJ8huN25Ymr/blobs/t1t2ZOnwB2RQPZOSv5M9/OP4815-IO%20-%20Front%20power.jpg" alt=""><figcaption></figcaption></figure>


---

# 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/op4815-io/operate-the-expansion-unit/power-on-and-check-status-indicators.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.
