Alpitronic · DC charger
Hypercharger HYC50 / HYC150 / HYC200 / HYC300 / HYC400 (DC) Modbus register map
Default configuration
- Protocol
- Modbus TCP
- Port
- 502
- Unit ID
- 1
- Addressing
- 0-based
- Byte order
- Big endian
- Word order
- High word first
Register map
| Address | Count | Name | Type | Unit | Scale | Access |
|---|---|---|---|---|---|---|
| 0 | 2 | Time Unix time. | UInt32 | s | 1 | R |
| 2 | 1 | NumConnectors Number of physical connectors: 1-4. | UInt16 | - | 1 | R |
| 3 | 1 | StationState 0 = available, 8 = unavailable, 10 = faulted. | UInt16 | - | 1 | R |
| 4 | 2 | TotalPowerDrained Total power drained from the grid by all connectors. | UInt32 | W | 1 | R |
| 6 | 12 | SerialNumber Charging station serial number, null-terminated 24-character string. | Ascii | - | 1 | R |
| 18 | 1 | LoadManagementEnabled Whether an external load management controller has control over the power drained from the grid. | UInt16 | - | 1 | R |
| 30 | 16 | ChargepointId OCPP ChargepointId, null-terminated 32-character string. | Ascii | - | 1 | R |
| 46 | 1 | MajorVersion HYC software major version. | UInt16 | - | 1 | R |
| 47 | 1 | MinorVersion HYC software minor version. | UInt16 | - | 1 | R |
| 48 | 1 | PatchVersion HYC software patch version. | UInt16 | - | 1 | R |
| 49 | 2 | Current maximum VAR inductive Currently possible inductive VAR value in 1 VAR steps, e.g. 15000. | UInt32 | VAR | 1 | R |
| 51 | 2 | Current maximum VAR capacitive Currently possible capacitive VAR value in 1 VAR steps, e.g. -15000. | UInt32 | VAR | 1 | R |
| 100 | 1 | Connector 1 state 0 = available, 1 = preparing tag ID ready, 2 = preparing EV ready, 3 = charging, 4 = suspended EV, 5 = suspended EVSE, 6 = finishing, 7 = reserved, 8 = unavailable, 9 = unavailable firmware update, 10 = faulted, 11 = unavailable connector object. | UInt16 | - | 1 | R |
| 101 | 2 | Connector 1 charging voltage Raw value in centivolts. | UInt32 | V | 0.01 | R |
| 103 | 1 | Connector 1 charging current Raw value in centiamps. | UInt16 | A | 0.01 | R |
| 104 | 2 | Connector 1 charging power | UInt32 | W | 1 | R |
| 106 | 1 | Connector 1 charge time Time since the charge started. | UInt16 | s | 1 | R |
| 107 | 1 | Connector 1 charged energy Energy of the current session; raw value is kWh/100. | UInt16 | kWh | 0.01 | R |
| 108 | 1 | Connector 1 state of charge Raw value is %/100. | UInt16 | % | 0.01 | R |
| 109 | 1 | Connector 1 type 0 = charge point, 1 = CCS DC, 2 = CHAdeMO, 3 = CCS AC, 4 = GB/T. | UInt16 | - | 1 | R |
| 110 | 2 | Connector 1 maximum charging power Maximum charging power determined by the EV and the Hypercharger. | UInt32 | W | 1 | R |
| 112 | 2 | Connector 1 minimum charging power Minimum charging power determined by the EV and the Hypercharger. | UInt32 | W | 1 | R |
| 118 | 4 | Connector 1 vehicle ID 8-byte vehicle ID, e.g. 00:00:AA:BB:CC:DD:EE:FF. | Ascii | - | 1 | R |
| 122 | 10 | Connector 1 idTag idTag as a 20-character string. | Ascii | - | 1 | R |
Read this device live with Modbus Connect, free for Windows, macOS and Linux
Related guides
Notes
MIRROR-SOURCED. Source: Alpitronic "Hypercharger - Load management manual", version 2-3, chapter 3 "Modbus TCP server" (Tables 10-13) for the HYC50/150/200/300/400 Hypercharger DC chargers. The vendor's download portal (doc.hypercharger.it) sits behind a partner login, so the manual was read from the copy in the Gekko device library (https://devicelib.my-gekko.com/download_docu.php?id_pk=292&ext=pdf&fname=EN_HYC_XX_MAN_Load+management+manual+Software+version+2.3.x.pdf), which is the file the SHA-256 below belongs to. BayWa r.e.'s SolarShop copy serves the older 'hypercharger - LoadManagement' version 1-17 instead (no connector-0 VAR registers 49/51 or connector-0 SetReactivePower at holding 2, SoC %/10), so it is not the source of these rows. The manual states port 502, big-endian byte order (the lower address holds the most significant byte) and function codes 3, 4 and 16. Input registers 0-51 describe the station; per-connector input registers use the first address digit for the connector (1xx = connector 1, 2xx = connector 2, 3xx = connector 3, 4xx = connector 4) and connector 1 is transcribed here. Holding registers 0 and 100 set the active power limit, 2 and 102 the target reactive power. The manual documents no unit identifier, so unit 1 is a placeholder. Left out: connector registers X14/X16 (deprecated VAR duplicates of registers 49/51) and X32 (INT64 total charged energy, a type the app does not have). Writing holding registers requires the configuration key ModbusLoadManagementEnabled; the server itself is enabled by default. File identity: SHA-256 f81911c3effe34d22d3b89dbdc0ba5b934f77851da749f0d8e0dca3f290b8f3c (PDF, downloaded 2026-11-07). The mirror is used only because the vendor publishes this load-management manual to partners rather than on its public portal; the document itself is Alpitronic's own, titled "Hypercharger - Load management manual", version 2-3.