How to Get Energy Meter Data into Your Software (MQTT & Modbus)

Two paths, two use cases

Energy meter integration almost always reduces to one of two architectures: you want the meter to push data to your cloud or analytics platform as it happens, or you want your SCADA system or historian to poll the meter on demand. Titan supports both, and you can run them simultaneously.

The right choice depends on where your application lives and how it consumes data:

Both paths use open, vendor-neutral standards. There is no proprietary SDK to install, no REST API, and no dependency on Tech OVN's cloud to access your own meter data.

Path 2 — Modbus TCP/RTU to SCADA and historians

Modbus is the lingua franca of industrial automation. If your SCADA system, PLC, or historian already speaks Modbus, you can add Titan meters to your existing polling infrastructure without any change to your data acquisition layer — just add the meter as a new Modbus device.

Modbus TCP vs Modbus RTU

Titan supports both variants. Modbus TCP runs over standard Ethernet/WiFi — the same network the meter uses for MQTT — and is the preferred path for modern installations. Modbus RTU runs over RS485, a two-wire bus that supports multi-drop wiring where multiple meters share a single cable run to a Modbus master. RTU is common in panel-level deployments where meters are physically close to a local panel PC or PLC with an RS485 port.

Register map overview

Titan exposes its measurement parameters as Modbus holding registers (function code 03). The register map covers voltage, current, power (active, apparent, reactive), energy accumulators (kWh, kVAh, kVArh), power factor, frequency, demand, and per-phase values. A representative block structure — again, verify the exact register addresses against the Titan Modbus documentation for your firmware version before configuring your SCADA:

Register block (illustrative addresses):
  0x0000 – Voltage L1 (×0.1 V, uint16)
  0x0001 – Voltage L2
  0x0002 – Voltage L3
  0x0003 – Current L1 (×0.01 A, uint16)
  0x0004 – Current L2
  0x0005 – Current L3
  0x000A – Active Power Total (W, int32, 2 registers)
  0x000C – Apparent Power Total (VA, int32, 2 registers)
  0x0010 – Power Factor Average (×0.001, int16)
  0x0020 – Import kWh Total (×0.01, uint32, 2 registers)
  0x0024 – Import kVAh Total (×0.01, uint32, 2 registers)

Exact register addresses, data types, scaling factors, and supported function codes are specified in the Titan Modbus register map. Request the document from Tech OVN before configuring your SCADA or historian.

Multi-meter and multi-site aggregation

Individual meter integration is straightforward. Aggregating dozens of meters across multiple sites into a coherent data pipeline takes a little more architecture, but the building blocks are the same.

Single-site, multiple meters

On a single site, all Titan meters publish to the same broker (MQTT) or respond to the same Modbus master (TCP/RTU). Differentiate meters in MQTT by device ID in the topic; in Modbus by unit address. Your backend maps device IDs or unit addresses to physical locations — incomer, production floor feeder A, utilities panel — in a configuration table or device registry.

Multi-site into one pipeline

For multiple sites, include the site identifier in the MQTT topic hierarchy. Each site's meters publish under their own site prefix; your central broker aggregates everything. A subscriber at HQ receives readings from all sites, tagged by site and device, and routes them to the appropriate tenant, building, or reporting entity in your database.

For sites with unreliable WAN links, run a local MQTT broker at the site that buffers readings during outages and bridges to the central broker when connectivity resumes. This pattern keeps local data continuity without losing readings to network gaps.

You own the raw data

The guiding principle of Titan's integration design is that the data belongs to you. Titan is the accurate hardware layer — Class 0.5S per IEC 62053-22 — that puts clean electrical measurements into your broker or your SCADA system. What you build on top of it — dashboards, anomaly detection, ESG reports, tenant billing, AI load forecasting — is entirely your stack. You are not locked to Tech OVN's cloud, and you can change your analytics platform or historian without changing the meters. Contact Tech OVN to discuss your integration architecture before you deploy.