> 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/hypersim/configure-ios/communication-protocol-ios/c37.118-slave/connect-the-hardware.md).

# Connect the Hardware

## Connect devices using standard Ethernet cables

C37.118 communication operates over **Ethernet (TCP/IP)** and uses the simulator’s **built‑in LAN ports**. To establish a connection between the master and C37.118 slaves, simply connect the devices using **standard Ethernet cables**.

## Set IP addresses and subnets

For reliable C37.118 communication, all devices must follow standard IP networking practices:

* The master and all slaves must be located on the same IP subnet unless routing has been explicitly configured.
* Each physical device must have a **unique IP address** to avoid conflicts.
* A single physical device may host **multiple logical slaves**, each identified by a **unique** **slave ID**.

**The master will use the IP address of the simulator’s LAN port connected to the C37.118 network.**\
This is the source IP address from which the C37.118 data, configuration, and header message exchange occurs.

Example of valid subnet configuration:

* Master: `192.168.10.10 / 255.255.255.0`
* Slave 1: `192.168.10.20 / 255.255.255.0`
* Slave 2: `192.168.10.30 / 255.255.255.0`

## Set the C37.118 communication port

C37.118 does **not** standardize a single fixed default port. In practice:

* Many implementations use **TCP or UDP port 4712**, but
* Any port may be used as long as both the master and slave are configured identically.

Multiple slaves can use the **same port number** as long as they have **different IP addresses**, or they are logical slaves within the same physical device.

If your application requires custom port numbers, ensure the following:

* No firewall or security policy blocks the selected TCP or UDP port.
* The master is configured to connect to (or listen on) the correct port for each slave.
* The slave data rate and message types (data, configuration, header) are consistent across devices.


---

# 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/hypersim/configure-ios/communication-protocol-ios/c37.118-slave/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.
