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

Klemsan KLEA 4 Modbus register map

Also searched as: KLEA 400R · KLEA 405R · KLEA 406R · KLEA 411R

43 Modbus registers of the Klemsan KLEA 4, with the address on the wire, the 30001-style reference, data type, byte order, unit and scale. Transcribed from ECRAS 3 & KLEA 4 User Manual (2025-03-03).

KLEA 4 series panel energy analyzers with optional RS485 Modbus RTU; measurements are 32-bit floats in holding registers.

Registers Read it by name
Device type
Power analyser
Registers
43
Interfaces
Modbus RTU
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; values span two registers.
  • Byte order follows the Data Type setting (BE, LE, BESP, LESP); the factory default BE is assumed here.
  • KLEA 405 has no RS485 port. The T2 register applies only to the two-tariff models (405R, 406R).

Registers

Grouped as in the vendor document.

Voltage 8 registers
Name and key Reference Address Type Byte order Unit Scale
Average phase-neutral voltagevoltage_avg_ln 40001 0x0000 float32 ABCD V
Phase-phase voltage V12voltage_l1_l2 40009 0x0008 float32 ABCD V
Phase-phase voltage V23voltage_l2_l3 40011 0x000A float32 ABCD V
Phase-phase voltage V31voltage_l3_l1 40013 0x000C float32 ABCD V
Average phase-phase voltagevoltage_avg_ll 40015 0x000E float32 ABCD V
Phase 1 voltagevoltage_l1_n 40019 0x0012 float32 ABCD V
Phase 2 voltagevoltage_l2_n 40021 0x0014 float32 ABCD V
Phase 3 voltagevoltage_l3_n 40023 0x0016 float32 ABCD V
Current 6 registers
Name and key Reference Address Type Byte order Unit Scale
Total currentcurrent_total 40003 0x0002 float32 ABCD A
Average currentcurrent_avg 40005 0x0004 float32 ABCD A
Neutral currentcurrent_neutral 40007 0x0006 float32 ABCD A
Phase 1 currentcurrent_l1 40025 0x0018 float32 ABCD A
Phase 2 currentcurrent_l2 40027 0x001A float32 ABCD A
Phase 3 currentcurrent_l3 40029 0x001C float32 ABCD A
Frequency 1 registers
Name and key Reference Address Type Byte order Unit Scale
Frequencyfrequency 40017 0x0010 float32 ABCD Hz
Power 12 registers
Name and key Reference Address Type Byte order Unit Scale
Phase 1 active poweractive_power_l1 40031 0x001E float32 ABCD W
Phase 2 active poweractive_power_l2 40033 0x0020 float32 ABCD W
Phase 3 active poweractive_power_l3 40035 0x0022 float32 ABCD W
Phase 1 reactive powerreactive_power_l1 40037 0x0024 float32 ABCD var
Phase 2 reactive powerreactive_power_l2 40039 0x0026 float32 ABCD var
Phase 3 reactive powerreactive_power_l3 40041 0x0028 float32 ABCD var
Phase 1 apparent powerapparent_power_l1 40043 0x002A float32 ABCD VA
Phase 2 apparent powerapparent_power_l2 40045 0x002C float32 ABCD VA
Phase 3 apparent powerapparent_power_l3 40047 0x002E float32 ABCD VA
Total active poweractive_power_total 40055 0x0036 float32 ABCD W
Total reactive powerreactive_power_total 40057 0x0038 float32 ABCD var
Total apparent powerapparent_power_total 40059 0x003A float32 ABCD VA
Energy 5 registers
Name and key Reference Address Type Byte order Unit Scale
Total T1 import active energyt1_import_active_energy 41001 0x03E8 float32 ABCD Wh
Total T1 export active energyt1_export_active_energy 41003 0x03EA float32 ABCD Wh
Total T1 import reactive energyt1_import_reactive_energy 41005 0x03EC float32 ABCD varh
Total T1 export reactive energyt1_export_reactive_energy 41007 0x03EE float32 ABCD varh
Total T2 import active energyt2_import_active_energy 41101 0x044C float32 ABCD Wh
Power factor 7 registers
Name and key Reference Address Type Byte order Unit Scale
Phase 1 power factorpower_factor_l1 40049 0x0030 float32 ABCD
Phase 2 power factorpower_factor_l2 40051 0x0032 float32 ABCD
Phase 3 power factorpower_factor_l3 40053 0x0034 float32 ABCD
System power factorpower_factor_total 40061 0x003C float32 ABCD
Phase 1 cos phicos_phi_l1 40067 0x0042 float32 ABCD
Phase 2 cos phicos_phi_l2 40069 0x0044 float32 ABCD
Phase 3 cos phicos_phi_l3 40071 0x0046 float32 ABCD
Quality 1 registers
Name and key Reference Address Type Byte order Unit Scale
Voltage unbalancevoltage_unbalance 40065 0x0040 float32 ABCD %
Counters 3 registers
Name and key Reference Address Type Byte order Unit Scale
On hour counteron_hour_counter 42001 0x07D0 uint32 ABCD h
Run hour counterrun_hour_counter 42003 0x07D2 uint32 ABCD h
Power interruption counterpower_interruption_counter 42005 0x07D4 uint32 ABCD

Source documents

  • ECRAS 3 & KLEA 4 User Manual , Klemsan, 2025-03-03 (accessed 2026-11-09) Section 4 RS485 Communication tables and section 5 factory settings. Linked from the KLEA 406R (606702) product page.

View this map on GitHub (YAML)

Read it by name

Read the KLEA 4 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-4"
    }
  }
}

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.