To get access to the OCPP logs you need the Premium Licence.
OCPP = Open Charge Point Protocol
OCPP is a universal application protocol that standardises communication between charging stations for electric vehicles and a central management system.
The Pico charging station does not support the OCPP protocol.
Analysis & assistance of OCPP logs
Information about the status:
In order for eCarUp to display the correct status of the station, the system needs the following message "StatusNotification" via the OCPP:
Available = a connector/connection is available for a new user (driver).
Preparing = a car is connected but charging has not yet been activated.
Charging = a car is connected, the release was done by eCarUp and power is released.
SuspendedEVSE = if the car is connected to the station but no power is released. This can be caused, for example, by the local load management.
SuspendedEV = the station releases power, but the car does not draw power.
Unavailable = station is not available.
Faulted = station has an internal problem and cannot deliver power.
Example1 :
Example2 :
In this example with the easee station, the station sends us a SuspendedEVSE due to the VendorErrorCode 55.
Info:
For the easee hardware you will find the vendorErrorCode`s as in the example above on the following page: https://developer.easee.cloud/docs/enumerations
OCPP Authorisation
Authentication via the RFID card:
The logs can be used to identify whether the driver is authorised or not and by means of which RFID card (UID) the charging attempt takes place.
The IdTAG is supplied with the Authorize.
This TAG must be stored in the driver's account.
If Accepted, eCarUp releases the charge.
If Invalid, eCarUp does not release the load.
Possible causes are:
The UID (idTAG) was not correctly assigned to the driver.
The driver does not have authorisation at the charging station.
The driver does not have a valid credit card in his account and therefore cannot activate a charging station with costs.
You can find out more about RFID and eCarUp on the following page.
Example:
Authentication via the web portal and the app
This is where the RemoteStartTransaction or RemoteStopTransaction comes into play.
Important: The ID tag cannot be traced back here.
Example:
OCPP errorCode
StatusNotification:
ConnectorLockFailure = Connector cannot be locked or unlocked.
EVCommunicationError = Communication error with the vehicle
GroundFailure = The ground fault circuit interrupter has been activated.
HighTemperature = The temperature in the charging station is too high.
InternalError = Error in internal hardware or software component
NoError = No error
OtherError = Other type of error, please refer to manufacturer's information
OverCurrentFailure = Overcurrent protection device has tripped
OverVoltage = The voltage has risen above an acceptable level.
UnderVoltage = The voltage has dropped below an acceptable level.
PowerMeterFailure = Error reading from energy meter
WeakSignal = Station reports a weak signal (WLAN,LAN etc.)
If these errors occur and they persist, the manufacturer of the station must be consulted.
Example:
Communication excerpt from the log of an ABB fast charging station:
>>"StatusNotification", {"connectorId":0, "errorCode": "OtherError", "vendorId": "com.abb.evci/event/v1", "vendorErrorCode": "EmergencyButtonReleased"<<
The emergency stop of the station was activated here.