Read voltage, current, power, power factor, frequency and energy from an Eastron SDM630 three-phase energy meter over Modbus RTU. This guide gives the full register map, FLOAT32 decoding, the FC04 input-register detail that trips people up, and how to get live data — and log it — with ModbusManager on Windows.
Windows 10/11 · free 14-day Pro trial · open the .json workspace inside the app
Every measurement is a FLOAT32 (two registers), read with function code 04. The left column is the 1-based number from the Eastron protocol; the second is the 0-based address that goes in the request frame.
| Register | Address | Measurement | Unit |
|---|---|---|---|
| 30001 | 0x0000 | Voltage L1-N | V |
| 30003 | 0x0002 | Voltage L2-N | V |
| 30005 | 0x0004 | Voltage L3-N | V |
| 30007 | 0x0006 | Current L1 | A |
| 30009 | 0x0008 | Current L2 | A |
| 30011 | 0x000A | Current L3 | A |
| 30013 | 0x000C | Active power L1 | W |
| 30015 | 0x000E | Active power L2 | W |
| 30017 | 0x0010 | Active power L3 | W |
| 30019 | 0x0012 | Apparent power L1 | VA |
| 30021 | 0x0014 | Apparent power L2 | VA |
| 30023 | 0x0016 | Apparent power L3 | VA |
| 30025 | 0x0018 | Reactive power L1 | VAr |
| 30027 | 0x001A | Reactive power L2 | VAr |
| 30029 | 0x001C | Reactive power L3 | VAr |
| 30031 | 0x001E | Power factor L1 | — |
| 30033 | 0x0020 | Power factor L2 | — |
| 30035 | 0x0022 | Power factor L3 | — |
| 30043 | 0x002A | Average voltage L-N | V |
| 30049 | 0x0030 | Sum of line currents | A |
| 30053 | 0x0034 | Total active power | W |
| 30057 | 0x0038 | Total apparent power | VA |
| 30061 | 0x003C | Total reactive power | VAr |
| 30063 | 0x003E | Total power factor | — |
| 30071 | 0x0046 | Frequency | Hz |
| 30073 | 0x0048 | Import active energy | kWh |
| 30075 | 0x004A | Export active energy | kWh |
| 30077 | 0x004C | Import reactive energy | kVArh |
| 30079 | 0x004E | Export reactive energy | kVArh |
| 30201 | 0x00C8 | Voltage L1-L2 | V |
| 30203 | 0x00CA | Voltage L2-L3 | V |
| 30205 | 0x00CC | Voltage L3-L1 | V |
| 30225 | 0x00E0 | Neutral current | A |
| 30235 | 0x00EA | Voltage THD L1-N | % |
| 30237 | 0x00EC | Voltage THD L2-N | % |
| 30239 | 0x00EE | Voltage THD L3-N | % |
| 30343 | 0x0156 | Total active energy (import + export) | kWh |
The protocol document lists further demand, per-phase energy and current-THD registers; the table above is what installers and integrators poll in practice. Configuration (baud rate, address, CT ratio on the MCT) lives in holding registers, read with FC03 and written with FC16.
The SDM630MCT measures through external current transformers instead of direct connection, but speaks the same Modbus: FC04, FLOAT32 pairs, and the measurement addresses above are identical. The practical differences are the CT ratio — set from the meter’s set-up menu (or the holding registers listed in the MCT protocol document) so the reported currents and powers are already scaled to primary values — and slightly different energy-resolution behaviour on some firmware. If your SDM630MCT readings look off by a constant factor, the CT ratio is the first thing to check. The free workspace on this page works with the MCT unchanged.
What actually goes over the RS-485 line when you read the L1 voltage from meter address 1.
| Bytes | Meaning |
|---|---|
Request01 04 00 00 00 02 71 CB | slave 1, FC04, address 0x0000 (register 30001), 2 registers, CRC |
Response01 04 04 43 66 66 66 A5 95 | slave 1, FC04, 4 data bytes, value, CRC |
Value0x43666666 | IEEE 754 float, high word first = 230.4 V |
Frequency works the same way at address 0x0046: request 01 04 00 46 00 02 90 1E, a 50.00 Hz answer is 01 04 04 42 48 00 00 6F EA. If you get 42 48 00 00 where you expected a power factor, you are reading 30071 — frequency — instead of 30063. And if the four data bytes come back as 66 66 43 66, your software has the word order the wrong way round: the SDM630 sends the high word first.
The SDM630 register layout is so widely used that other meters clone it — learn it once and you can read many devices.
Eastron’s SDM630 is the most widely deployed three-phase Modbus energy meter in the European prosumer and installer market — MID-certified, direct 100 A connection (or CT version), and around 100 Modbus registers covering everything from per-phase voltage to total energy. Its register map has become the de facto reference: the SDM630MCT and SDM630-TCP variants share it, and many Carlo Gavazzi and clone meters follow the same FLOAT32 layout. If you can read an SDM630, you can read most three-phase Modbus meters.
A free ModbusManager Pro workspace with the SDM630 register map already set up: Float32 tags and an energy-meter dashboard. Open it and point it at your meter.
The workspace polls input registers from 30001 (address 0, FC04) and decodes voltage, current, power, power factor and frequency as 32-bit floats — no scripting, no manual word-pairing. Every value lands on a clean dashboard ready to read. Set your meter’s slave ID and connection, and you have live data in seconds.
Open in ModbusManager Pro · 📋 Workspace → open · needs the Float32 tag type (v1.6+)
Set these from the meter’s front panel (SET menu), then match them in ModbusManager.
| Setting | Typical value |
|---|---|
| Protocol | Modbus RTU (2-wire RS-485) |
| Baud rate | 9600 (also 2400/4800/19200/38400) |
| Parity | None (1 stop bit) — default |
| Node address | 1–247 (set on meter) |
| Function code (measurements) | 04 — input registers |
| Function code (config) | 03 read / 16 write — holding registers |
| Data type | FLOAT32 (2 registers, big-endian) |
Baud rate is not only a setup detail — it caps how often a whole line of meters can be read. At 9600 baud a 10-register read of one SDM630 costs roughly 52 ms, so twenty meters on the same pair need about a second for one full pass. See for the timing per baud rate and how to pick an interval that holds.
From wiring to live values in a few minutes.
ModbusManager reads any SDM630 register directly, with built-in FLOAT32 decoding so you do not combine register pairs by hand, and a serial monitor to see every frame. The Standard edition ($49) covers polling, scaling and the serial monitor. The Pro edition ($119) adds drag-and-drop Modbus HMI software, a data logging Historian with CSV export for energy and load profiling, and an alarm system — all running locally on Windows, with no SCADA server or cloud account.
One SDM630 is easy. Ten of them on the same RS-485 line, read by a PLC that has a single Modbus connection, is a different job. ModbusManager Pro can poll every meter and republish just the values you need — total active power, per-phase currents, energy counters — as one common register map the PLC reads in a single request. The FLOAT32 pairs stay floats, or get scaled into integers if that is what the PLC block expects. The same rows can go to MQTT and Home Assistant too — see Modbus to MQTT, with a free SDM630 workspace.
Modbus gateway software →Download ModbusManager and connect to your meter over RTU. Free 14-day Pro trial — no credit card, no cloud.
Windows 10/11 · Standard $49 · Pro $119 one-time
We use Google Analytics cookies to see how the site is used. You can accept or decline — declining keeps analytics off. See our Privacy Policy.