> 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/rt-lab/configure-ios/communication-protocol-ios/scpi/connect-the-hardware.md).

# Connect the Hardware

## Connect devices using standard Ethernet cables

SCPI operates over **Ethernet (TCP/IP)** and uses the simulator’s **built‑in LAN ports**. To establish communication between the simulator and external devices or applications, simply connect the systems using **standard Ethernet cables**.

## Configure IP addresses and subnets

For reliable SCPI communication, standard IP networking rules must be followed:

* The simulator and all SCPI devices must be located on the same IP subnet unless routing has been explicitly configured.
* Each physical device must be assigned a unique IP address to avoid address conflicts.
* A single device may host multiple SCPI over TCP connections, each differentiated by its TCP port number.
* The simulator uses the IP address of the selected LAN interface as the local endpoint for SCPI TCP communication.
* On Linux systems, IP aliasing may be used to assign multiple IP addresses to the same network interface, allowing different SCPI connections to use distinct local IP addresses when required.

**Example of valid subnet configuration**

* Simulator: `192.168.10.10 / 255.255.255.0`
* Remote device 1: `192.168.10.20 / 255.255.255.0`
* Remote device 2: `192.168.10.30 / 255.255.255.0`

## Set the TCP ports

SCPI over Ethernet relies on TCP port numbers to identify instrument control services and individual connections.

Many SCPI instruments expose a default SCPI TCP port (commonly **5025**), but the actual port number is device‑specific and configurable on some instruments. Any valid, unused TCP port may be used, provided both endpoints are configured consistently.

When configuring SCPI over TCP ports:

* Ensure that no firewall, security appliance, or operating system rule blocks the selected TCP port.
* The simulator must connect to the exact TCP port on which the SCPI device is listening.
* Multiple SCPI devices may use the same TCP port number as long as they are hosted on different IP addresses.
* Care must be taken to avoid TCP port conflicts when multiple services are hosted on the same device.


---

# 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/rt-lab/configure-ios/communication-protocol-ios/scpi/connect-the-hardware.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.
