> 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/op4610xg/get-started/connect-the-simulator.md).

# Connect the Simulator

## Safety precautions <a href="#safety-precautions" id="safety-precautions"></a>

{% hint style="danger" %}

* Use **only the approved power cable** supplied with the product. Do **not** replace it with an inadequately rated cord.
* **Do not block ventilation vents**. Leave at least **15 cm (6”)** clearance at the sides and rear when not rack-mounted.
* Detailed safety instructions are available in the **Overview** documentation page of the simulator.
  {% endhint %}

## Procedure

{% stepper %}
{% step %}

### Connect a monitor to the simulator’s VGA port and a keyboard to any USB port

{% hint style="info" %}
These peripherals are **required only for specific configuration or troubleshooting tasks**, such as **initial network setup** (for example, setting the IP address), and are **not required for normal operation**.

Alternatively, **the simulator can be accessed remotely using an SSH client**; in this case, the simulator’s IP address must be known. See the procedure on the page entitled “**Access the Simulator Remotely via an SSH Client**” in the “**Supplementary Operations**” below.
{% endhint %}

* Connect the **monitor** to the **VGA port** (#1 in the illustration below). Do not use the HDMI port (#7) to connect a monitor to the simulator as it is not available.

{% hint style="info" %}
If your monitor does not have a VGA input port, use a **VGA-to-HDMI adapter.** Note that this type of adapter is **unidirectiona**l and an **HDMI-to-VGA adapter won't work**.
{% endhint %}

* Connect the **keyboard** to any of the **USB ports** (#5 in the illustration below).
  {% endstep %}

{% step %}

### Connect an Ethernet cable to LAN1 port <a href="#connect-an-ethernet-cable-to-lan1-port" id="connect-an-ethernet-cable-to-lan1-port"></a>

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/1aQlMaHTNkI8lCH1iqdQ" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Connect the power cable to a grounded outlet <a href="#connect-the-power-cable-to-a-grounded-outlet" id="connect-the-power-cable-to-a-grounded-outlet"></a>

{% 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/op4610xg/get-started/connect-the-simulator.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.
