In this guide
Tap your card on the metro gate and the flap opens. That half-second interaction is RFID, and the RC522 module gives your final-year project the same superpower for the price of a vada pav. Attendance systems, door locks, smart vending, toll collection — anywhere a project needs to know who or what just showed up, this little blue board is the answer.
This guide covers what the RC522 really is, how 13.56 MHz RFID works, the exact specifications, SPI wiring (including the 3.3V rule that destroys modules), the mistakes that make tags unreadable, and eight project ideas — each linked to a real projectech.in listing built around this module.
What is the RC522?
The RC522 is a 13.56 MHz RFID reader module built around the MFRC522 chip. It powers up passive MIFARE cards and key fobs wirelessly, reads each tag's unique ID (UID), and can read and write the 1KB of memory on a MIFARE Classic 1K card. Your microcontroller talks to it over SPI.
What it is NOT: it is not long-range — expect 3–5 cm, a deliberate tap, not a walk-through gate. It is not a secure identity system on UID alone — UIDs can be cloned with cheap hardware, so UID-only locks suit attendance and convenience, not bank vaults. And it does not read UHF tags, NFC phone emulation reliably, or the 125 kHz cards used by some old access systems.
- Frequency: 13.56 MHz (high-frequency RFID)
- Chip: NXP MFRC522
- Interface: SPI
- Logic voltage: 3.3V ONLY — 5V damages the module
- Tags: MIFARE Classic 1K cards and fobs (UID + 1KB memory in 16 sectors)
- Read range: ~3–5 cm with the supplied cards
- Library: the MFRC522 Arduino library (by GithubCommunity) handles the protocol
How the RC522 works
The module and the card have a conversation powered entirely by the reader. Step by step:
- The reader energizes the field. The MFRC522 drives its PCB antenna at 13.56 MHz, creating a small electromagnetic field extending a few centimeters. With no tag present, nothing happens — the module just listens.
- A tag enters the field. The passive card's antenna coil harvests energy from the reader's field — no battery needed — and wakes up its tiny chip.
- The tag answers. The card modulates its answer back onto the field (load modulation), and the reader decodes it. First comes the anti-collision sequence, which lets the reader pick one tag even if several are in range.
- The UID is read. Every MIFARE Classic card carries a 4-byte (sometimes 7-byte) unique identifier. For attendance and simple access control, this UID is all your code needs.
- Authentication opens memory. The 1KB of card memory is split into 16 sectors, each guarded by two keys (Key A and Key B). Your code authenticates with the default keys (usually all 0xFF) before reading or writing a sector — real projects change these keys.
- Data is exchanged. Read a stored balance, write a timestamp, decrement a value block — the MFRC522 library exposes all of this over SPI, with the reader handling the low-level framing.
- The field drops when the tag leaves. Remove the card and the transaction ends. This tap-in, tap-out behavior is why RFID suits attendance: one deliberate action per person, no ambiguity.
Key specifications
| Parameter | Value |
|---|---|
| Reader chip | NXP MFRC522 |
| Operating frequency | 13.56 MHz |
| Interface | SPI |
| Operating voltage | 3.3V (5V will damage the module) |
| Compatible tags | MIFARE Classic 1K (S50) cards and fobs |
| Tag memory | 1KB (16 sectors × 4 blocks × 16 bytes) |
| Read range | ~3–5 cm |
| Antenna | Onboard PCB antenna |
| Typical current | ~13–26 mA idle, ~30 mA+ while reading |
| Typical cost (India) | ₹120–₹200 (module + card + fob) |
Wiring it up: RC522 + Arduino Uno
The RC522 speaks SPI. The Uno's SPI pins are fixed (D11/D12/D13), and the module's chip-select (SDA/SS) can be any digital pin — D10 is the convention.
| RC522 pin | Arduino Uno pin | Notes |
|---|---|---|
| 3.3V | 3.3V | POWER: 3.3V only |
| GND | GND | Common ground |
| RST | D9 (any digital pin) | Reset line |
| SDA (SS) | D10 | Chip select — must match the code |
| MOSI | D11 | SPI MOSI (fixed) |
| MISO | D12 | SPI MISO (fixed) |
| SCK | D13 | SPI clock (fixed) |
| IRQ | Not connected | Optional interrupt — leave unconnected |
Warning: 3.3V ONLY — 5V will damage the RC522. This is the #1 killer of these modules. Power the module from the Uno's 3.3V pin (never 5V), and do not drive its logic pins with 5V signals. The Uno's 3.3V pin supplies ~50 mA, which covers the module's draw, but if you add more 3.3V peripherals, use a separate 3.3V regulator.
Common mistakes that kill RC522 projects
1. Powering it from 5V. The module's absolute maximum is 3.6V. One touch of the 5V pin and the MFRC522 chip is dead — often silently, reading nothing ever again. Fix: triple-check the red wire lands on 3.3V before first power-up, every time you rewire.
2. SS pin mismatch between wiring and code. The library defaults to pin 10 for chip select and pin 9 for reset; if you wired SDA to D8 but left the code at the default, nothing responds. Fix: keep a one-line comment at the top of your sketch mapping every wire, and pass the right pins to the MFRC522 constructor.
3. Expecting long range. Students plan walk-through attendance gates, then discover the read zone is a 4 cm bubble. Fix: design around the tap — a marked target on the enclosure where the card must touch. For genuine distance, you need UHF RFID hardware, a different budget entirely.
4. Metal near the antenna. Mounting the module on a metal enclosure or near a metal door frame detunes the antenna and collapses the range to near zero. Fix: keep at least 1–2 cm of plastic or air between the module's antenna area and any metal.
5. Treating the UID as unforgeable. MIFARE Classic UIDs can be cloned with inexpensive tools, and the Classic's encryption was broken years ago. Fix: UID checks are fine for attendance and convenience locks; for anything where cloning costs real money, add a PIN, an OTP, or a fingerprint as a second factor.
6. Locking yourself out of card sectors. Writing wrong access bits to a sector trailer can permanently brick that sector — the card still reads its UID, but the sector is unusable forever. Fix: prototype all sector writes on a spare card, and never write sector trailers until you understand access bits.
Project ideas using the RC522
IoT Smart Door Lock with Fingerprint, RFID and OTP
A door that opens for the right fingerprint, the right RFID card, or a one-time password — three independent factors with an ESP32 logging every entry to the cloud. The RC522 handles the card factor; the multi-factor design is what makes it viva-worthy. Build it here: IoT Smart Door Lock.
RFID Attendance Logger with ESP32
Tap in, tap out: the RC522 captures each student's UID, the ESP32 timestamps it and pushes the log to a cloud dashboard — no more paper registers, no proxy attendance. The classic RFID project, done properly with real-time sync. Build it here: RFID Attendance Logger.
IoT Weighbridge Automation with RFID and Load Cells
Trucks roll onto the weighbridge, the RC522 identifies the vehicle from a windshield tag, load cells capture the weight, and the system logs the transaction automatically — RFID removing the human (and the fraud) from the loop. Build it here: IoT Weighbridge Automation.
Keypad + RFID Door Lock with Web Access Log
A door lock that accepts either an RFID card or a keypad PIN, with every access event logged to a web dashboard. Two-factor convenience plus an audit trail — the access-log half is what elevates it above a weekend build. Build it here: Keypad + RFID Door Lock.
RFID Student Attendance with Arduino and LCD
The lab-friendly version: an Arduino reads cards on the RC522, shows the student's name on an LCD instantly, and stores the attendance locally. No Wi-Fi dependency means it works in exactly the classrooms that need it most. Build it here: RFID Student Attendance System.
RFID Smart Vending Machine
Tap your card, the machine deducts credit from the card's stored balance and dispenses the item — the RC522's read/write memory doing real work, not just UID checks. Stored-value logic plus dispensing mechanics makes this a full systems project. Build it here: RFID Smart Vending Machine.
RFID-Guided Warehouse Robot
RFID tags embedded in the floor act as waypoints: the robot's downward-facing RC522 reads each tag and follows the route, stopping at the right stations. It is line-following's smarter cousin, and immune to dirty floors. Build it here: RFID-Guided Warehouse Robot.
RFID Library Book Return Bin with Self Check-In
Drop a tagged book into the return bin: the RC522 reads the book's tag, the system checks it back into the library database, and a dashboard shows returns in real time. Asset tracking with a genuinely useful deployment story. Build it here: RFID Library Book Return Bin.
Frequently asked questions
How far can the RC522 read a card? About 3–5 cm with the cards and fobs bundled in the kit — a firm tap, not a wave. Range shrinks with metal nearby and with smaller tag antennas (stickers and key fobs read closer than full-size cards). Design your enclosure around a marked tap zone.
Can it read my metro card or office access card? Sometimes. If the card is MIFARE Classic 1K, the RC522 reads its UID and (with the keys) its memory. Many modern transit and office cards use DESFire, Plus, or other types the RC522 cannot talk to. The UID read attempt is harmless — try it and see.
Is RFID attendance secure against proxy? UID-only attendance stops casual proxy (one card per student, tap in person), but UIDs can be cloned by a determined student with cheap hardware. For exam halls and high-stakes attendance, pair the card with a fingerprint or a live photo — the multi-factor door lock listing shows the pattern.
Can I use the RC522 with an ESP32? Yes, and it is arguably the better pairing: the ESP32 is natively 3.3V, so the voltage worry disappears, and you get Wi-Fi for cloud logging for free. Wire SPI to the ESP32's VSPI pins (GPIO 23/19/18) and set any GPIO as chip select.
Why does my module read nothing at all? Run the checklist in order: 3.3V power (not 5V), common ground, SS/RST pins matching the code, SPI pins on the right fixed pins, and a known-good MIFARE Classic card held flat against the antenna. Nine times out of ten, it is the SS pin or the voltage.
Can one reader handle multiple cards at once? The anti-collision protocol can select one tag among several in the field, but practical student builds process one tap at a time — which is exactly what attendance and access control want. True multi-tag inventory needs UHF hardware.
Where to go next
For a first RFID build, the Arduino attendance system is the fastest path to a working demo; for the strongest final-year story, pick the multi-factor door lock or the vending machine with stored-value logic. Open the listing, confirm the parts, and wire the module on 3.3V from the very first power-up — your future self will thank you.