Siemens VersiCharge EV charger

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
evse_error_code	1600	I16	1
ocpp_state	1601	U16	1
pcba_temperature	1602	I16	1	°C
pause_state	1629	U16	1
max_charging_current_sum	1633	U16	1	A
charger_phase	1642	U16	1
charging_current_phase_l1	1647	U16	1	A
charging_current_phase_l2	1648	U16	1	A
charging_current_phase_l3	1649	U16	1	A
charging_current_phase_sum	1650	U16	1	A
charging_voltage_phase_l1_n	1651	U16	1	V
charging_voltage_phase_l2_n	1652	U16	1	V
charging_voltage_phase_l3_n	1653	U16	1	V
current_charging_speed_l1	1662	U16	1	W
current_charging_speed_l2	1663	U16	1	W
current_charging_speed_l3	1664	U16	1	W
current_charging_speed_phase_sum	1665	U16	0.1	W
power_factor_phase_l1	1666	U16	0.01
power_factor_phase_l2	1667	U16	0.01
power_factor_phase_l3	1668	U16	0.01
average_power_factor	1669	U16	0.01
apparent_power_phase_l1	1670	U16	1	VA
apparent_power_phase_l2	1671	U16	1	VA
apparent_power_phase_l3	1672	U16	1	VA
average_apparent_power	1673	U16	1	VA
reactive_power_phase_l1	1674	U16	1	var
reactive_power_phase_l2	1675	U16	1	var
reactive_power_phase_l3	1676	U16	1	var
average_reactive_power	1677	U16	1	var
real_energy_consumed_phase_sum	1692	U32BE	0.1	Wh

link settings as documented (unverified): RTU/TCP; default 38400 8E1; unit ID 2; FC 03,06,16; Modbus RTU default address is 2 and can be modified by writing to register 0xA000. Modbus TCP port is 502.

bench facts as documented (unverified)

response timeout	2000 ms
protocol notes	Minimum Pollrate is 1000 ms. Information reporting on registers with dynamic data may take several cycles to update.
model register	40013
serial register	40008
firmware register	40032
doc revision	A5E52200882-AB, 02/2023
firmware applicability	V2.120 or higher

generated by gemini:gemini-3.5-flash · harvested from https://cache.industry.siemens.com/dl/files/359/109814359/att_1129076/v1/109814359_versicharge_wallbox_modBus_map_en-US.pdf (Siemens); 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.