Peblar · EV charger
Home / Home Plus / Business (also ChargeLine Home / Business) 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 |
|---|---|---|---|---|---|---|
| 30008 | 2 | Power phase 1 Instantaneous power of phase 1. | Int32 | W | 1 | R |
| 30010 | 2 | Power phase 2 Instantaneous power of phase 2. | Int32 | W | 1 | R |
| 30012 | 2 | Power phase 3 Instantaneous power of phase 3. | Int32 | W | 1 | R |
| 30014 | 2 | Power total Instantaneous power of all phases combined. | Int32 | W | 1 | R |
| 30016 | 2 | Voltage phase 1 Instantaneous voltage on phase 1. | Int32 | V | 1 | R |
| 30018 | 2 | Voltage phase 2 Instantaneous voltage on phase 2. | Int32 | V | 1 | R |
| 30020 | 2 | Voltage phase 3 Instantaneous voltage on phase 3. | Int32 | V | 1 | R |
| 30022 | 2 | Current phase 1 Instantaneous current of phase 1. | Int32 | mA | 1 | R |
| 30024 | 2 | Current phase 2 Instantaneous current of phase 2. | Int32 | mA | 1 | R |
| 30026 | 2 | Current phase 3 Instantaneous current of phase 3. | Int32 | mA | 1 | R |
| 30050 | 12 | Product serial number Serial number as a 24-byte string. | Ascii | - | 1 | R |
| 30062 | 12 | Product number Product number as a 24-byte string. | Ascii | - | 1 | R |
| 30074 | 12 | Firmware version Firmware identifier as a 24-byte string. | Ascii | - | 1 | R |
| 30086 | 2 | WLAN signal strength | Int32 | dBm | 1 | R |
| 30088 | 2 | Cellular signal strength | Int32 | dBm | 1 | R |
| 30090 | 2 | Uptime Time since the last boot. | UInt32 | s | 1 | R |
| 30092 | 1 | Phase count Number of physically connected phases, either defined by the hardware or configured during installation. | UInt16 | - | 1 | R |
| 30093 | 1 | Independent relays 0 = L1/2/3 and N on a single relay, 1 = L1/N and L2/L3 on separate relays (L1 can then be used alone on a three-phase system). | UInt16 | - | 1 | R |
| 30100 | 1 | Active warning 1 Warning number, 0 when inactive; several warnings can be active at once. | UInt16 | - | 1 | R |
| 30101 | 1 | Active warning 2 Warning number, 0 when inactive. | UInt16 | - | 1 | R |
| 30102 | 1 | Active warning 3 Warning number, 0 when inactive. | UInt16 | - | 1 | R |
| 30103 | 1 | Active warning 4 Warning number, 0 when inactive. | UInt16 | - | 1 | R |
| 30104 | 1 | Active warning 5 Warning number, 0 when inactive. | UInt16 | - | 1 | R |
| 30105 | 1 | Active error 1 Error number, 0 when inactive; several errors can be active at once. | UInt16 | - | 1 | R |
| 30106 | 1 | Active error 2 Error number, 0 when inactive. | UInt16 | - | 1 | R |
| 30107 | 1 | Active error 3 Error number, 0 when inactive. | UInt16 | - | 1 | R |
| 30108 | 1 | Active error 4 Error number, 0 when inactive. | UInt16 | - | 1 | R |
| 30109 | 1 | Active error 5 Error number, 0 when inactive. | UInt16 | - | 1 | R |
| 30110 | 1 | CP state Control-pilot level: A = no EV connected, B = EV connected but suspended, C = EV connected and charging, D = as C with ventilation requested, E = error (short to PE or powered off), F = fault, I = invalid CP level measured, U = unknown. | UInt16 | - | 1 | R |
| 30111 | 1 | Lock state 0 = unlocked, 1 = locked. Stays 0 on fixed-cable systems. | Int16 | - | 1 | R |
| 30112 | 1 | Charge current limit source Active limiting source: 0 = unknown, 1 = fixed cable, 2 = thermal, 3 = configuration limit, 4 = dynamic load balancing, 5 = group load balancing, 6 = user cable, 7 = overcurrent protection, 8 = hardware limit, 9 = power factor, 10 = OCPP smart charging, 11 = phase imbalance monitoring, 12 = local scheduled charging, 13 = solar charging, 14 = current slider, 15 = local REST API, 16 = local Modbus API, 17 = power limit input, 18 = household power limit, 19 = reserved, 20 = internal power limiter. | UInt16 | - | 1 | R |
| 30113 | 2 | Charge current limit actual Current actually communicated to the vehicle: the lowest of all limiting sources. | UInt32 | mA | 1 | R |
| 30122 | 1 | Hardware identifier Reserved for future use, reads 0. | UInt16 | - | 1 | R |
| 30123 | 1 | Modbus API version major Major API version, increased on breaking changes. This map follows major version 1. | UInt16 | - | 1 | R |
| 30124 | 1 | Modbus API version minor Minor API version, increased when a register is added. This document describes minor version 0. | UInt16 | - | 1 | R |
Read this device live with Modbus Connect, free for Windows, macOS and Linux
Related guides
Notes
Source: Peblar (Prodrive Technologies), "Developer Information - Modbus API", published on the vendor's own developer site at the supplier_url. That page is Peblar's developer information application: it renders client-side and the Modbus API reference, including the register tables used here, is part of the page's bundled content - the former deep link /modbus-api now answers 404 while the site root still serves the same document. The page fixes the transport: the Modbus TCP server uses port 502, word and byte order are big endian, the server is supported from firmware 1.6 onwards and has to be enabled in the charger's advanced web settings, either ReadOnly or ReadWrite (only ReadWrite allows control of the charge current and forcing single-phase charging). The register numbers of that page (40000 for holding registers, 30000 for input registers) are used unchanged as wire addresses here and declared zero_based; evcc's peblar driver confirms that reading, it addresses the same 30000/40000 numbers directly and cites this same page as its source. The vendor page documents no slave address: the unit ID 1 above is a placeholder taken from the evcc peblar template (secondary source), not a value from any document, and the user must set the charger's own address. Left out on purpose: EnergyTotal (30000) and SessionEnergy (30004), both int64 over four registers, because this schema has no 64-bit integer type. The 24-byte strings are 12 registers each. Charging caveats quoted from the page: pausing via a current limit below 6 A should not happen more than three times per rolling ten minutes because the on-board relays are stressed, and the fallback current of 40052 overrules the charge current limit after the alive timeout of 40050 expires.