This article contains guides for managing new RFID tags.
Follow the guide (RFID - administrator) if the charger is part of load balancing/organisation
If the charger is single (stand-alone) without load balancing/organisation, follow this one. (RFID - end users)
RFID - administrator
Log in via the Charge Amps Cloud – Admin portal
You can either do this directly via our cloud service if you have a HEX code for the RFID tag, or on site by physically reading the tag on one of the chargers. If you have registered them via the portal by entering the code, you can skip to step 4.
1) Switch on the RFID Lock for the charger.
2. read the tags individually and physically label them (e.g. Tag 1, ...2, ...3, ...4, etc.).
3. These are now visible in the Admin portal under "Latest Rejected Tags".
4. Add these and name the tags.
5. Create users under ''Users''.
6. go to the created user and add the tag under ''Add tags''.
7. Then go to the user's tab and select "Give RFID access to chargers/outlets".
If you prefer another tag or card, it needs to fulfil the conditions/certificates we support (ISO/IEC 14443 Type A 13.56MHz Mifare).
RFID - end users
Here is a guide to configuring RFID tags for the end user.
(This is only if you do NOT have load balancing).
1. Log in to your user profile on my.charge.space.
2. In the top header, click on the REMOTE CONTROL tab.
3. in the list of functions is the "RFID Lock" button; make sure it is switched on and in the "ON" position.
4. Read the included RFID tag/card by placing it against the centre shield with the Charge-Amps logo on your Halo. The logo will then flash red.
5. Then go to the "PROFILE" tab. Below that is the heading "RFID TAGS". When a tag has been read but not configured, it is displayed as Latest rejected tag (see image below):
6. Select and copy the tag. Then paste it in the "RFID Tag Id" box.
7. If desired, a comment can also be added under "Comment for tag #".
8. Then click UPDATE.
A limit of one (1) RFID tag is set by default, but can be extended if needed. If any other tag or card is preferred, it must fulfil the conditions/certificates we support (ISO/IEC 14443 Type A 13.56MHz Mifare).