> 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/op4810-io/supplementary-operations/change-the-ip-address.md).

# Change the IP Address

When multiple OP4810-IO or OP4815-IO expansion units are connected to a master simulator, each expansion unit must be assigned a **unique IP Address**. This section explains how to assign a static IP address to an OP4810-IO or OP4815-IO expansion unit by programming the EEPROM.

{% hint style="danger" %}
For **multi-expansion-unit orders**, IP addresses are **preconfigured at the factory** and documented in the **System Description Document** provided with your system. No additional configuration is required in this case.

If additional expansion units are added later to an existing system, you must assign a **unique IP address** to each new unit to avoid address conflicts and communication errors.
{% endhint %}

{% stepper %}
{% step %}

### Power ON the Versal expansion unit

Boot the Versal chassis and wait approximately **10 seconds**. Use the **Menu** button on the LCD screen, if necessary, to display the current IP address.
{% endstep %}

{% step %}

### Log in the simulator&#x20;

Refer to the **Get Started** section of your simulator documentation for instructions on connecting to and logging in to the simulator. As described in the procedure, the simulator can alternatively be accessed remotely using an **SSH client**; in this case, the simulator’s IP address must be known.
{% endstep %}

{% step %}

### Verify network connectivity

Ensure that the simulator and the expansion unit are connected as described in the **Connect the Expansion Unit** section of this documentation. To avoid IP address conflicts, only the expansion unit whose IP address will be changed must be connected.

While logged in to the simulator, verify that the expansion unit is reachable by pinging its current IP address. For example:

&#x20;`ping -c 4 192.168.3.5`
{% endstep %}

{% step %}

### Program the IP address in EEPROM

The IP address is configured using the `arm_util.py` script.&#x20;

1. On the OPAL‑RT simulator, navigate to the directory where the script is located:\
   **RT-LAB**\
   `cd /usr/opalrt/common/bin/Data/Drivers/OpalBoards_GUI/`\
   **HYPERSIM**\
   `cd /export/local/ssr/<hypersim_version>/linux-oprtlinux3-64/HyServer/rt/lib/Data/Drivers/OpalBoards_GUI/`
2. Run the following command to program the IP address in the EEPROM:

`python3 arm_util.py --ip <CURRENT_IP_ADDRESS> network --nic1 --set <IP_ADDRESS> <NETMASK> <GATEWAY>`

Where:

* `<CURRENT_IP_ADDRESS>` is the current IP address of the expansion unit
* `<IP_ADDRESS>` is the desired static IP address
* `<NETMASK>` is the desired subnet mask
* `<GATEWAY>` is the desired gateway address

Example:

`python3 arm_util.py --ip 192.168.3.5 network --nic1 --set 192.168.3.8 255.255.255.0 192.168.3.1`

<figure><img src="broken://spaces/7LhLoEldIvunS3fxYxrx/files/v7JRSYfzvneeEfDlpYza" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The `arm_util.py` script can also be found on the workstation, provided that RT‑LAB or HYPERSIM 2024.1 or later is installed. In this case, the script is located in the corresponding RT‑LAB or HYPERSIM installation directory:

* RT‑LAB: `...\common\bin\x64\Data\Drivers\OpalBoards_GUI`
* HYPERSIM: `...\Windows\HyGui\lib\Data\Drivers\OpalBoards_GUI`
  {% endhint %}
  {% endstep %}

{% step %}

### Power-cycle the expansion unit

Power off the expansion unit, wait a few seconds, then power it back on and allow approximately 10 seconds for the DHCP timeout before checking the LCD screen again.&#x20;

This behavior is expected, as the unit always attempts to obtain an IP address via DHCP first and falls back to the IP address stored in the EEPROM if no DHCP server responds.

The new IP address should now appear on the LCD screen; you can also ping the new address to verify connectivity between the simulator and the expansion 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/op4810-io/supplementary-operations/change-the-ip-address.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.
