Remote I/O Gateway

Remote I/O Gateway – Modbus TCP Controller for Ethernet Monitoring and Relay Control

Sollae remote I/O gateways read digital inputs, switch relay outputs, and expose everything as Modbus TCP registers — so you can integrate into SCADA, HMI, or PLC systems, or control signals directly from a browser without modifying existing automation code.

Read more

What Remote I/O Controllers Are Used For in Practice

A remote I/O controller is typically purchased to reduce site visits, add visibility to signals from "dumb" equipment, and enable quick relay control over Ethernet. Real-world uses include:

  • Remote reset and power cycling of edge devices (routers, modems, PLCs, PCs) via relay outputs
  • Status monitoring — limit switches, door contacts, alarms, machine ready/fault signals
  • Simple remote control of gates, pumps, valves, and lighting circuits via low-voltage control relays
  • Distributed I/O extensions where adding cabling or a full PLC rack is not justified
  • Multi-site standardization using a consistent Modbus TCP register map across many locations

Modbus TCP Integration: SCADA / HMI / PLC + ModMap Commissioning

Sollae industrial I/O gateways expose inputs and relay outputs as standard Modbus TCP registers. You can integrate them into any Modbus TCP-capable SCADA, HMI, or PLC, and validate the wiring in minutes using the free ModMap tool.

  • Modbus TCP control and monitoring from software, mobile apps, HMI panels, or other Modbus TCP devices
  • Embedded web server with a preloaded page — and the option to customize the UI for operators
  • Multiple simultaneous TCP connections so more than one tool or operator can monitor the same I/O
  • Macro / logic automation for local rules that run without server dependency
Fit check: If your project is signal-first (digital inputs, relay outputs, web control), a remote I/O controller is the fastest path. If your project is protocol-conversion-first (serial fieldbus to Ethernet), start in the Modbus gateway category instead.

Compare Remote I/O Gateway Models: CIE-H12G vs CIE-H14G vs CIE-H10G

Model I/O + Interfaces Power / Environment Best for
CIE-H12G — Compact gateway Digital input (opto-isolated, up to 24 VDC) + relay outputs (pulse capable) + Ethernet; Modbus TCP + HTTP + Macro DC 5 V; industrial operating temperature range Small-site monitoring: a few signals, quick web and Modbus TCP integration
CIE-H14G — 4-port controller 4 DI (photo-coupler, max 24 VDC) + 4 relay DO (pulse capable) + RS-232 + Ethernet; Modbus TCP + web + macros DC 8.5–38 V wide-range supply; operating temp down to −40 °C Cabinet and field installs with multiple I/O points and flexible power input
CIE-H10G — 8-port controller 8 DI (photo-coupler, max 24 VDC) + 8 relay DO (pulse capable) + RS-232 + Ethernet; Modbus TCP + web UI; serial↔Ethernet conversion also supported DC 5 V; industrial enclosure options; suitable operating temperature for plant environments Higher I/O density: monitoring and relay control across many signals at distributed sites

Why Sollae Remote I/O Controllers Beat Generic Ethernet I/O Modules

Most Modbus TCP I/O modules provide register access — and then leave you to build the operator layer. Sollae remote I/O gateways are more deployment-ready for IT/OT teams:

  • Embedded web server with a customizable page: a usable interface from day one
  • Macro / logic formulas: run basic automation locally without a PLC change for every small rule
  • ModMap ecosystem: faster commissioning and troubleshooting than most generic devices
  • "Internet Switch" concept: link multiple controllers so inputs on one device can trigger outputs on another across the network
  • IT-friendly networking: modern IP stacks and access restrictions suitable for segmented OT networks
Quick pick: Start small with CIE-H12G. Scale to CIE-H14G for four I/O points and wide DC input. Choose CIE-H10G when you need eight I/O points or higher signal density.

Remote I/O Controller Buyer Checklist

  1. I/O count: how many digital inputs and relay outputs do you need today and in the next 12 months?
  2. Power constraints: need wide-range DC input? Choose CIE-H14G (DC 8.5–38 V).
  3. Control method: Modbus TCP for SCADA/HMI integration, or browser UI via the built-in web server.
  4. Autonomy: need local macro-based rules without server dependency? Confirm macro/logic capability on the chosen model.
  5. Multi-site scaling: plan distributed control? Consider "Internet Switch" style linking between controllers.
Skip to product grid

3 products