KEBA KeContact P30 c/x-series EV charger (Modbus TCP)

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire; word order and scaling are only confirmed at the hardware-verified rung.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

point	address (0-based)	type	scale	unit
charging_state	1000	U32BE	1
cable_state	1004	U32BE	1
evse_error_code	1006	U32BE	1
charging_current_l1	1008	U32BE	0.001	mA
charging_current_l2	1010	U32BE	0.001	mA
charging_current_l3	1012	U32BE	0.001	mA
serial_number	1014	U32BE	1
product_type_and_features	1016	U32BE	1
firmware_version	1018	U32BE	1
active_power	1020	U32BE	0.001	mW
total_energy	1036	U32BE	1	Wh
voltage_l1	1040	U32BE	1	V
voltage_l2	1042	U32BE	1	V
voltage_l3	1044	U32BE	1	V
power_factor	1046	U32BE	0.1	0.1 %
max_charging_current	1100	U32BE	0.001	mA
max_supported_current	1110	U32BE	0.001	mA
rfid_card	1500	U32BE	1
charged_energy	1502	U32BE	1	Wh
phase_switching_source	1550	U32BE	1
phase_switching_state	1552	U32BE	1
failsafe_current_setting	1600	U32BE	0.001	mA
failsafe_timeout_setting	1602	U32BE	1	s
set_charging_current	5004	U16	0.001	mA
set_energy	5010	U16	10	10 Wh
unlock_plug	5012	U16	1
enable_disable_charging_station	5014	U16	1
set_phase_switch_toggle	5050	U16	1
trigger_phase_switch	5052	U16	1
failsafe_current	5016	U16	0.001	mA
failsafe_timeout	5018	U16	1	s
failsafe_persist	5020	U16	1

link settings as documented (unverified): TCP; unit ID 255; FC 03,06; Modbus TCP is intended for transmission via Ethernet, for which TCP port 502 is reserved. The Unit ID must be set to 255.

bench facts as documented (unverified)

terminals	Ethernet (LAN cable)
wiring notes	To enable the Modbus TCP interface the DIP switch DSW1.3 on the charging station must be set to ON.
max registers/read	2
broadcast	supported
protocol notes	It is not possible to read several registers at once. The maximum reading length is 2 words. Recommended timing interval for reading is >0.5s, and for writing is >5s.
model register	1016
serial register	1014
firmware register	1018
doc revision	V 1.04
firmware applicability	KeContact P30 c-series with firmware version 3.10.16 or higher, or KeContact P30 x-series with software version 1.11 or higher

generated by gemini:gemini-3.5-flash · harvested from https://wallboxcenter.de/wp-content/uploads/2023/08/KEBA-KeContact-P30-Modbus.pdf (KEBA); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; proved interop-verified on 2026-06-10 · recorded 2026-06-10

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
interop-verified — Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.