eCharge Documentation

Technical documentation for integrating with eCharge Hardy Barth AC charging stations.

Interfaces

Modbus TCP — the register map served by the station at Unit ID 1: transport and session rules, enumerations, timing and failsafe behaviour, and worked integration examples. This is the interface an EMS or SCADA system uses to read telemetry and control charging. Start with the quickstart guide: it covers what the station expects before charging control behaves as expected, and the mistakes that cost integrations the most time.

REST API — the HTTP interface to the station's internal state. Rendered directly from the OpenAPI description, so every endpoint, parameter and response shown here is the one the firmware serves.

Getting help

Questions about an integration that this documentation does not answer go to eCharge support. Include the station's serial number and firmware version — both are readable over either interface.