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.
Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
| point | address (0-based) | type | scale | unit |
|---|---|---|---|---|
| EV status | 100 | U16 | 1 | |
| Proximity charging current | 101 | U16 | 1 | A |
| Charging time | 102 | U32BE | 1 | s |
| DIP switch configuration | 104 | U16 | 1 | |
| Firmware version | 105 | U32BE | 1 | |
| Error codes | 107 | U16 | 1 | |
| Display meter voltage V1 | 108 | U32BE | 1 | |
| Display meter voltage V2 | 110 | U32BE | 1 | |
| Display meter voltage V3 | 112 | U32BE | 1 | |
| Display meter current I1 | 114 | U32BE | 1 | |
| Display meter current I2 | 116 | U32BE | 1 | |
| Display meter current I3 | 118 | U32BE | 1 | |
| Display meter real power | 120 | U32BE | 1 | |
| Display meter reactive power | 122 | U32BE | 1 | |
| Display meter apparent power | 124 | U32BE | 1 | |
| Display meter power factor | 126 | U32BE | 1 | |
| Display meter energy | 128 | U32BE | 1 | |
| Display meter maximum power | 130 | U32BE | 1 | |
| Energy of current charging process | 132 | U32BE | 1 | |
| Display meter mains frequency | 134 | U32BE | 1 | |
| Display meter maximum current I1 | 136 | U32BE | 1 | |
| Display meter maximum current I2 | 138 | U32BE | 1 | |
| Display meter maximum current I3 | 140 | U32BE | 1 | |
| Status of overcurrent shutdown | 142 | U16 | 1 | |
| Digital input EN (Enable) | 200 | U16 | 1 | |
| Digital input XR (External Release) | 201 | U16 | 1 | |
| Digital input LD (Lock Detection) | 202 | U16 | 1 | |
| Digital input ML (Manual Lock) | 203 | U16 | 1 | |
| Digital output CR (Charger Ready) | 204 | U16 | 1 | |
| Digital output LR (Locking Request) | 205 | U16 | 1 | |
| Digital output VR (Vehicle Ready) | 206 | U16 | 1 | |
| Digital output ER (Error) | 207 | U16 | 1 | |
| Set charging current (PWM signal) | 300 | U16 | 1 | A |
| MAC address | 301 | U16 | 1 | |
| Serial number | 304 | U16 | 1 | |
| Device name | 310 | U16 | 1 | |
| IP address | 315 | U16 | 1 | |
| Subnet mask | 319 | U16 | 1 | |
| Gateway | 323 | U16 | 1 | |
| Definition of output CR | 327 | U16 | 1 | |
| Definition of output LR | 328 | U16 | 1 | |
| Definition of output VR | 329 | U16 | 1 | |
| Definition of output ER | 330 | U16 | 1 | |
| Voltage V1 | 331 | U16 | 1 | |
| Voltage V2 | 332 | U16 | 1 | |
| Voltage V3 | 333 | U16 | 1 | |
| Current I1 | 334 | U16 | 1 | |
| Current I2 | 335 | U16 | 1 | |
| Current I3 | 336 | U16 | 1 | |
| Real power | 337 | U16 | 1 | |
| Reactive power | 338 | U16 | 1 | |
| Apparent power | 339 | U16 | 1 | |
| Power factor | 340 | U16 | 1 | |
| Energy meter total | 341 | U16 | 1 | |
| Maximum power (current charging process) | 342 | U16 | 1 | |
| Energy meter can be reset | 343 | U16 | 1 | |
| Mains frequency | 344 | U16 | 1 | |
| Maximum current I1 | 345 | U16 | 1 | |
| Maximum current I2 | 346 | U16 | 1 | |
| Maximum current I3 | 347 | U16 | 1 | |
| Reset register 1 | 348 | U16 | 1 | |
| Reset value 1 | 349 | U16 | 1 | |
| Reset register 2 | 350 | U16 | 1 | |
| Reset value 2 | 351 | U16 | 1 | |
| Voltage V1 | 352 | F32BE | 1 | |
| Voltage V2 | 354 | F32BE | 1 | |
| Voltage V3 | 356 | F32BE | 1 | |
| Current I1 | 358 | F32BE | 1 | |
| Current I2 | 360 | F32BE | 1 | |
| Current I3 | 362 | F32BE | 1 | |
| Real power | 364 | F32BE | 1 | |
| Reactive power | 366 | F32BE | 1 | |
| Apparent power | 368 | F32BE | 1 | |
| Power factor | 370 | F32BE | 1 | |
| Energy meter total | 372 | F32BE | 1 | |
| Maximum power (current charging process) | 374 | F32BE | 1 | |
| Energy meter can be reset | 376 | F32BE | 1 | |
| Mains frequency | 378 | F32BE | 1 | |
| Maximum current I1 | 380 | F32BE | 1 | |
| Maximum current I2 | 382 | F32BE | 1 | |
| Maximum current I3 | 384 | F32BE | 1 | |
| Baud rate for communication to energy meter | 386 | U32BE | 1 | |
| Modbus address of energy meter | 388 | U16 | 1 | |
| Polling cycle of energy meter | 389 | U16 | 1 | ms |
| Activation of the charging contactor | 390 | U16 | 1 | |
| Name of energy meter | 391 | U16 | 1 | |
| Enable charging process | 400 | U16 | 1 | |
| Request digital communication | 401 | U16 | 1 | |
| Charging station available | 402 | U16 | 1 | |
| Manual locking | 403 | U16 | 1 | |
| Switch DHCP on/off | 404 | U16 | 1 | |
| Output 1 | 405 | U16 | 1 | |
| Output 2 | 406 | U16 | 1 | |
| Output 3 | 407 | U16 | 1 | |
| Output 4 | 408 | U16 | 1 | |
| Activate overcurrent shutdown | 409 | U16 | 1 | |
| Byte sequence | 410 | U16 | 1 | |
| "Voltage in status A/B detected" function activated | 411 | U16 | 1 | |
| "Status D, reject vehicle" function activated | 412 | U16 | 1 | |
| Reset charging controller | 413 | U16 | 1 | |
| Voltage in status A/B detected | 414 | U16 | 1 | |
| Status D, vehicle rejected | 415 | U16 | 1 | |
| Configuration of input ML | 416 | U16 | 1 | |
| Voltage V1 | 500 | U16 | 1 | |
| Voltage V2 | 501 | U16 | 1 | |
| Voltage V3 | 502 | U16 | 1 | |
| Current I1 | 503 | U16 | 1 | |
| Current I2 | 504 | U16 | 1 | |
| Current I3 | 505 | U16 | 1 | |
| Real power | 506 | U16 | 1 | |
| Reactive power | 507 | U16 | 1 | |
| Apparent power | 508 | U16 | 1 | |
| Power factor | 509 | U16 | 1 | |
| Energy meter total | 510 | U16 | 1 | |
| Maximum power (current charging process) | 511 | U16 | 1 | |
| Energy meter can be reset | 512 | U16 | 1 | |
| Mains frequency | 513 | U16 | 1 | |
| Maximum current I1 | 514 | U16 | 1 | |
| Maximum current I2 | 515 | U16 | 1 | |
| Maximum current I3 | 516 | U16 | 1 | |
| Reset 1 | 517 | U16 | 1 | |
| Reset 2 | 518 | U16 | 1 | |
| Delay before contactor monitoring after ending the charging process | 519 | U16 | 1 | ms |
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
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.