What you see
Every charge point you operate, its live state, and what each charging session actually delivered and earned.
- checkLive and completed charging sessions — connector, energy delivered (kWh), duration and revenue — on a dedicated Charging page.
- checkRevenue per session and per charger, priced from the metered energy against your per-kWh rate.
- checkOnline / offline state from the charger’s own OCPP heartbeat, against a window you set.
- checkFaults surfaced from StatusNotification — a charger reporting Faulted or an error code becomes an alert, not a mystery.
- checkA live map of every site, so a location with a down charger is obvious at a glance.
How revenue is priced
When a session stops, the charger reports its final energy meter. PulseGrid takes the delta from the start reading, converts it to kWh, and multiplies by your price per kWh — set once for the organisation, or overridden per charger for a site on a different tariff.
If a charger drops its connection mid-session without ever sending a stop, the session is still closed and priced from the last meter reading it sent, so an interrupted charge does not silently vanish from your revenue.
How it connects
EV chargers do not post to a REST API — they speak OCPP. So instead of writing any code, you point the charge point at PulseGrid as its central system.
PulseGrid exposes an OCPP 1.6J (JSON over WebSocket) endpoint. The charger’s BootNotification, Heartbeat, StatusNotification, Start/Stop transaction and MeterValues messages are mapped onto the same sessions, uptime and revenue you already get for every other device type.
- checkProvision an EV Charger terminal in the dashboard — it comes back with its own key.
- checkPoint the charger’s central-system URL at PulseGrid’s OCPP endpoint.
- checkAuthenticate the connection with the terminal’s ID as the username and its key as the password.
- checkSet a default price per kWh for the org, and override it per charger where needed.
- checkNothing to install — a built-in charge-point simulator lets you see the whole flow before a real charger is on site.
What it is not
PulseGrid is a read-only monitoring layer for your chargers, not a charging management system. It listens to what the charger reports; it never sends it commands — no remote start or stop, no reset, no unlock, no tariff push to the hardware.
It does not authorise drivers, run your app, or settle payments. If you operate through a CSMS or back office, PulseGrid sits alongside it and gives you one uptime-and-revenue view across chargers and every other device type you run.
Common questions
Which version of OCPP does it support?
OCPP 1.6J — JSON over WebSocket. Your charge point connects to PulseGrid as its central system and authenticates with the terminal’s ID and ingest key. OCPP 2.0.1 is not supported yet.
Can PulseGrid start, stop or reset a charger?
No. The adapter is deliberately read-only: it acknowledges the charger’s messages but never sends commands. It monitors sessions, energy, uptime and faults; remote control stays with your charging management system.
How is charging revenue calculated?
From the energy metered during the session. PulseGrid takes the meter delta between start and stop, converts to kWh, and multiplies by the price per kWh you set — org-wide by default, or per charger. A charger with no price set still records energy, at zero revenue, until you set one.
What if a charger disconnects mid-session?
The session is closed automatically after a period of silence and priced from the last meter reading the charger sent, so an interrupted charge is still counted rather than left open forever.
Do I need special hardware or a gateway?
No. If your charge point speaks OCPP 1.6J — most do — you point its central-system URL at PulseGrid. There is nothing to install, and a built-in simulator lets you exercise the full flow before a real charger is connected.