NFC device compatibility and stability issues explained
NFC Devices compatible with Token2 Burner apps
Token2 programmable tokens can be seeded and configured using one of our burner apps, currently available under Windows, iOS (iPhones only), and Android platforms. The only requirement for the burner apps to operate is having an NFC chip. While the majority of Android devices (including phones and tablets) are equipped with an NFC module, the laptops running Windows are rarely equipped with a built-in NFC module. So far we were able to test and confirm the compatibility with the Windows burner app with the following model(s):
- Dell Latitude 7480
With laptops without built-in NFC modules, external USB NFC readers should be used for the Windows version of the NFC Burner. We successfully tested the following models:
- Token2 NFC Reader/Writer device
- ACS ACR 122U (only genuine ones, beware of counterfeit products)
- Sony USB NFC Reader RC-S380/S
Python version of the NFC Burner - token2_config.pyWe also have a python script to program and configure the second generation NFC-programmable single-profile TOTP hardware tokens using nfcpy python library. It works under Linux, macOS and Windows. Python version can currently work with the StickID NFC Writer only.
A note on the NFC link stability issues with Token2 programmable tokens
A few of the customers have reported NFC connectivity issues when using some Android devices which makes the burning process a little troublesome. This behavior with the link breaking can certainly occur with NFC, it's just the nature of the technology with such a short-range wireless communication. This is especially true at relatively higher bit rates where packets can get lost or corrupted easier (i.e. during the burn process). NFC was chosen as a method to control the programmable tokens because NFC equipment is relatively cheap, easy to find, and consumes less power compared to others (BLE, Wifi etc.). But the protocol (or to be entirely correct, a set of protocols) NFC is based on, was originally meant to be used primarily in contactless payment systems (or similar), where a powered device (i.e. a payment terminal) and a powerless card (i.e. a credit card or a transport card) are communicating with each other for a very short amount of time. The concept of data exchange is obviously different with NFC programmable tokens. On top of that the NFC antenna used in our products even thinner and more miniature than, for instance, NFC tags to allow keeping the dimensions of the tokens as small as possible. Another inconvenience that plagues the burning process is that with the wide variety of Android phones comes many different locations for the NFC chip — and thereby some frustrating experiences when users don't find it. On one device it might be located at the top, another in the center, and another at the bottom.
Here is something to keep in mind when using our NFC burner apps:
1) It's important that the NFC area on the token is touching the NFC area on the writer device (NFC module or the phone/tablet's NFC chip) when programming the token. Check the manufacturer's website to find the exact location of the NFC module, as this may vary significantly. See the example below showing NFC detection areas of a few Samsung phones. A full list is available here.
2) Turn off and on the token and try again by removing and placing the device back onto the NFC area
3) Verify if the NFC link is successfully established. Android devices produce specific sounds (depending on the model etc.) during establishing NFC links, these sounds are different for successful and unsuccessful attempts.
With USB NFC modules, the established NFC links are indicated by a green LED indicator. With ACR122, for example, a successfully established link is indicated by a green led flashing once and then turning off after a couple of seconds; while with unsuccessful links the led is turning red.
Subscribe to our mailing list
Want to keep up-to-date with the latest Token2 news, projects and events? Join our mailing list!