- Home
- Modbus register maps
- KOSTAL
- KOSTAL Smart Energy Meter (KSEM G1 / G2)
Energy meter · Modbus register map
KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2) Modbus register map
Updated 17 November 2026
The KSEM is a three-phase energy meter and energy manager. As a Modbus RTU slave (RS485 A/B) or Modbus TCP slave (port 502, TLS on 802) it exposes OBIS-coded power and energy registers, a plug-and-play identification block and a SunSpec meter block. This map covers the internal instantaneous values (0-145), the 64-bit energy counters (512-791) and the identification block (8192-8249).
This page lists 69 Modbus registers for the KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2) — 0 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from KOSTAL’s own free documentation (linked below) and checked against it.
- Manufacturer
- KOSTAL
- Model
- KOSTAL Smart Energy Meter (KSEM G1 / G2)
- Equipment type
- Energy meter
- Registers
- 69 (0 writable)
- Transport
- Modbus RTU, Modbus TCP
- Default unit ID
- Not stated
- TCP port
- 502
- Documented addressing
- 0-based (the number printed is the address on the wire)
- 32-bit word order
- ABCD high word first (big-endian)
- Firmware
- KSEM software 2.6.0
- Also known as
- KSEM, KSEM G1, KSEM G2, KOSTAL Smart Energy Meter
Integration notes: KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2)
Turn on the Modbus TCP slave in the KSEM web UI and poll the listed blocks of holding registers 0-145 for live values and 512-791 for 64-bit energy counters, high word first, splitting reads at the gaps. Net grid power is Active power+ minus Active power-.
Minimum registers to map
Addresses are 0-based wire addresses. Enough to monitor and run the unit; map more as the job needs.
| Register | Name | Type | Why | Access |
|---|---|---|---|---|
| HR 0 | Active power+ | UINT32 ABCD | Active power import (0.1 W) | Read |
| HR 2 | Active power- | UINT32 ABCD | Active power export (0.1 W) | Read |
| HR 26 | Supply frequency | UINT32 ABCD | Grid frequency | Read |
| HR 62 | Voltage (L1) | UINT32 ABCD | Voltage L1 | Read |
| HR 60 | Current (L1) | UINT32 ABCD | Current L1 | Read |
| HR 512 | Active energy+ | UINT64 ABCD | Imported active energy (0.1 Wh) | Read |
| HR 516 | Active energy- | UINT64 ABCD | Exported active energy (0.1 Wh) | Read |
| HR 8228 | SerialNumber | STRING[32] | Serial number for identification | Read |
Enable Modbus control & writes
In the KSEM web interface open the Modbus settings and activate the TCP slave (and optionally TLS), or set RS485 A or B to Modbus RTU slave; save the settings before polling.
Byte order & addressing
- Values are unsigned with separate + and - registers instead of one signed value, except power factor (int32).
- With TLS enabled the slave only answers on port 802, not 502.
- 64-bit energy counters must be read as all four registers in one request.
Network setup
- Default TCP port 502; encrypted Modbus on port 802.
- A self-signed TLS client certificate must be accepted in the KSEM certificate list before reads are allowed.
Watch out for
- Reading across a gap between listed registers returns exception 0x02, so split polls at the gaps (e.g. 0-7, 16-27, 40-47).
KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2) Modbus registers
Address = 0-based wire address (the documented number is shown under it when it differs) · Order: ABCD = high word first, CDAB = low word first · Scale: engineering value = raw × scale.
| Table | Address | Name | Description | Type | Order | Scale | Units | Access | Values / bits |
|---|---|---|---|---|---|---|---|---|---|
| HR | 0 | Active power+ | OBIS 1-0:1.4.0*255 | UINT32 | ABCD | × 0.1 | W | Read | |
| HR | 2 | Active power- | OBIS 1-0:2.4.0*255 | UINT32 | ABCD | × 0.1 | W | Read | |
| HR | 4 | Reactive power+ | OBIS 1-0:3.4.0*255 | UINT32 | ABCD | × 0.1 | var | Read | |
| HR | 6 | Reactive power- | OBIS 1-0:4.4.0*255 | UINT32 | ABCD | × 0.1 | var | Read | |
| HR | 16 | Apparent power+ | OBIS 1-0:9.4.0*255 | UINT32 | ABCD | × 0.1 | VA | Read | |
| HR | 18 | Apparent power- | OBIS 1-0:10.4.0*255 | UINT32 | ABCD | × 0.1 | VA | Read | |
| HR | 24 | Power factor | OBIS 1-0:13.4.0*255 | INT32 | ABCD | × 0.001 | Read | ||
| HR | 26 | Supply frequency | OBIS 1-0:14.4.0*255 | UINT32 | ABCD | × 0.001 | Hz | Read | |
| HR | 40 | Active power+ (L1) | OBIS 1-0:21.4.0*255 | UINT32 | ABCD | × 0.1 | W | Read | |
| HR | 42 | Active power- (L1) | OBIS 1-0:22.4.0*255 | UINT32 | ABCD | × 0.1 | W | Read | |
| HR | 44 | Reactive power+ (L1) | OBIS 1-0:23.4.0*255 | UINT32 | ABCD | × 0.1 | var | Read | |
| HR | 46 | Reactive power- (L1) | OBIS 1-0:24.4.0*255 | UINT32 | ABCD | × 0.1 | var | Read | |
| HR | 56 | Apparent power+ (L1) | OBIS 1-0:29.4.0*255 | UINT32 | ABCD | × 0.1 | VA | Read | |
| HR | 58 | Apparent power- (L1) | OBIS 1-0:30.4.0*255 | UINT32 | ABCD | × 0.1 | VA | Read | |
| HR | 60 | Current (L1) | OBIS 1-0:31.4.0*255 | UINT32 | ABCD | × 0.001 | A | Read | |
| HR | 62 | Voltage (L1) | OBIS 1-0:32.4.0*255 | UINT32 | ABCD | × 0.001 | V | Read | |
| HR | 64 | Power factor (L1) | OBIS 1-0:33.4.0*255 | INT32 | ABCD | × 0.001 | Read | ||
| HR | 80 | Active power+ (L2) | OBIS 1-0:41.4.0*255 | UINT32 | ABCD | × 0.1 | W | Read | |
| HR | 82 | Active power- (L2) | OBIS 1-0:42.4.0*255 | UINT32 | ABCD | × 0.1 | W | Read | |
| HR | 84 | Reactive power+ (L2) | OBIS 1-0:43.4.0*255 | UINT32 | ABCD | × 0.1 | var | Read | |
| HR | 86 | Reactive power- (L2) | OBIS 1-0:44.4.0*255 | UINT32 | ABCD | × 0.1 | var | Read | |
| HR | 96 | Apparent power+ (L2) | OBIS 1-0:49.4.0*255 | UINT32 | ABCD | × 0.1 | VA | Read | |
| HR | 98 | Apparent power- (L2) | OBIS 1-0:50.4.0*255 | UINT32 | ABCD | × 0.1 | VA | Read | |
| HR | 100 | Current (L2) | OBIS 1-0:51.4.0*255 | UINT32 | ABCD | × 0.001 | A | Read | |
| HR | 102 | Voltage (L2) | OBIS 1-0:52.4.0*255 | UINT32 | ABCD | × 0.001 | V | Read | |
| HR | 104 | Power factor (L2) | OBIS 1-0:53.4.0*255 | INT32 | ABCD | × 0.001 | Read | ||
| HR | 120 | Active power+ (L3) | OBIS 1-0:61.4.0*255 | UINT32 | ABCD | × 0.1 | W | Read | |
| HR | 122 | Active power- (L3) | OBIS 1-0:62.4.0*255 | UINT32 | ABCD | × 0.1 | W | Read | |
| HR | 124 | Reactive power+ (L3) | OBIS 1-0:63.4.0*255 | UINT32 | ABCD | × 0.1 | var | Read | |
| HR | 126 | Reactive power- (L3) | OBIS 1-0:64.4.0*255 | UINT32 | ABCD | × 0.1 | var | Read | |
| HR | 136 | Apparent power+ (L3) | OBIS 1-0:69.4.0*255 | UINT32 | ABCD | × 0.1 | VA | Read | |
| HR | 138 | Apparent power- (L3) | OBIS 1-0:70.4.0*255 | UINT32 | ABCD | × 0.1 | VA | Read | |
| HR | 140 | Current (L3) | OBIS 1-0:71.4.0*255 | UINT32 | ABCD | × 0.001 | A | Read | |
| HR | 142 | Voltage (L3) | OBIS 1-0:72.4.0*255 | UINT32 | ABCD | × 0.001 | V | Read | |
| HR | 144 | Power factor (L3) | OBIS 1-0:73.4.0*255 | INT32 | ABCD | × 0.001 | Read | ||
| HR | 512 | Active energy+ | OBIS 1-0:1.8.0*255 | UINT64 | ABCD | × 0.1 | Wh | Read | |
| HR | 516 | Active energy- | OBIS 1-0:2.8.0*255 | UINT64 | ABCD | × 0.1 | Wh | Read | |
| HR | 520 | Reactive energy+ | OBIS 1-0:3.8.0*255 | UINT64 | ABCD | × 0.1 | varh | Read | |
| HR | 524 | Reactive energy- | OBIS 1-0:4.8.0*255 | UINT64 | ABCD | × 0.1 | varh | Read | |
| HR | 544 | Apparent energy+ | OBIS 1-0:9.8.0*255 | UINT64 | ABCD | × 0.1 | VAh | Read | |
| HR | 548 | Apparent energy- | OBIS 1-0:10.8.0*255 | UINT64 | ABCD | × 0.1 | VAh | Read | |
| HR | 592 | Active energy+ (L1) | OBIS 1-0:21.8.0*255 | UINT64 | ABCD | × 0.1 | Wh | Read | |
| HR | 596 | Active energy- (L1) | OBIS 1-0:22.8.0*255 | UINT64 | ABCD | × 0.1 | Wh | Read | |
| HR | 600 | Reactive energy+ (L1) | OBIS 1-0:23.8.0*255 | UINT64 | ABCD | × 0.1 | varh | Read | |
| HR | 604 | Reactive energy- (L1) | OBIS 1-0:24.8.0*255 | UINT64 | ABCD | × 0.1 | varh | Read | |
| HR | 624 | Apparent energy+ (L1) | OBIS 1-0:29.8.0*255 | UINT64 | ABCD | × 0.1 | VAh | Read | |
| HR | 628 | Apparent energy- (L1) | OBIS 1-0:30.8.0*255 | UINT64 | ABCD | × 0.1 | VAh | Read | |
| HR | 672 | Active energy+ (L2) | OBIS 1-0:41.8.0*255 | UINT64 | ABCD | × 0.1 | Wh | Read | |
| HR | 676 | Active energy- (L2) | OBIS 1-0:42.8.0*255 | UINT64 | ABCD | × 0.1 | Wh | Read | |
| HR | 680 | Reactive energy+ (L2) | OBIS 1-0:43.8.0*255 | UINT64 | ABCD | × 0.1 | varh | Read | |
| HR | 684 | Reactive energy- (L2) | OBIS 1-0:44.8.0*255 | UINT64 | ABCD | × 0.1 | varh | Read | |
| HR | 704 | Apparent energy+ (L2) | OBIS 1-0:49.8.0*255 | UINT64 | ABCD | × 0.1 | VAh | Read | |
| HR | 708 | Apparent energy- (L2) | OBIS 1-0:50.8.0*255 | UINT64 | ABCD | × 0.1 | VAh | Read | |
| HR | 752 | Active energy+ (L3) | OBIS 1-0:61.8.0*255 | UINT64 | ABCD | × 0.1 | Wh | Read | |
| HR | 756 | Active energy- (L3) | OBIS 1-0:62.8.0*255 | UINT64 | ABCD | × 0.1 | Wh | Read | |
| HR | 760 | Reactive energy+ (L3) | OBIS 1-0:63.8.0*255 | UINT64 | ABCD | × 0.1 | varh | Read | |
| HR | 764 | Reactive energy- (L3) | OBIS 1-0:64.8.0*255 | UINT64 | ABCD | × 0.1 | varh | Read | |
| HR | 784 | Apparent energy+ (L3) | OBIS 1-0:69.8.0*255 | UINT64 | ABCD | × 0.1 | VAh | Read | |
| HR | 788 | Apparent energy- (L3) | OBIS 1-0:70.8.0*255 | UINT64 | ABCD | × 0.1 | VAh | Read | |
| HR | 8192 | ManufacturerID | Fixed TQ maker ID, reads 0x5233. | UINT16 | Read | ||||
| HR | 8193 | ProductID | Hardware type of the meter. | UINT16 | Read | 18498 = HW v1 (0x4842); 18514 = HW v2 (0x4852); 18530 = HW v3 (0x4862) | |||
| HR | 8194 | ProductVersion | Hardware revision of the processor board. | UINT16 | Read | ||||
| HR | 8195 | FirmwareVersion | Firmware revision, e.g. 0x0103 = 1.3.x. | UINT16 | Read | ||||
| HR | 8196 | VendorName | Vendor name, NUL padded. | STRING[32] | Read | ||||
| HR | 8212 | ProductName | Product name, NUL padded. | STRING[32] | Read | ||||
| HR | 8228 | SerialNumber | Serial number, NUL padded. | STRING[32] | Read | ||||
| HR | 8244 | MeasuringInterval | Measuring interval of the metering chip. | UINT16 | ms | Read | |||
| HR | 8245 | UNIXTimestamp | Current UNIX time in milliseconds. | UINT64 | ABCD | ms | Read | ||
| HR | 8249 | ModbusSpecVersion | Version of the Modbus specification in use. | UINT16 | Read |
Notes on this map
- Word order is stated in section 2.2: in a multi-register value the lower address holds the most significant bits, and the worked examples combine register 0 x 2^16 + register 1 and registers 512-515 most significant first.
- Each import/export quantity is split into a '+' and a '-' register, both unsigned; net power = (+) minus (-).
- The SunSpec block at 40000-40177, the static/dynamic E-mobility and energy-flow areas, group registers and sensor registers are not included in this file.
- Register 146 ('Minimum active power+ * 3', no OBIS code) and the MAC address at 8250-8252 (outside the stated PnP range) are left out.
- Reading an address not listed in the tables returns exception 0x02 (illegal data address); request each multi-register value in a single read.
Check it against the live device. A register map tells you what the controller can expose; the unit in front of you may differ by firmware or options. Read a few registers and compare them with the unit’s own display; for a 32-bit value the float and byte-order decoder shows all four word orders at once, so a wrong word order or scale is obvious. New to this? Read what a register map is and why addresses are off by one.
Questions about the KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2)
What Modbus registers does the KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2) have?
This map lists 69 registers: 69 holding registers. 0 of them can be written. Registers vary with firmware, options and configuration, so confirm against the device.
Are the KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2) Modbus addresses 0-based or 1-based?
The manufacturer's document numbers registers 0-based (the number printed is the address on the wire). Every address on this page is the 0-based wire address you put in the request; the documented number is shown under it where it differs. The register tables give decimal and hex addresses that are used directly on the wire: the manual's own example reads active power+ from holding registers 0 and 1 and energy from registers 512-515.
What byte order does the KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2) use for 32-bit values?
Multi-register values in this map use ABCD (high word first (big-endian)). Set your client to this order for every 32/64-bit value in the table.
What are the minimum Modbus registers to integrate the KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2)?
Start with HR 0 Active power+ (Active power import (0.1 W)); HR 2 Active power- (Active power export (0.1 W)); HR 26 Supply frequency (Grid frequency); HR 62 Voltage (L1) (Voltage L1); HR 60 Current (L1) (Current L1); HR 512 Active energy+ (Imported active energy (0.1 Wh)); HR 516 Active energy- (Exported active energy (0.1 Wh)); HR 8228 SerialNumber (Serial number for identification).
How do I enable Modbus control of the KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2)?
In the KSEM web interface open the Modbus settings and activate the TCP slave (and optionally TLS), or set RS485 A or B to Modbus RTU slave; save the settings before polling.
Where is the official KOSTAL KOSTAL Smart Energy Meter (KSEM G1 / G2) Modbus documentation?
The source is KSEM G1/G2 KOSTAL Smart Energy Meter - Interface Description MODBUS (DOC02348405-0007), revision 2025-03-13, published free by KOSTAL at https://www.kostal-solar-electric.com/fileadmin/downloadcenter/kse/BA_KOSTAL_Interface_KSEM_EN.pdf.
Other power & energy meters register maps
- Power meter (power factor controller)
Lovato Electric DCRL3 / DCRL5 / DCRL8 power factor controllers
DCRL3, DCRL5 and DCRL8 automatic power factor controllers with optical port or EXP10xx modules (Modbus TCP on DCRL8 only), per protocol document I427 GB 05 20.
Also known as: DCRL3, DCRL5, DCRL8, DCRL 3, DCRL 5, DCRL 8 - Energy meter (DIN-rail, three-phase, MID)
Lumel NMID31 / NMID32 three-phase energy meter
Lumel NMID31 and NMID32 DIN-rail single/three-phase energy meters with RS-485 Modbus RTU, per their interface manual.
Also known as: NMID31, NMID32 - Power meter (modular multi-circuit energy meter)
Northern Design multicube modular meter, SM352 sub-metering slave (Modbus RTU)
Each SM352 slave meter in a multicube system with the RTU485 Modbus module, per comms manual Rev Beta 1.02 (March 2011).
Also known as: MultiCube, ND multicube, SM352, RTU485 - Sensor / multi-parameter controller
ProMinent DULCOMETER diaLog DACa multi-parameter controller (Modbus RTU)
diaLog DACa controllers with the Modbus RTU interface option, per software manual BA DM 212 12/15.
Also known as: DACa, diaLog DACa, DULCOMETER DACa - Power meter
Rishabh Instruments RISH Delta VAF NX volt/amp/frequency panel meter
Rishabh RISH Delta VAF NX programmable panel meters with RS-485 Modbus RTU, per operating manual AMAN-00IM-0118 Rev. F.
Also known as: RISH Delta VAF NX, Delta VAF NX, RISH Delta VAF - Energy meter
Rishabh Instruments RISH EM 3490 SS single-phase energy meter
Rishabh RISH EM 3490 SS single-phase energy meters with the optional RS-485 Modbus output, per the 1-phase manual Rev D.
Also known as: RISH EM 3490 SS 1P, EM3490SS 1P, EM 3490 SS single-phase
All power & energy meters Modbus register maps →
Source: KSEM G1/G2 KOSTAL Smart Energy Meter - Interface Description MODBUS · DOC02348405-0007 · rev. 2025-03-13. Register numbers, types, scaling and units are reproduced as published; descriptions are our own.