RFID attendance with live register

Roll call takes ten minutes of every lab hour and proxies are common. RFID cards with a live register let faculty see attendance at once and export it.

ESP32Mini or Major projectECE, CSE, Diploma
ESP32RC522HelloLCDFeatured
Parts
₹2,565
Build
10 weeks
Board
ESP32
Objectives
6

Block diagram

Inputs
  • RC522
    RC522 RFID readerReads student cards
  • ESP32
    CameraCaptures a photo when the event happens+
Controller
  • ESP32
    ESP32Checks the card and logs time
Outputs
  • 23.4°CLCD
    LCD and buzzerConfirm each scan
  • WEB
    Web registerShows and exports attendance
  • DATA
    Data loggerStores timestamped readings for analysis+

Objectives

  1. To read and identify RFID cards within one second.
  2. To record date and time of each scan (NTP time) without duplicates in one period.
  3. To show a live register on a web page and export it as CSV.
  4. To measure read range and failed reads over 200 scans.
  5. To capture and store an image automatically when an event is detected.
  6. To log timestamped data and analyse it to support the conclusions with evidence.

Parts and specifications

Total about ₹2,565 at typical online prices. Tap a part for its pinout and datasheet notes.

Design calculations

Scan rate

One read plus storage takes about 100 ms, so one reader handles about 60 students in under 2 minutes, even with queueing.

Storage

Each record (UID 4 bytes + time 4 bytes + student index 2 bytes) is 10 bytes; 60 students × 6 periods × 100 days = 360 KB, which fits in ESP32 flash with LittleFS.

Duplicate window

Ignore the same UID within one period (for example 50 minutes) so a second tap does not double count.

Pin map

SignalPin or connection
RC522 SDA(SS) / SCK / MOSI / MISOGPIO 5 / 18 / 23 / 19
RC522 RSTGPIO 22
RC522 VCC3.3 V only
LCD SDA / SCLGPIO 21 / 15 (second I²C or move RST)
BuzzerGPIO 27

Firmware outline

  1. Connect to Wi-Fi and set the clock from NTP (Asia/Kolkata, UTC+5:30).
  2. Load the student list (UID → name, roll number) from a CSV in flash.
  3. Poll the RC522; on a new card read the UID.
  4. If unknown, beep twice and show 'Not registered'.
  5. If known and not already marked this period, save UID and time, beep once, show the name.
  6. Serve /register (today's table) and /export.csv over a small web server.

Test plan

TestExpected result
Registered cardName shown and beep within 1 s
Same card twice in one periodCounted once
Unknown cardRejected with two beeps
200 scansFailed reads counted, range measured in cm
ExportCSV opens in a spreadsheet with correct times

These rows start your results table when you plan the project.

Viva practice

Say your answer out loud first, then check. The first 2 answers are free; Maker opens all 6.

1. How does a passive RFID card get power?
2. Can RFID stop proxy attendance?
3. Why must the RC522 run on 3.3 V?
4. What is SPI?
5. Why NTP and not millis()?
6. How would you secure the data?

Make it yours

One or two upgrades for a mini project, two to four for a major one.

Build these first

Datasheets and sources to cite

  • NXP MFRC522 datasheet
  • ISO/IEC 14443 Type A
  • Espressif ESP32 datasheet

About this project

How much does the rfid attendance with live register project cost?

About ₹1,255 for the parts in the base list: ESP32 DevKit V1, RC522 RFID reader with card and tag, MIFARE Classic 1K cards × 10, 16×2 LCD with I²C backpack, Active buzzer 5 V, Breadboard 830 points, Wires and box.

How long does it take?

About 6 weeks for the base project, built on an ESP32. Each upgrade adds time.

Which branches is it suitable for?

Electronics and Communication, Computer Science / IT (IoT, AI), Diploma (any electronics branch), as a mini or major project.

Which pins and design calculations does it use?

RC522 SDA(SS) / SCK / MOSI / MISO on GPIO 5 / 18 / 23 / 19; RC522 RST on GPIO 22; RC522 VCC on 3.3 V only. Worked calculations on this page: scan rate, storage, duplicate window.

How do I test it?

Registered card: Name shown and beep within 1 s. Same card twice in one period: Counted once. Unknown card: Rejected with two beeps. 200 scans: Failed reads counted, range measured in cm. Export: CSV opens in a spreadsheet with correct times.

What are the objectives?

To read and identify RFID cards within one second. To record date and time of each scan (NTP time) without duplicates in one period. To show a live register on a web page and export it as CSV. To measure read range and failed reads over 200 scans.