The following guideline will assist you in analysing the causes of rejected RFID cards and explain the steps necessary for a detailed investigation of the behaviour of the charging station.
Before you begin, please check if the charging station was connected to be.ENERGISED at the time of the failed authorization.
Charging station was offline at time of authorization
Three situations why a charging station can reject the request of authorization:
- The station had no online-connection with the be.ENERGISED instance at the time of authorization
- The connection was too slow and caused a timeout
- The RFID card is not included in the local cache of the charging station
You can prevent this by sending a whitelist of card numbers to the charging station at regular intervals. This card data is then stored in the cache of the charging station and can therefore also contribute to authorisation if the station is not connected.
|Please note, however, that in this context there may also be authorizations that are no longer valid. If, for example, you block a card in the backend, you must ensure that the cache of the charging station is also reset.
Charging station was online at the time of authorization
If the charging station has a permanent communication connection, you will see the failed authorisation request in the charging station log data (station data sheet/logs). By clicking on Details of the message, the corresponding details of the RFID card are displayed. There you can also view the tag ID, which is helpful for further investigation:
RFID card from own card portfolio
If the RFID card is one of your own, you can search for the tag ID under Infrastructure/Identification media. It should be found and displayed in the table. If no card is found, then no card is recorded in your system, which can have the following causes:
- it is a charging card of a roaming partner.
- The Endian coding of the charging station is not set correctly, so the card is not shown in the table.
However, if a RFID card is found, check its properties in the following order:
- card marked as "active"?
- the expiry date has not yet been exceeded
- The card is not assigned to a tariff that restricts access to the charging station
Please check the above settings. If they are correct, the card should be accepted.
RFID card of a roaming provider
If the RFID card is not from your own card portfolio, but from roaming provider, please also check the menu: Roaming/Interfaceprovider/Communikation-Logs. Replace “Interfaceprovider” with the name of the roaming provider that manages the card. You will also see the authorization request in this context and can click on Details to view the roaming provider's response.
Please not that RFID cards to roaming systems must be transmitted in big-endian format. If your charging station reads cards in Little-Endian format, you may need to correct this in the basic settings of the charging station.
If the RFID card has been rejected by the roaming provider, you have no further option to take action.
Version: 2024-01-25 05:03:12 UTC