RFID Smart Toll Collection System using Arduino

Toll plazas are choke points. Every vehicle that stops to pay adds seconds of delay, and those seconds compound across thousands of vehicles into long queues, wasted fuel and idling emissions — at plazas built to keep traffic moving. Manual collection also leaks revenue: cash is hard to audit, change-making slows the lane, and the whole operation depends on an attendant being present and alert. Electronic tolling solves the payment, but a tag alone is not a system — the plaza must still identify the vehicle, verify it can pay, open the barrier, and log the transaction for audit. That is an identification-plus-billing-plus-actuation problem, which maps neatly onto embedded hardware: a contactless reader for identity, a prepaid wallet in firmware for billing, a servo barrier for actuation, and a cloud log so every deduction is traceable. At tabletop scale it demonstrates the complete transaction pipeline real ETC systems run.

1. A vehicle carrying an RFID tag approaches the plaza within the reader's zone.
2. The EM-18 reader captures the tag's unique ID and sends it to the microcontroller over UART.
3. The firmware looks up the tag in its registered-vehicle table and checks the prepaid balance.
4. If the tag is valid and funded, the toll is deducted, the servo lifts the barrier arm, and the OLED confirms the deduction.
5. The transaction (tag ID, vehicle number, amount, balance, timestamp) is pushed over WiFi to the dashboard log.
6. Invalid tags or low balances trigger the buzzer and a dashboard alert; the operator can use manual override.

• Contactless vehicle identification with EM-18 125 kHz RFID reader (8–12 cm read range)
• Prepaid wallet logic — toll auto-deducted from each tag's registered balance
• Servo-driven barrier arm lifts in ~1 s after successful payment (design target)
• Live web dashboard with transaction history, vehicle log and balance table
• Low-balance warnings and invalid/unknown-tag alerts with buzzer
• On-plaza 0.96" OLED display showing vehicle ID, toll and remaining balance
• Manual override button for unregistered vehicles
• Multi-lane logic support — one controller can serve two reader/barrier pairs
• Toll-rate table (car vs. truck pricing) to demonstrate fare classes

• Assembled toll-plaza prototype with booth, barrier gantry and lane markings
• Complete source code (Arduino IDE, well-commented)
• Circuit diagram and wiring schematic
• Project report PDF (synopsis, design, results, conclusion)
• PPT presentation for final review
• Viva Q&A preparation document
• RFID tags pre-registered as demo vehicles with starter balances

FAQs

1. What does this project cover technically? RFID communication, embedded control, wallet and billing logic, UART protocols and cloud transaction logging — mapping to ECE, EEE and CSE (IoT) coursework. The report and viva Q&A document each part.
2. How is this different from real FASTag? Real FASTag uses UHF RFID with long-range readers and bank-linked wallets. This prototype demonstrates the same end-to-end flow — tag identification, balance deduction, barrier control, transaction logging — at demo scale with the EM-18 module. The report prepares you to discuss the comparison.
3. What happens if a tag has insufficient balance? The barrier stays down, the red LED and buzzer activate, and the dashboard raises a low-balance alert. The manual-override button lets the demo continue — a realistic touch.
4. Can I register more vehicles? Yes — the firmware holds a registry of tag IDs with vehicle numbers and balances, and the dashboard setup guide shows how to add vehicles and top up wallets.
5. Does it work without internet? Yes — RFID reading, deduction, barrier and OLED all run locally. Only the cloud transaction log needs WiFi; a phone hotspot is fine for demos.
6. What are sensible extensions? ANPR camera integration, UHF long-range readers, SMS receipts via GSM, and toll-rate classes by vehicle type. The report lists them as future scope.

• The EM-18 read range (8–12 cm) means demo vehicles must pass close to the reader — full-size plazas use long-range UHF readers; the report documents this difference for review readiness.
• Prepaid balances are stored in the prototype's local database — a production system would need a secure central server.
• A stable 2.4 GHz WiFi connection is needed for cloud logging; barrier operation and the OLED work offline.
• Supports one lane per reader out of the box; multi-lane needs additional readers.