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.
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 |
|---|---|---|---|---|
| modbus_tcp_register_layout_version | 4 | U16 | 1 | |
| charging_state | 5 | U16 | 1 | |
| current_l1 | 6 | U16 | 0.1 | A |
| current_l2 | 7 | U16 | 0.1 | A |
| current_l3 | 8 | U16 | 0.1 | A |
| temperature_pcb | 9 | I16 | 0.1 | °C |
| voltage_l1 | 10 | U16 | 1 | V |
| voltage_l2 | 11 | U16 | 1 | V |
| voltage_l3 | 12 | U16 | 1 | V |
| extern_lock_state | 13 | U16 | 1 | |
| power | 14 | U16 | 1 | W |
| energy_since_power_on | 15 | U32BE | 1 | VAh |
| energy_since_installation | 17 | U32BE | 1 | VAh |
| energy_during_charge_cycle | 19 | U32BE | 1 | VAh |
| hardware_configuration_maximal_current | 100 | U16 | 1 | A |
| hardware_configuration_minimal_current | 101 | U16 | 1 | A |
| watchdog_timeout | 257 | U16 | 0.001 | |
| remote_lock | 259 | U16 | 1 | |
| maximal_current_command | 261 | U16 | 0.1 | A |
| failsafe_current | 262 | U16 | 0.1 | A |
| charging_permission_command | 302 | U16 | 1 | |
| rfid_card_counter | 2000 | U16 | 1 | |
| rfid_uid_length | 2001 | U16 | 1 | |
| rfid_security_type | 2018 | U16 | 1 | |
| charging_permission | 2019 | U16 | 1 | |
| wallbox_ready_for_charging | 2020 | U16 | 1 | |
| int_mid_available | 3000 | U16 | 1 | |
| int_mid_current_l1 | 3001 | U16 | 0.1 | A |
| int_mid_current_l2 | 3002 | U16 | 0.1 | A |
| int_mid_current_l3 | 3003 | U16 | 0.1 | A |
| int_mid_voltage_l1 | 3004 | U16 | 1 | V |
| int_mid_voltage_l2 | 3005 | U16 | 1 | V |
| int_mid_voltage_l3 | 3006 | U16 | 1 | V |
| int_mid_power_forward | 3007 | U16 | 1 | W |
| int_mid_energy_forward_since_installation | 3008 | U32BE | 1 | Wh |
| int_mid_power_reverse | 3010 | U16 | 1 | W |
| int_mid_energy_reverse_since_installation | 3011 | U32BE | 1 | Wh |
| internal_hcb_current_l1 | 3500 | U16 | 0.1 | A |
| internal_hcb_current_l2 | 3501 | U16 | 0.1 | A |
| internal_hcb_current_l3 | 3502 | U16 | 0.1 | A |
| internal_hcb_voltage_l1 | 3503 | U16 | 1 | |
| internal_hcb_voltage_l2 | 3504 | U16 | 1 | |
| internal_hcb_voltage_l3 | 3505 | U16 | 1 | |
| internal_hcb_power | 3506 | U16 | 1 | |
| internal_hcb_energy_since_power_on | 3507 | U32BE | 1 | |
| internal_hcb_energy_since_installation | 3509 | U32BE | 1 | |
| ext_current_l1 | 4000 | U16 | 0.1 | |
| ext_current_l2 | 4001 | U16 | 0.1 | |
| ext_current_l3 | 4002 | U16 | 0.1 | |
| ext_voltage_l1 | 4003 | U16 | 1 | |
| ext_voltage_l2 | 4004 | U16 | 1 | |
| ext_voltage_l3 | 4005 | U16 | 1 | |
| ext_power_forward | 4006 | U16 | 1 | |
| ext_energy_forward_since_installation | 4007 | U32BE | 1 | |
| ext_power_reverse | 4009 | U16 | 1 | |
| ext_energy_reverse_since_installation | 4010 | U32BE | 1 | Wh |
| maximal_power_target_command | 500 | U16 | 1 | W |
| phase_switch_control | 501 | U16 | 1 | |
| charging_management_strategy | 502 | U16 | 1 | |
| duration_time_phase_switch | 503 | U16 | 1 | |
| waiting_time_phase_switch | 504 | U16 | 1 | |
| disconnect_simulation_command | 505 | U16 | 1 | |
| maximal_power_set | 5000 | U16 | 1 | |
| phase_switch_state | 5001 | U16 | 1 | |
| status_charging_management_strategy | 5002 | U16 | 1 | |
| status_disconnecting_simulation | 5003 | U16 | 1 |
⚠ Please do not use registers that are not described in this document or are not intended for use by the user. — Starkest reads only; we never write a control register.
| serial register | 1000 |
| firmware register | 1250 |
| doc revision | 20240130 |
| firmware applicability | Version 1.0.8 – Version 2.0.2 |
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
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.