Vestel EVC04 EV charger (Modbus TCP)

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
date	290	U32BE	1	yymmdd
time	294	U32BE	1	hhmmss
chargepoint_power	400	U32BE	1	W
number_of_phases	404	U16	1
chargepoint_state	1000	U16	1
charging_state	1001	U16	1
equipment_state	1002	U16	1
cable_state	1004	U16	1
evse_fault_code	1006	U32BE	1
current_l1	1008	U16	0.001	mA
current_l2	1010	U16	0.001	mA
current_l3	1012	U16	0.001	mA
voltage_l1	1014	U16	1	V
voltage_l2	1016	U16	1	V
voltage_l3	1018	U16	1	V
active_power_total	1020	U32BE	1	W
active_power_l1	1024	U32BE	1	W
active_power_l2	1028	U32BE	1	W
active_power_l3	1032	U32BE	1	W
meter_reading	1036	U32BE	0.1	0.1 kWh
session_max_current	1100	U16	1	A
evse_min_current	1102	U16	1	A
evse_max_current	1104	U16	1	A
cable_max_current	1106	U16	1	A
session_energy	1502	U32BE	1	Wh
session_start_time	1504	U32BE	1	hhmmss
session_duration	1508	U32BE	1	s
session_end_time	1512	U32BE	1	hhmmss
failsafe_current	2000	U16	1	A
failsafe_timeout	2002	U16	1	s
charging_current	5004	U16	1	A
alive_register	6000	U16	1

link settings as documented (unverified): TCP; unit ID 255; Modbus TCP communication port number is 502. There can be only one active Modbus master connection at any time.

bench facts as documented (unverified)

response timeout	20000 ms
protocol notes	If the master does not update the value of the alive register until the failsafe timeout, the device switches to the failsafe state; TCP socket is terminated and failsafe current becomes active.
model register	210
serial register	100
firmware register	230
doc revision	V1.8

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.