page_banner

OCPP 1.6J Charger Requirements V1.1 June 2021

At ev.energy we want to offer everyone cheaper, greener, simpler electric vehicle
charging.
Part of the way in which we achieve this goal is by integrating chargers from
manufacturers like yourself into the ev.energy platform.
Typically a charger connects to our platform over the internet. Our platform can then
remotely control the customer’s charger, turning it on or off, depending on various
factors like the cost of energy, the amount of CO2 and demand on the grid.
At the most basic level we require:
A connection over the internet from the charger to our platform
The ability to turn the charger on and off We recommend that you use OCPP 1.6J to integrate with our platform.
If you have an alternative method of communication, please contact us.

OCPP Requirements
Below is the absolute minimum requirements for an OCPP 1.6J integration with
ev.energy:
Supports WSS with TLS1.2 and a suitable cipher suite (as allowed by the
Amazon EC2 security policy ELBSecurityPolicy-TLS-1-2-Ext-2018-06. We DO NOT accept WS connections.
Note that WSS connection requires a correct system time on the charger in
order to successfully validate our server SSL certificate.
It is advised to keep the charger system time up-to-date, perhaps via NTP.
Supports Basic Auth OR Certificates*
Supports the following profiles:
Core
Required: MeterValues message sends Power.Active.Import OR
Current.Import AND Voltage
Firmware Management
Required: if ev.energy manages firmware updates. NOT required if the
charger manufacturer manages firmware updates.
Smart Charging
Required: accepts SetChargingProfile message with Purpose as
TxProfile OR ChargePointMaxProfile
Remote Trigger
We remotely trigger BootNotification and StatusNotification

At the moment we support Security Profile 2 (Basic Auth) only, but will be adding support for client-side Certificates soon.

Configuration We use the ChangeConfiguration message to request:
MeterValuesSampleData : Energy.Active.Import.Register , Power.Active.Import MeterValueSampleInterval : 60

Meter Values
We record meter readings from StartTransaction , StopTransaction and the
Energy.Active.Import.Register measurand of MeterValues . We use the Power.Active.Import measurand (or a combination of Current.Import and
Voltage ) to record power for several uses:
To estimate how much time we must schedule to complete charging
To calculate the total energy (and derived costs) used per charging session
To display in the app whether the vehicle is charging or just connected

Status Notifications
We use the following StatusNotification status values:
Available : to indicate the vehicle is unplugged
Charging : to indicate (in combination with the import power) that the vehicle is
charging
Faulted : to indicate the charger is in an error state
SuspendedEV / SuspendedEVSE to indicate that the vehicle is plugged in (but not
charging)

Non-functional Requirements
The following requirements are not essential but RECOMMENDED for ease of
operation:
Ability to connect to the charger remotely (via web interface or SSH)
Robust connectivity strategy (recommended WiFi AND GSM)


Post time: Apr-22-2022