> For the complete documentation index, see [llms.txt](https://docs.voltmasters.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voltmasters.io/dso-rtu/io-module-installation.md).

# Installing the IO modules

The IO modules provide the digital outputs and inputs that DSO RTU uses, for example the [hardware emergency stop](/dso-rtu/io-module-emergency-stop.md). **How many modules you need, and where they go, depends on the physical layout of your installation**, because every relay has to be wired to the asset or switchgear it controls.

### The hardware

* **Channels:** 6 digital inputs (DI) and 6 relay outputs (DO) per module.
* **Communication:** Modbus TCP/IP over the installation network.
* **Power:** 24 VDC nominal (12–36 VDC), ≈ 4.5 W per module, DIN-rail or wall mounted (27.8 × 124 × 84 mm).
* The relay outputs are potential-free contacts wired into the local safety/stop circuit, each rated **max. 5 A resistive or 2 A inductive at 250 VAC / 30 VDC**; the digital inputs can be used for status feedback.
* Field wiring up to 14 AWG (≈ 2.5 mm²) on screw terminals.

See [Technical specifications](/dso-rtu/io-extension/io-extension-specifications.md) for the complete data, including what the relay outputs may and may not switch directly.

### How many modules do I need?

There is no fixed number; it follows the **physical setup**:

* A single module can serve every relay and input that is **near it** (in the same cabinet).
* If outputs or inputs are needed in **physically separate cabinets**, each of those cabinets needs its **own** module, because the wiring to the relays stays local to the cabinet.

So a compact, single-cabinet installation may need just one module, while an installation spread over several cabinets needs one module per cabinet that has to be controlled.

### Placement and cabling

**Single cabinet**

Place the module in the cabinet, close to the assets and the relay(s) it drives.

**Separate cabinets**

For each additional cabinet:

1. Run a **network (Ethernet) cable** from the installation network to the cabinet.
2. Place an **IO module** inside that cabinet.
3. Wire the cabinet's relays and inputs to that local module.

This keeps the safety wiring short and local, while every module stays reachable by the controller over the network.

### Layout

```
                  ┌───────────────────────────┐
                  │    Voltmasters controller  │
                  └───────────────┬────────────┘
                                  │
                  installation network (Modbus TCP)
                                  │
        ┌─────────────────────────┼─────────────────────────┐
        │                         │                         │
   network cable             network cable             network cable
        │                         │                         │
┌───────▼────────┐        ┌───────▼────────┐        ┌───────▼────────┐
│   Cabinet A    │        │   Cabinet B    │        │   Cabinet C    │
│  ┌──────────┐  │        │  ┌──────────┐  │        │  ┌──────────┐  │
│  │ IO module│  │        │  │ IO module│  │        │  │ IO module│  │
│  └────┬─────┘  │        │  └────┬─────┘  │        │  └────┬─────┘  │
│  relays/inputs │        │  relays/inputs │        │  relays/inputs │
│  (local assets)│        │  (local assets)│        │  (local assets)│
└────────────────┘        └────────────────┘        └────────────────┘

   One module per cabinet; the number of modules follows the layout.
```

### Network and power

* Connect each module to the **installation network** (the same network the controller uses for Modbus TCP).
* Give each module a **fixed IP address**, and power it from the cabinet's 24 VDC supply (12–36 VDC, ≈ 4.5 W per module).
* Note each module's **IP address, port and Modbus slave ID**, since you need them when adding the device on the platform.

{% hint style="info" icon="lightbulb" %}
Each module has **two Ethernet ports** that act as a small switch, so modules can be **daisy-chained** instead of each taking up a port on a switch. Remember that a daisy chain is a single path: a module that loses power also cuts off the modules behind it. For a module that carries an emergency stop, prefer a direct link to the switch.
{% endhint %}

For converting RS-485 devices to Modbus TCP elsewhere in the installation, see [RS485 to Modbus TCP adapters](/getting-started/adding-and-verifying-devices/rs485-to-modbus-tcp-adapters.md).

### Next steps

Once the modules are installed and reachable on the network, add each one on the platform and assign its outputs. See [IO module emergency stop](/dso-rtu/io-module-emergency-stop.md) for the emergency-stop configuration, and [Technical specifications](/dso-rtu/io-extension/io-extension-specifications.md) for the module's electrical limits.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.voltmasters.io/dso-rtu/io-module-installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.