The business card is composed of a 0.6mm thick PCB in the standard business card size (3.5"x2"), along with a NT3H1201 NFC IC, an LED, NFC antenna, and a few support components. This means that every time you scan it, the LED will light up, magically harvesting power from the device that's scanning it. Stores up to 2kb of data.
This listing includes 5 cards, with a customizable front and back.
A Python-based CLI for PN532 and PN532Killer. Supports the PN532 with USB Serial Chip in HSU Mode, the All-in-one PN532, and the PN532Killer. Supports ISO 14443A, 14443B, 15693, adn EM4100.
By using an SDR receiver it is possible to capture, demodulate and decode the NFC signal between the card and the reader. Currently, detection and decoding is implemented for:
- NFC-A (ISO14443A): 106kbps, 212kbps and 424kbps with ASK / BPSK modulation.
- NFC-B (ISO14443B): 106kbps, 212kbps and 424kbps with ASK / BPSK modulation.
- NFC-V (ISO15693): 26kbps and 53kbps, 1 of 4 code and 1 of 256 code PPM / BPSK modulation (pending FSK).
- NFC-F (ISO18092): Preliminary support to 212kbps and 424kbps with manchester modulation.
Human Interface Device emulator for NFC readers. Reads the chip, outputs the contents as if it were a keyboard. Designed to run as a service in the background (or more accurately, a user daemon - since it requires the current user desktop session to function). The ideal time to start the program is on login. To avoid conflicts, the application will only attempt to load once. You may have problems getting it to work after switching users unless the first user logs out completely.
Requires pcscd, Python v2.7.
The nfcpy module implements NFC Forum specifications for wireless short-range data exchange with NFC devices and tags. It is written in Python and aims to provide an easy-to-use yet powerful framework for applications integrating NFC. The source code is licensed under the EUPL and hosted on GitHub. Release versions are published on PyPI for pip install -U nfcpy. Documentation for latest development and active release versions can be found on Read the Docs. The GitHub issues tracker is the place for bug reports or related questions. Other questions may have been or get answered on the project's Launchpad answers page or stackoverflow.