Using SCADA Software for Energy Meter Monitoring via Modbus
Most industrial energy meters — Schneider ION/PM series, Siemens PAC, Carlo Gavazzi EM series, and similar submeters — report voltage, current, power, and cumulative kWh over Modbus TCP or RTU. Both SCADA Desktop and SCADA Cloud can connect to these meters directly as a Modbus device, so you don't need separate energy-management software just to see live power data on a dashboard.
Why Monitor Energy Meters Through SCADA
Energy meters are usually installed to satisfy a metering or billing requirement, but the data they produce is far more useful when it's visible on a live dashboard alongside the rest of your process. Pulling meter data into SCADA lets you correlate power consumption with production runs, spot abnormal load patterns before they show up on a utility bill, and trigger alarms on over-voltage, under-voltage, or demand spikes automatically instead of relying on someone checking a meter's front panel display.
Typical Energy Meter Register Map
While every manufacturer's register map differs, most three-phase energy meters expose a similar set of measurements over Modbus:
| Measurement | Typical Data Type | Notes |
|---|---|---|
| Line-to-neutral / line-to-line voltage | FLOAT32 | Per phase (A, B, C) |
| Current | FLOAT32 | Per phase, sometimes with a CT ratio scale factor |
| Active / reactive / apparent power | FLOAT32 | Total and often per-phase |
| Power factor | FLOAT32 | Total and per-phase |
| Frequency | FLOAT32 | Usually a single system-wide value |
| Cumulative energy (kWh) | FLOAT32 or UINT32 | Often split into two registers; check for a multiplier constant |
Step 1 — Identify the Meter's Register Map
Get the Modbus communication manual
Download the meter's Modbus register reference from the manufacturer's site (search "[meter model] Modbus register map"). Note the address, data type, and any scale factor for each measurement you want to monitor.
Step 2 — Add the Meter as a Modbus Device
SCADA Desktop
Go to Devices → Add Device → Modbus TCP (or RTU), enter the meter's IP address and port, or COM port and baud rate, along with the slave/unit ID from the meter's DIP switches or configuration menu.
SCADA Cloud
Go to Devices → Add Device → Modbus TCP and enter the same connection details. If the meter sits on an isolated network, expose it through a gateway or reverse proxy rather than opening inbound firewall rules.
Step 3 — Map Registers to Tags
Create one tag per measurement, matching the function code (commonly FC03 for holding registers or FC04 for input registers), register address, and data type from the meter's manual. Name tags clearly — Meter1_Voltage_A, Meter1_kWh_Total — so they're easy to find when you build the dashboard.
Step 4 — Build a Power Monitoring Dashboard
Add gauge widgets for real-time voltage, current, and power factor, and a trend chart for cumulative kWh to visualize consumption over shifts, days, or production runs. A status indicator tag can flag when the meter connection itself drops, so a communication fault doesn't get mistaken for a real zero-power reading.
Step 5 — Set Energy Alarms
Configure alarm rules for conditions that matter operationally — voltage outside the utility's normal supply band, power factor below a penalty threshold, or demand approaching a contracted limit. Both SCADA Desktop and SCADA Cloud support email notification on alarm trigger, so the right person is alerted without watching the dashboard continuously.
Test the Register Map Before the Meter Arrives
If the physical meter isn't installed yet, or you want to validate your tag configuration without risking a live billing meter, a Modbus slave simulator lets you configure holding registers that match the meter's documented map and set realistic values for voltage, current, and kWh. Build and test your dashboard and alarms against the simulator first, then simply repoint the same tags to the real meter's IP address once it's on the network. For meters on Modbus TCP specifically, a Modbus TCP simulator confirms the Ethernet connection and port behavior before you touch the production network. If you want a deeper walkthrough of simulating meter-style registers, see Modbus Energy Meter Testing on the Modbus blog.
Troubleshooting Common Issues
Values look wrong or wildly out of range
- Double-check the data type — a FLOAT32 register read as two separate INT16 values produces nonsense numbers.
- Try swapping byte/word order if the value is off by several orders of magnitude.
- Confirm any scale factor or CT/PT ratio specified in the meter's manual is applied in the tag configuration.
Device won't connect
- Verify the slave/unit ID matches the meter's configured address — a mismatch causes silent timeouts on Modbus TCP.
- For RTU meters, confirm baud rate and parity match the meter's DIP switch or menu settings exactly.
kWh value never seems to reset or resets unexpectedly
- Most meters report a non-resettable lifetime energy total by default — check if the manual documents a separate resettable register if that's what you need.
Monitor Your Energy Meters on Desktop or Cloud
SCADA Desktop: 15-day free trial, one-time license, fully local. SCADA Cloud: 60-day free trial, remote dashboards from any browser.
Start Free Cloud Trial → Download SCADA Desktop →Related Articles
- → SCADA Desktop vs Cloud SCADA: Which Is Right for Your Plant?
- → How to Connect a Modbus TCP PLC to SCADA Desktop
- → Energy Monitoring SCADA Overview
- → Modbus Slave Simulator — Test Without Physical Hardware
- → Modbus TCP Simulator — Ethernet Device Testing
- → Modbus Energy Meter Testing (Modbus Blog)
- → Back to SCADA Blog