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

Klemsan KLEA 6 Modbus register map

Also searched as: KLEA 606R · KLEA 606RE · KLEA 616RE · KLEA-6

49 Modbus registers of the Klemsan KLEA 6, with the address on the wire, the 30001-style reference, data type, byte order, unit and scale. Transcribed from KLEA-6 Serisi Kullanma Kılavuzu (2026-10-27).

KLEA-6 series TFT energy analyzers with Modbus RTU (and Modbus TCP on RE models); floats and doubles in holding registers.

Registers Read it by name
Device type
Power analyser
Registers
49
Interfaces
Modbus RTU, Modbus TCP
Default unit ID
1
Byte order (multi-register values)
ABCD
Serial settings
38400 baud, no parity, 1 stop bit

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. Floats span two registers, energy counters (double) span four.
  • Byte order follows the Endianness setting (register 10006: BE, LE, BE SWAP, LE SWAP); the factory default BE is assumed here.
  • Modbus TCP is only on 606RE and 616RE; the manual gives port 502 as default.

Registers

Grouped as in the vendor document.

Voltage 8 registers
Name and key Reference Address Type Byte order Unit Scale
Average L-N voltagevoltage_avg_ln 40001 0x0000 float32 ABCD V
L1-L2 voltagevoltage_l1_l2 40017 0x0010 float32 ABCD V
L2-L3 voltagevoltage_l2_l3 40019 0x0012 float32 ABCD V
L3-L1 voltagevoltage_l3_l1 40021 0x0014 float32 ABCD V
Average L-L voltagevoltage_avg_ll 40023 0x0016 float32 ABCD V
L1 - N voltagevoltage_l1_n 40101 0x0064 float32 ABCD V
L2 - N voltagevoltage_l2_n 40103 0x0066 float32 ABCD V
L3 - N voltagevoltage_l3_n 40105 0x0068 float32 ABCD V
Current 5 registers
Name and key Reference Address Type Byte order Unit Scale
Total currentcurrent_total 40003 0x0002 float32 ABCD A
Neutral currentcurrent_neutral 40015 0x000E float32 ABCD A
Phase 1 currentcurrent_l1 40107 0x006A float32 ABCD A
Phase 2 currentcurrent_l2 40109 0x006C float32 ABCD A
Phase 3 currentcurrent_l3 40111 0x006E 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 40113 0x0070 float32 ABCD W
Phase 2 active poweractive_power_l2 40115 0x0072 float32 ABCD W
Phase 3 active poweractive_power_l3 40117 0x0074 float32 ABCD W
Phase 1 reactive powerreactive_power_l1 40119 0x0076 float32 ABCD var
Phase 2 reactive powerreactive_power_l2 40121 0x0078 float32 ABCD var
Phase 3 reactive powerreactive_power_l3 40123 0x007A float32 ABCD var
Phase 1 apparent powerapparent_power_l1 40125 0x007C float32 ABCD VA
Phase 2 apparent powerapparent_power_l2 40127 0x007E float32 ABCD VA
Phase 3 apparent powerapparent_power_l3 40129 0x0080 float32 ABCD VA
Frequency 1 registers
Name and key Reference Address Type Byte order Unit Scale
Frequencyfrequency 40013 0x000C float32 ABCD Hz
Energy 10 registers
Name and key Reference Address Type Byte order Unit Scale
Total imported active energyimport_active_energy 41001 0x03E8 float64 ABCD Wh
Phase 1 imported active energyimport_active_energy_l1 41005 0x03EC float64 ABCD Wh
Phase 2 imported active energyimport_active_energy_l2 41009 0x03F0 float64 ABCD Wh
Phase 3 imported active energyimport_active_energy_l3 41013 0x03F4 float64 ABCD Wh
Total exported active energyexport_active_energy 41017 0x03F8 float64 ABCD Wh
Phase 1 exported active energyexport_active_energy_l1 41021 0x03FC float64 ABCD Wh
Phase 2 exported active energyexport_active_energy_l2 41025 0x0400 float64 ABCD Wh
Phase 3 exported active energyexport_active_energy_l3 41029 0x0404 float64 ABCD Wh
Total imported reactive energyimport_reactive_energy 41033 0x0408 float64 ABCD varh
Total exported reactive energyexport_reactive_energy 41049 0x0418 float64 ABCD varh
Power factor 7 registers
Name and key Reference Address Type Byte order Unit Scale
System power factorpower_factor_total 40011 0x000A float32 ABCD
Phase 1 power factorpower_factor_l1 40131 0x0082 float32 ABCD
Phase 2 power factorpower_factor_l2 40133 0x0084 float32 ABCD
Phase 3 power factorpower_factor_l3 40135 0x0086 float32 ABCD
Phase 1 cos phicos_phi_l1 40137 0x0088 float32 ABCD
Phase 2 cos phicos_phi_l2 40139 0x008A float32 ABCD
Phase 3 cos phicos_phi_l3 40141 0x008C float32 ABCD
Quality 6 registers
Name and key Reference Address Type Byte order Unit Scale
L1-N THDVthd_voltage_l1 40501 0x01F4 float32 ABCD %
L2-N THDVthd_voltage_l2 40503 0x01F6 float32 ABCD %
L3-N THDVthd_voltage_l3 40505 0x01F8 float32 ABCD %
Phase 1 THDIthd_current_l1 40507 0x01FA float32 ABCD %
Phase 2 THDIthd_current_l2 40509 0x01FC float32 ABCD %
Phase 3 THDIthd_current_l3 40511 0x01FE float32 ABCD %

Source documents

  • KLEA-6 Serisi Kullanma Kılavuzu , Klemsan, 2026-10-27 (accessed 2026-11-09) Bölüm 4 Haberleşme tables; serial defaults from section 4.13.2. Linked from the KLEA 606R and 606RE product pages.

View this map on GitHub (YAML)

Read it by name

Read the KLEA 6 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.

Get the MCP server

proxus-mcp.json

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

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.