Remote I/O — couplers, modules and how to choose
How remote I/O systems are built (coupler + backplane + modules), IP20 vs IP67, fieldbus choice, diagnostics, addressing and a selection checklist.
Remote (distributed) I/O moves input and output modules out of the controller rack to where the signals are: a cabinet in the field, a machine section or directly onto the machine (IP67). The controller exchanges process data with the remote station over a fieldbus or industrial Ethernet.
How a station is built
| Part | Role |
|---|---|
| Coupler / interface module | Fieldbus slave/device (PROFINET IO device, EtherNet/IP adapter, Modbus TCP server, EtherCAT slave…); maps module data to the bus, handles diagnostics |
| Backplane | Internal bus between coupler and modules (often in the module housings themselves) |
| Power modules | Feed and segment the 24 V supply for electronics and field (potential groups) |
| I/O modules | Digital, analog, counter, temperature, IO-Link master, safety, communication modules |
| Terminal / base units | Wiring, often push-in, with or without separate field potential bus |
IP20 cabinet systems vs IP67 block I/O
- IP20 modular (ET 200SP, WAGO 750, u-remote, FLEX 5000, Axioline): many channel types, fine granularity, needs a cabinet.
- IP67 block (TBEN, ET 200eco, IP67 IO-Link masters): mounted on the machine with M12 connectors, short sensor cables, fewer channel types; IO-Link masters turn them into flexible hubs.
Choosing the bus
Use what the controller speaks natively: PROFINET with Siemens, EtherNet/IP with Rockwell, EtherCAT with Beckhoff/Omron motion, Modbus TCP when you need a simple, vendor-neutral link (SCADA, edge, small PLCs). Multiprotocol couplers detect the protocol automatically.
Addressing and data mapping
- PROFINET: device name + GSDML; I/O addresses come from the controller project.
- EtherNet/IP: IP address + EDS; data in input/output assemblies (connection size matters).
- Modbus TCP: IP address; register map from the manual (often inputs in input registers/discrete inputs, outputs in coils/holding registers with a fixed offset per module).
- Check process image byte order and analog formats (e.g. S7 range 0–27648 vs raw 0–32767 vs engineering units).
Diagnostics you should use
Channel diagnostics (wire break, short circuit, overflow), module pull/plug, supply voltage missing, coupler status LEDs and web servers. Map diagnostics to alarms — a "frozen" analog value with good quality is worse than a clear fault.
Selection checklist
- Fieldbus and controller compatibility (GSDML/EDS/ESI available, tested firmware).
- Channel count and types per station, spare capacity (typically 10–20 %).
- Environment: IP rating, temperature, vibration, Ex/hazardous areas.
- Potential groups and power budget per segment (see the 24 V supply article).
- Diagnostics level, hot swap, redundancy (S2/R1, DLR, MRP).
- Safety I/O (PROFIsafe, CIP Safety, FSoE) if required.
- Lifecycle, delivery time and the team's familiarity with the tooling.
Connections
Open in Knowledge Graph →Loading the map…
Sources
- SIMATIC ET 200MP / S7-1500 System Manual — Siemens
- PROFINET — technology — PI
- EtherNet/IP — ODVA
Updated 2026-10-04