Charge points will use Authorize as described in section 4.1 of OCPP 1.6
Charge points will use Boot Notifications as required by section 4.2 of OCPP 1.6. One notable exception is that Easee Virtual devices will not synchronize the internal clock with the central system.
Charge points support Change Availability as described in section 4.1 of OCPP 1.6
Availability is persistent, but chargers will change status to available for >1s before going Unavailable after a reboot.
Change configuration is supported for a very limited number of configuration keys, and initial roadmap is to support as much as possible from the OCPP Core profile.
Other keys are set to readonly, even if defined as RW in OCPP 1.6. These are meant to describe current charge point functionality.
In addition to the core profile Easee OCPP extends the available configuration keys “freecharging” and “rfidfreecharging”. See Extensions for a full description of the freecharging mode
When requested the Charge Point will respond to Clear Cache requests by sending the Clear Cache command to the charger and should behave as described in 5.4 of OCPP 1.6
When requested the Charge Point will respond to Clear Charging Profile requests as described in 5.5 of OCPP 1.6
When requested the Charge Point will respond with the current active charging profile as determined by validity and stack level.
Easee OCPP deviates from the OCPP 1.6 Smart Charging standard and calls to Get Composite Schedule will return the current active plan for the charger.
Since we do not support transaction specific profiles, and only have one connector, any valid TxDefaultMaxprofile will override ChargePointMaxProfiles.
This is due to the complexities of merging charge profiles with different purposes and the hardware only supports a single profile, so instead of merging profile purposes we only send a single profile as specified by the central system.
When requested the Charge Point will respond to Get Configuration requests as described in 5.8 of OCPP 1.6
When requested the Charge Point will respond to Get Local List Version requests by returning local list version maintained by the OCPP layer and should behave as described in 5.10 of OCPP 1.6
Charge points will send heartbeats roughly every 3 minutes. In the current version charge points will not use the requested heartbeat interval from the Boot Notification response.
In the current implementation Meter Values for will not adhere to any intervals from the configuration and will be forwarded from the charger when the value is received from the Easee Cloud. In most cases this means that a single Sampled Value is sent in each Meter Values call.
The endpoint is configurable to send MeterValues also outside of transactions to provide general information about the chargepoint.
Currently we support the following measurands:
Charge points support Remote Start as described in section 5.11 of OCPP 1.6
Charge points support Remote Stop as described in section 5.12 of OCPP 1.6
Charge points support Reset as described in section 5.14 of OCPP 1.6.
It is important to remember especially when using Reset, that the Easee OCPP devices are virtual devices, so both a soft and a hard reset will result in a reset command being sent to the physical charge point and an attempted reset of the OCPP device.
Charge points support Send Local List as described in section 5.15 of OCPP 1.6
Due to hardware constraints the local list is managed in OCPP, and synchronized with the charger
Charge point supports Set Charging Profile as described in section 5.16 of OCPP 1.6 9 with the following exceptions.
- Relative charging profiles are not supported
- TxProfile purpose types are not supported
- Only supports connector 0 and 1, but for all intents and purposes they are the same for Easee Chargers
- Charging profiles with different purpose are not merged, but any valid TxDefaultProfile will override ChargePointMaxProfile. The currently used profile will be returned by Get Composite Schedule.
- Only current (A) can be used as the ChargingRateUnit
Profiles are stored in non-volatile memory on the chargers, and frequent writes to this memory will cause wear in charger hardware. If on average profiles are updated more than 10 times a day for a longer period of time, the warranty for the charge point is voided.
Please see the OCPP extension for controlling charger current in real time in chapter [#dynamic_currents]
Charge points support Start Transaction as described in section 4.8 of OCPP 1.6.
Charge points support Start Transaction as described in section 4.9 of OCPP 1.6.
Charge points support Start Transaction as described in section 4.10 of OCPP 1.6.
Checking the Configuration from Get Configuration will give an overview of charger behaviour on transaction stop, and handling of stop messages in the current software revision.
Charge points support Trigger Message as described in section 5.17 of OCPP 1.6.
The following MessageTriggers are supported: BootNotification, Heartbeat, MeterValues and StatusNotification. Others will respond NotImplemented.
Charge points support Unlock Connector Message as described in section 5.18 of OCPP 1.6
Calling UnlockConnector will terminate any ongoing transaction, and will change the value of configuration key "UnlockConnectorOnEVSideDisconnect" to "true".
Updated 6 months ago