mDAQ
The ruggedized field data-acquisition device that captures industrial sensor signals — pressure, flow, level, temperature — directly from the field, with no PLC in the loop. Four analog channels, digital I/O, cellular publish, on a 24 V box sized for the field.
4 analog (0–10 V / 4–20 mA, 16-bit) · 8 + 8 digital I/O (24 V) · Modbus TCP/RTU acquisition · HTTPS / MQTT publish · 4G / Wi-Fi / GPS · −10 to +85 °C · optional battery · IP65 / IP67-compatible (BOM-scoped).
Sensor signals, straight from the field — no PLC required.
mDAQ is a ruggedized field data-acquisition device. It captures industrial sensor signals — pressure, flow, level, temperature, and more — directly from the field over its analog and digital inputs, with no PLC in the loop, and publishes them over cellular or Wi-Fi. It is the field-replacement product: where the Edge Gateway bridges an existing PLC fleet, mDAQ removes the need for a PLC when the job is direct sensor acquisition and publishing. (It is an acquisition device — it does not replace a PLC's control, safety, sequencing, or interlock functions.)
It is the Data Acquisition pillar — see the capability story → /capabilities/data-acquisition. Combined with EdgeConnect and EREMOS V2, mDAQ completes an Elpis-only path from the sensor to the dashboard, with no third-party hardware in the chain. (The VAS vibration analyser is built on the mDAQ hardware platform, configured for specialized vibration acquisition and analytics — see Condition Monitoring.)
What it does — and what it removes from your BOM.
Direct sensor acquisition
Four analog channels (0–10 V or 4–20 mA, 16-bit) capture pressure, flow, level, temperature, and similar signals straight from the field.
Digital I/O
Eight 24 V digital inputs and eight 24 V digital outputs for status, counts, alarms, enables, and simple discrete signals.
Acquires and publishes
Modbus TCP/RTU acquisition where a device speaks it; HTTPS / MQTT publish to your broker or to EREMOS V2.
Remote-ready
4G, Wi-Fi, GPS, and an optional battery for sites without power or cable.
One mDAQ removes from the customer BOM:
- a standalone PLC for sensor acquisition;
- a separate cellular modem and edge appliance;
- a site-specific battery backup (available as an mDAQ option).
The device, in numbers.
| Analog inputs | 4 channels, 0–10 V or 4–20 mA, 16-bit, up to 860 S/s (per-channel / aggregate behavior + reporting interval confirmed during BOM scope) |
| Digital I/O | 8 × 24 V digital inputs · 8 × 24 V digital outputs |
| Acquisition protocols | Modbus TCP / Modbus RTU |
| Publish | HTTPS · MQTT |
| Connectivity | 4G (cellular) · Wi-Fi · GPS · optional Ethernet |
| Power | 24 V; optional battery for sites without power. Current draw, terminal type, and circuit-protection recommendation confirmed during BOM scope. |
| Environmental | −10 °C to +85 °C operating range |
| Enclosure | Ruggedized, 180 × 150 × 60 mm |
| Ingress protection | IP65 / IP67-compatible configurations can be scoped where a site requires it; final protection level, enclosure approach, and any certification requirements confirmed during BOM scope. (Compatibility, not a certified rating — no formal IP certification is currently claimed.) |
| Mounting | Field mount; cabinet clearance, cable routing, and antenna placement confirmed during BOM scope |
DAQ details confirmed during BOM scope
| Item | Confirmed during BOM scope |
|---|---|
| Analog input configuration | Per-channel voltage / current mode, loop power / excitation, signal conditioning, input protection, accuracy assumptions |
| Sampling + reporting | Whether 860 S/s is per-channel or aggregate, report interval, timestamping, buffering / offline retention; GPS as geo-context and/or time source |
| Digital I/O | Input thresholds, output type / current rating, sink / source behavior, protection |
| Power | Supply tolerance, current draw, battery runtime / charging, circuit protection |
| Mechanical | Mounting hardware, terminals / connectors, cable glands, antenna placement, enclosure approach, weight |
| Environment | Humidity / condensation, exposure, ingress-protection approach (IP65 / IP67-compatible), site compliance |
How it installs.
| Field wiring | Sensors wire directly to the analog/digital inputs — no PLC in between. Per-channel sensor type, loop power, and signal conditioning confirmed during BOM scope. |
| Power | 24 V; optional battery for sites without mains power. Current draw / terminal / protection confirmed during BOM scope. |
| Connectivity | 4G cellular for remote sites; Wi-Fi where available; GPS for location/geo-context. SIM / carrier / antenna and network/firewall assumptions confirmed during BOM scope. |
| Environment | −10 °C to +85 °C operating range. Exposure, humidity, and enclosure approach confirmed during BOM scope; IP65 / IP67-compatible configurations can be scoped where the placement requires it (no certified rating claimed). |
| Offline | Acquires locally and publishes when connectivity returns. |
| Mounting + site fit | Enclosure dimensions, mounting, cabinet clearance, and antenna/cabling confirmed during BOM scope. |
The device in the stack.
ArchitecturePanel.interactive variant.
For PLC-fronted floors, the Edge Gateway bridges existing PLCs instead — see → /edge-gateway. The full stack → /architecture.
One device, plus the path to the dashboard.
Packaging labels are illustrative until commercial packaging is approved; this section describes how the unit is bought + what it pairs with, not pricing.
mDAQ is a hardware unit, scoped against channel count + sensor types, site connectivity, power/battery needs, field environment, and mounting. On its own it acquires and publishes; combined with EdgeConnect and EREMOS V2 it completes an Elpis-only sensor-to-dashboard path. Bring the sensor list (signal types + ranges), the site connectivity (cellular vs. wired), power availability, and the environment; we'll scope the BOM. Contact Elpis for unit availability and BOM scoping; detailed pricing follows the BOM review. No pricing tables, SKU grids, or per-unit pricing on this page.
Built for the field, not the office.
Built for the field, not the office.
Ruggedized 180 × 150 × 60 mm enclosure, 24 V power with an optional battery, −10 °C to +85 °C operating range. Wires straight to the sensors it reads.
Remote-ready, offline-capable.
4G + Wi-Fi + GPS for sites without cable; acquires locally and publishes on reconnect. No PLC or industrial PC in the loop.
Formal third-party certifications are not currently claimed. Certification, ingress-protection, and site-compliance requirements are handled case-by-case during BOM scope; IP65 / IP67-compatible configurations can be scoped where required, but certified/rated claims are published only when formal evidence exists for the specific product/configuration.
What plant engineers ask.
What sensors can it read?
Four analog channels accept 0–10 V or 4–20 mA signals (16-bit, up to 860 S/s; per-channel / aggregate behavior + reporting interval confirmed during BOM scope) — pressure, flow, level, temperature, and similar. Eight 24 V digital inputs and eight 24 V digital outputs handle status, counts, alarms, enables, and simple discrete signals. Per-channel sensor type, loop power, and signal conditioning are confirmed during BOM scope.
How is mDAQ different from the Edge Gateway?
Edge Gateway bridges existing PLCs (Modbus TCP) to the network. mDAQ reads sensors directly with no PLC in the acquisition path — it removes the need for a PLC when the job is acquisition and publishing (it does not replace PLC control, safety, sequencing, or interlock functions). If you already have PLCs controlling the process, scope Edge Gateway; if you have sensors and no PLC — or want a separate acquisition path that bypasses the PLC — scope mDAQ. They can also be used together.
How does the data reach a dashboard?
mDAQ publishes over HTTPS or MQTT to your broker or to EREMOS V2. With EdgeConnect + EREMOS V2 it forms an Elpis-only sensor-to-dashboard path with no third-party hardware in the chain.
Can it run without mains power or a network?
Yes. An optional battery covers sites without power; 4G cellular publishes from remote sites. It acquires locally and publishes when connectivity returns.
What's the operating temperature and enclosure?
−10 °C to +85 °C, in a ruggedized 180 × 150 × 60 mm enclosure. Exposure and ingress-protection requirements are confirmed during BOM scope.
Is it certified? What about IP65 / IP67?
No formal third-party certifications are currently claimed. Certification, ingress-protection, and site-compliance requirements are handled case-by-case during BOM scope. Where a site requires IP65 / IP67-compatible protection, Elpis can scope an IP65 / IP67-compatible configuration or enclosure approach; formal certification or rating claims are published only when the specific product/configuration has the required certification or test evidence.
How does it relate to VAS?
VAS — the Vibration Analyser System — is built on the mDAQ hardware platform, configured for specialized vibration acquisition and analytics. If you need rotating-machinery vibration monitoring, see Condition Monitoring (VAS).
Can it be mounted outside an enclosure / exposed?
Cabinet placement, exposure, temperature, humidity, antenna placement, and ingress-protection requirements are confirmed during BOM scope. IP65 / IP67-compatible configurations can be scoped where required, but no formal certified IP rating is claimed unless evidence exists for the specific configuration.
Bring us your sensors and your site.
A sensor list (signal types + ranges), your site connectivity and power, and the environment it'll sit in — that's what we scope a BOM against. We confirm the channels, power, and mounting for your site, not for a brochure.