Capture industrial signals directly from sensors — when there is no PLC, or when you want to bypass the one you have.
"What if I don't have a PLC, or I want to bypass it and read sensors directly?"
The field-acquisition hardware for this pillar.
mDAQ — General-purpose industrial data acquisition
Ruggedized acquisition device that captures signals from industrial instruments — flow meters, pressure transmitters, level transmitters, temperature probes, vibration sensors, 4-20 mA loop-powered transducers — directly from the field, no PLC in the loop. 4 analog channels (0-10 V or 4-20 mA), 16-bit, 860 S/s. 8 × 24 V digital inputs + 8 × 24 V digital outputs. Modbus TCP / RTU acquisition. HTTPS / MQTT publish. 4G, Wi-Fi, GPS, optional Ethernet. −10 °C to +85 °C operating range. Optional battery backup for sites without continuous power. 180 × 150 × 60 mm rugged enclosure.
HARDWARE APPLIANCE · 4 AI + 8 DI + 8 DO · 4G/WI-FI/GPS · 24 V DCData Acquisition is the field-replacement product — combine it with EdgeConnect and EREMOS V2 for a complete Elpis-only signal-to-dashboard path with no third-party hardware in the chain.
- A standalone PLC purchased solely for sensor acquisition (when you don't actually need ladder-logic control)
- A separate cellular modem and edge appliance (mDAQ has 4G / Wi-Fi / GPS / Ethernet built in)
- A site-specific battery backup for power-loss continuity (optional onboard battery available)
- A separate field-mountable signal-conditioning box for analog inputs
- The custom wiring complexity that comes from stitching together discrete acquisition + comms + power components
- Vendor coordination across 3-4 separate hardware suppliers for a single greenfield acquisition installation
Buyers
- Plant engineer (greenfield) — designing acquisition from scratch; no legacy PLC to integrate
- Plant engineer (retrofit / PLC-bypass) — existing PLC doesn't expose the signals the team needs; mDAQ reads sensors directly
- OT Architect — evaluating mDAQ as the field-acquisition layer of a broader Elpis-only deployment
Industries
- Oil & Gas (pipeline monitoring; surface flow, pressure, temperature)
- Water & Utilities (pump-station monitoring; flow + pressure analytics)
- Manufacturing — process (flow / temperature / pressure on tank, reactor, distillation systems)
- Mining & Construction (heavy-equipment hydraulic signal acquisition)
- Power & Energy (substation auxiliary signals; instrumentation outside the main SCADA path)
Deployment footprint
- Operating across India and the Middle East
- Offline-capable with optional battery — deployable at remote and unmanned sites (pipeline pump stations, mining outposts, well heads, off-grid water infrastructure) without continuous mains or network
- Multi-site fleets: per-gateway identity established at first start; per-site binding clean from day one
Data Acquisition is the field-acquisition layer of the Industrial Intelligence Stack.
How this differs from PLC-based data acquisition. If you already have a PLC and it already exposes the signals you need, read from the PLC — Connectivity & Edge handles that pillar with Modbus TCP, S7, and OPC UA Client. mDAQ exists for the cases the PLC doesn't cover: greenfield installs with no PLC yet, PLC-bypass retrofits where the controller is locked or doesn't expose the signal you need, and direct-sensor reads where adding a PLC layer would be more expensive than acquiring the signal directly. mDAQ is purpose-built for "the signal exists at the sensor and the PLC can't tell you about it."
Pillar 2 sits at the field edge — where physical signals first become digital. mDAQ captures sensor data directly from the field, then publishes via MQTT or HTTPS to Pillar 1 (Connectivity & Edge) for integration with everything else on the floor. From there, Pillar 5 (Operational Intelligence) turns the signals into OEE / alarms / reports. mDAQ also serves as the hardware platform for Pillar 4 specialty analytics (VAS / vibration). One acquisition platform, multiple application paths.
No PLC in the trust chain.
mDAQ reads sensors directly — no PLC in the trust chain, no third-party gateway interpreting your signals before they reach you. Signals are timestamped at the device with per-tag quality codes that propagate end-to-end. Offline-capable with optional battery; air-gapped sites are first-class. Configuration changes captured in the hash-chained audit log on the EdgeConnect pipeline that mDAQ feeds.
Read the full operational trust posture → /security
Looking for the same thing from another angle?
Bring us your sensor list. We'll scope a BOM.
Whether you're scoping a greenfield install with no existing PLC infrastructure, or a retrofit where the existing PLC can't expose the signals you need — bring us the sensor list and we'll scope the BOM. Real hardware against real signals, not slideware.