Skip to content
Proxus 2.0.1 Licence and sign-in fixes after the 2.0 upgrade Release notes
Book a demo

Klemsan KLEA 320P Modbus register map

Also searched as: KLEA · KLEA Energy Analyzer · 606100

48 Modbus registers of the Klemsan KLEA 320P, with the address on the wire, the 30001-style reference, data type, byte order, unit and scale. Transcribed from KLEA Energy Analyzer User Manual (2022-08-24).

KLEA 320P network energy analyzer with RS485 Modbus RTU; measurements are 32-bit floats in holding registers.

Registers Read it by name
Device type
Power analyser
Registers
48
Interfaces
Modbus RTU
Byte order (multi-register values)
ABCD

Hardware verification

Not yet verified on hardware. The map is transcribed from the vendor document and checked against it by script; check the first readings against the device display.

Verify it on your device What the levels mean

Connection notes

  • Read with function 03; the manual's example frame reads address 0x0000, count 2, and decodes 43 5D 36 E0 as 221.2143555 V (big-endian float).
  • Every value spans two registers; read them in pairs.
  • Tariff indexes are also available as 64-bit floats from register 1366 onward; only the 32-bit copies are listed here.

Registers

Grouped as in the vendor document.

Voltage 8 registers
Name and key Reference Address Type Byte order Unit Scale
Average voltage of three phasesvoltage_avg_ln 40001 0x0000 float32 ABCD V
Voltage V1-2voltage_l1_l2 40015 0x000E float32 ABCD V
Voltage V2-3voltage_l2_l3 40017 0x0010 float32 ABCD V
Voltage V3-1voltage_l3_l1 40019 0x0012 float32 ABCD V
Average line to line voltagevoltage_avg_ll 40021 0x0014 float32 ABCD V
Phase 1 voltagevoltage_l1_n 40029 0x001C float32 ABCD V
Phase 2 voltagevoltage_l2_n 40153 0x0098 float32 ABCD V
Phase 3 voltagevoltage_l3_n 40277 0x0114 float32 ABCD V
Current 5 registers
Name and key Reference Address Type Byte order Unit Scale
Total current of three phasescurrent_total 40003 0x0002 float32 ABCD A
Neutral currentcurrent_neutral 40023 0x0016 float32 ABCD A
Phase 1 currentcurrent_l1 40031 0x001E float32 ABCD A
Phase 2 currentcurrent_l2 40155 0x009A float32 ABCD A
Phase 3 currentcurrent_l3 40279 0x0116 float32 ABCD A
Power 12 registers
Name and key Reference Address Type Byte order Unit Scale
Total active poweractive_power_total 40005 0x0004 float32 ABCD W
Total reactive powerreactive_power_total 40007 0x0006 float32 ABCD var
Total apparent powerapparent_power_total 40009 0x0008 float32 ABCD VA
Phase 1 active poweractive_power_l1 40033 0x0020 float32 ABCD W
Phase 1 reactive powerreactive_power_l1 40035 0x0022 float32 ABCD var
Phase 1 apparent powerapparent_power_l1 40037 0x0024 float32 ABCD VA
Phase 2 active poweractive_power_l2 40157 0x009C float32 ABCD W
Phase 2 reactive powerreactive_power_l2 40159 0x009E float32 ABCD var
Phase 2 apparent powerapparent_power_l2 40161 0x00A0 float32 ABCD VA
Phase 3 active poweractive_power_l3 40281 0x0118 float32 ABCD W
Phase 3 reactive powerreactive_power_l3 40283 0x011A float32 ABCD var
Phase 3 apparent powerapparent_power_l3 40285 0x011C float32 ABCD VA
Frequency 3 registers
Name and key Reference Address Type Byte order Unit Scale
Phase 1 frequencyfrequency_l1 40043 0x002A float32 ABCD Hz
Phase 2 frequencyfrequency_l2 40167 0x00A6 float32 ABCD Hz
Phase 3 frequencyfrequency_l3 40291 0x0122 float32 ABCD Hz
Energy 4 registers
Name and key Reference Address Type Byte order Unit Scale
Tariff 1 import active indext1_import_active_energy 40405 0x0194 float32 ABCD kWh
Tariff 1 export active indext1_export_active_energy 40419 0x01A2 float32 ABCD kWh
Tariff 1 import reactive indext1_import_reactive_energy 40433 0x01B0 float32 ABCD kvarh
Tariff 1 export reactive indext1_export_reactive_energy 40447 0x01BE float32 ABCD kvarh
Power factor 8 registers
Name and key Reference Address Type Byte order Unit Scale
Average cos phi of three phasescos_phi_avg 40011 0x000A float32 ABCD
Average power factor of three phasespower_factor_avg 40013 0x000C float32 ABCD
Phase 1 cos phicos_phi_l1 40039 0x0026 float32 ABCD
Phase 1 power factorpower_factor_l1 40041 0x0028 float32 ABCD
Phase 2 cos phicos_phi_l2 40163 0x00A2 float32 ABCD
Phase 2 power factorpower_factor_l2 40165 0x00A4 float32 ABCD
Phase 3 cos phicos_phi_l3 40287 0x011E float32 ABCD
Phase 3 power factorpower_factor_l3 40289 0x0120 float32 ABCD
Quality 8 registers
Name and key Reference Address Type Byte order Unit Scale
Total voltage harmonic distortionthd_voltage_total 40025 0x0018 float32 ABCD %
Total current harmonic distortionthd_current_total 40027 0x001A float32 ABCD %
Phase 1 voltage THDthd_voltage_l1 40045 0x002C float32 ABCD %
Phase 1 current THDthd_current_l1 40047 0x002E float32 ABCD %
Phase 2 voltage THDthd_voltage_l2 40169 0x00A8 float32 ABCD %
Phase 2 current THDthd_current_l2 40171 0x00AA float32 ABCD %
Phase 3 voltage THDthd_voltage_l3 40293 0x0124 float32 ABCD %
Phase 3 current THDthd_current_l3 40295 0x0126 float32 ABCD %

Source documents

  • KLEA Energy Analyzer User Manual , Klemsan, 2022-08-24 (accessed 2026-11-09) Section 4, Table 4-4 Read-only Data. Linked from the KLEA 320P (606100) product page.

View this map on GitHub (YAML)

Read it by name

Read the KLEA 320P with an AI assistant

The Proxus Industrial MCP Server includes this map. Set it on the device, and Claude, Cursor or VS Code reads registers by key with the right type, byte order, scale and unit. It only reads.

This device speaks Modbus RTU: reach it through a Modbus TCP gateway and use the gateway’s address with the device’s unit ID.

Get the MCP server

proxus-mcp.json

{
  "devices": {
    "klea-1": {
      "protocol": "modbus-tcp",
      "host": "192.168.10.40",
      "unit_id": 1,
      "map": "klemsan/klea-320p"
    }
  }
}

Ask your assistant

Read voltage_avg_ln, voltage_l1_l2, voltage_l2_l3 from klea-1.

The tool call it makes

read_named(device: "klea-1", keys: ["voltage_avg_ln", "voltage_l1_l2", "voltage_l2_l3"])

Have this device? Verify the map.

Ask your assistant to run verify_device_map. It reads every register once, read-only, checks that the values are plausible and asks you to compare two values with the display. You get a report and a prefilled GitHub issue to submit; your name goes on this map’s verified list.

How verification works

Collecting from many devices?

Proxus reads Modbus TCP and RTU devices next to the machines, keeps the history and delivers the values to dashboards, databases and AI.

Modbus in Proxus Industrial connectivity

Data: Modbus Register Maps by Proxus contributors, CC BY 4.0.