Connecting Field Sensors to Your SCADA System Over Ethernet

In most industrial environments, the sensors that matter most are the ones furthest from the control room. Temperature probes on a transformer, flow meters at a remote pump station, contact closures on a security gate, analog signals from a weather station. These instruments generate the data that operators rely on, but getting that data reliably into a SCADA or historian system is where the complexity starts.

The traditional approach was to run dedicated signal cabling from every sensor back to a central I/O rack. That works when everything is in one building. It falls apart quickly when sensors are spread across a large site, mounted on remote infrastructure, or located hundreds of metres from the nearest control cabinet.

This is where Ethernet-based remote I/O and edge computing change the architecture.

The problem with long signal runs

Running analog and digital signal cables over long distances introduces real engineering challenges. Signal degradation on analog 4-20mA loops increases with cable length. Electromagnetic interference from nearby power cables or switching equipment corrupts readings. Every additional metre of copper adds cost, installation time, and potential failure points.

More fundamentally, traditional wiring doesn’t scale well. Adding a new sensor means pulling new cable, often through existing conduit that’s already at capacity. On brownfield sites, the cost of trenching and cable routing can dwarf the cost of the sensor itself.

Remote I/O: bring the conversion closer to the sensor

Ethernet remote I/O devices solve this by placing the analog-to-digital (or digital-to-Ethernet) conversion right at the sensor location. Instead of running long signal cables back to a central rack, you run a short cable from the sensor to a local I/O module, and the data travels the rest of the way over standard Ethernet.

The Moxa ioLogik E1200 Series is a good example of this approach. It’s a compact, DIN-rail mounted remote I/O unit with a built-in two-port Ethernet switch. Different models in the series handle digital inputs, digital outputs, analog inputs, analog outputs, RTD temperature sensors, and thermocouples, so you can match the I/O type to whatever sensors you’re connecting.

The built-in Ethernet switch is a practical detail that matters on site. It allows daisy-chaining: you run a single Ethernet cable from your network to the first I/O module, then loop from module to module. This eliminates the need for a separate Ethernet switch at every sensor location and significantly reduces cabling.

The ioLogik E1200 speaks Modbus TCP, EtherNet/IP, SNMP, and RESTful API simultaneously. That means your SCADA system, your IT monitoring tools, and your IIoT platform can all pull data from the same device without protocol conversion middleware.

Edge computing: aggregate, process, and forward

Remote I/O gets sensor data onto the Ethernet network. But in many architectures, you also need a local compute layer to aggregate data from multiple I/O points, perform basic processing or logic, handle protocol conversion, and manage upstream communication over cellular or WAN links.

This is where an edge computer like the Moxa UC-1222A fits. The UC-1222A sits on the same Ethernet network as the remote I/O modules, collects data via Modbus TCP or other protocols, and can run local applications for filtering, alarming, logging, or forwarding data to a central SCADA, historian, or cloud platform.

For sites without fixed network infrastructure, the UC-1222A’s mPCIe expansion slot accepts an LTE cellular module, providing the upstream backhaul. The data path becomes: sensor to ioLogik (short cable), ioLogik to UC-1222A (Ethernet), UC-1222A to central system (cellular).

This three-tier architecture (sensor, remote I/O, edge compute) keeps signal runs short, puts intelligence close to the data source, and maintains reliable upstream communication even at remote or unmanned sites.

Where this architecture works well

This pattern applies across a range of industrial scenarios:

• BESS sites where inverter and battery management data needs to be aggregated locally and forwarded to an energy management system.
• Substations and distribution points where environmental and equipment monitoring sensors feed into a utility SCADA platform.
• Remote pump stations and water treatment facilities where flow, pressure, and level sensors need reliable telemetry over cellular.
• Mining and resources operations where field instruments are distributed across large areas with limited fixed network coverage.

In each case, the combination of remote I/O at the sensor and edge compute for aggregation and communication provides a cleaner, more scalable architecture than running dedicated signal cables back to a central control room.

Available from Madison Technologies

Both the Moxa ioLogik E1200 Series and the Moxa UC Series edge computers are available through Madison Technologies. We can help with architecture planning, product selection across the I/O and compute range, and pre-configuration so devices arrive ready for deployment.

Get in touch with our team to discuss your remote monitoring or data acquisition project.