OCPP 1.6 path
A practical starting point for many deployed chargers and smart charging profiles.
OCPP
A shared language for chargers and charging software.
OCPP helps compatible EVSEs communicate with charging management systems. For GlintEV, it is one path to charger-first control and measured operational visibility.
Why OCPP matters
Open charger communication reduces lock-in and gives software a standard control path.
Without a common protocol, every charger can become its own custom integration. OCPP gives compatible chargers a standard way to report status, receive commands, and participate in smart charging.
EVSE / OCPP control
OCPP command loop
Standardized charger path
PolicyGlintEV calculates allowed current.
GatewayTranslates request into OCPP message.
EVSEApplies smart charging profile.
HistoryStatus and command result return to GlintEV.
GlintEV uses OCPP forCharger identity, connector state, smart charging profiles, and operational history.
Future versions
The model leaves room for newer protocol versions as sites and chargers require them.
Local gateways
Some deployments can keep charger communication close to the site through a controller or gateway.
Cloud coordination
The dashboard still manages policy, history, account state, and device configuration.