Siemens VersiCharge EV charger

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

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

⚠ disputed: Modbus RTU default address can be modified by writing to register 0xA000 — disputed by later document revisions (e.g., A5E52200882-AD / A5E52200882-AL) which state the address is modified at register 41826 (0xA362)

field reports — community-sourced, unverified (checked 2026-06-11)

In firmware version V2.128 or higher, the Pause command (pause_state @ register 1629) was removed from the Modbus register map (VERCHGTL-694), causing Modbus exception 2 (illegal data address) on integrations attempting to read or write to it. [source]
confirmed: Baud rate 38400, default unit ID 2, Modbus TCP port 502, parity E, stop bits 1, response timeout 2000 ms, and minimum poll rate 1000 ms — confirmed by Siemens VersiCharge AC Series ModBus Map (A5E52200882-AB)
confirmed: Identification registers (firmware_register 40032, model_register 40013, serial_register 40008) — confirmed by Siemens VersiCharge AC Series ModBus Map
confirmed: Register map summary (evse_error_code @ 1600, ocpp_state @ 1601, pcba_temperature @ 1602, pause_state @ 1629) — confirmed by Siemens VersiCharge AC Series ModBus Map

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.
coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.