OCPP error analysis
This section describes various errors that can be retrieved and analyzed using an OCPP log.
This section describes various errors that can be retrieved and analyzed using an OCPP log.
OCPP is a universal application protocol that standardizes communication between electric vehicle charging stations and a central management system.
eCarUp currently supports version 1.6j
⚠️ Important: The Pico charging station does not support the OCPP protocol and has its own, more limited logs.
On the left side of the portal, click “Maintenance,” then click “Actions.”
Next, tap the three dots located on the right side of the charging station in question.
A menu should then appear; tap “Logs.”
A menu should open where you can filter by both the start and end dates. It’s best to select 1 day before and 1 day after the date in question so that all information is displayed. So, if the charging test was conducted on May 5, 2025, you should select May 4, 2025 as the start date and May 6, 2025 as the end date (unless the test was performed on the current date).
The logs should then appear below. If, as shown in the example, no logs are available, it could be that the station is not sending us logs and is therefore not communicating with eCarUp. In this case, the error is usually on the charging station’s side or due to a configuration issue.
If log entries appear, note that they also display the specified date. Be aware that the time is in UTC, so if the charging station is located in Europe, the time on the logs is off by one or two hours.
Once you have set and checked everything correctly, you can click “Export CSV” to download a CSV file containing the logs.
⚠️ Important: You need an eCarUp Premium license to generate a log
Request In StartTransaction [2,“33736216”,“StartTransaction”,{“connectorId”:1,“meterStart”:9664049,“idTag”:“”,‘timestamp’:“2025-08-14T11:40:44Z”}]
If the station sends us an “idTag”:“”
You must verify whether the commissioning instructions in accordance with OCPP charging stations were followed.
If this does not resolve the issue, it must be investigated together with the charging station manufacturer. Please feel free to send us the solution so that we can update the wiki accordingly.
Authorize [2, “6b2ff788-524f-47e0-9a6d-7843ff2caccbb”, “Authorize”, {‘idTag’:“xxxxx”}]
Authorize [3, “6b2ff788-524f-47e0-9a6d-7843ff2caccbb”, {“idTagInfo”:{“status”:“Invalid”,‘expiryDate’:“2025-12-10T06:26:06.234Z”}}]
This is not strictly an error; rather, it means that someone is presenting an RFID card at the station.
If “invalid” is displayed after an “Authorize,” this means
either that we cannot associate the RFID card with any account,
or that while the RFID card is associated with an account, that account cannot be used to charge at the station because it is restricted or private.
Or that the person is attempting to top up at a paid charging station but has not added a valid credit card to their account.