Manufacturer
go-e Modbus register maps
Updated 17 November 2026
2 go-e models, 47 registers in all, each re-typed from go-e’s own free documentation and checked against it.
2 of 2 shown
- EV charger
go-e go-eCharger (Modbus TCP API v1)
go-eCharger wallboxes running firmware 0.40 or newer with the v1 API (Modbus TCP API v1 document version 1.0, 2020-10-01).
Also known as: go-eCharger Modbus API v1, go-e Charger - EV charger
go-e go-eCharger (Modbus TCP, API v2)
go-eCharger models covered by the go-eCharger API v2 repository (Modbus page on the main branch); the byte-order fix noted for firmware 60.4 applies.
Also known as: go-eCharger Modbus API v2, go-e Charger
go-e: default communication settings
Factory defaults as the manufacturer documents them. Change one setting at a time on site and write down what you changed. Word order applies to 32-bit values; the addressing column says how the manufacturer prints register numbers (every map on this site also gives the 0-based wire address).
| Model | Transport | Unit ID | Serial | Word order | Documented addressing | Registers |
|---|---|---|---|---|---|---|
| go-eCharger (Modbus TCP API v1) | TCP | 1 | - | 16-bit only | 0-based | 24 |
| go-eCharger (Modbus TCP, API v2) | TCP | Not stated | - | 16-bit only | Modicon | 23 |