1 / 27

ECE445 | Senior Design Group #4 RFID Parking Meter System

ECE445 | Senior Design Group #4 RFID Parking Meter System. Kyle Cline Wes McClain Rich Walther. Introduction. Over the course of 4 (or 5) years at the U of I, we’ve received many tickets as a result of not having change to feed the parking meter

ornice
Download Presentation

ECE445 | Senior Design Group #4 RFID Parking Meter System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ECE445 | Senior DesignGroup #4RFID Parking Meter System Kyle Cline Wes McClain Rich Walther

  2. Introduction • Over the course of 4 (or 5) years at the U of I, we’ve received many tickets as a result of not having change to feed the parking meter • Why not have a system that automates the city parking process? • More convenient • Cost effective for the consumer and the city

  3. Objectives • Create a parking system that: -Utilizes the RFID concept -Requires very little input from the consumer -Requires very little work by attendants -Minimize Cost

  4. Design • Hub Unit • Collects and stores parking meter data • Can be connected to a central database • Parking Meter Unit • Preliminary design to complement existing meters (would be mounted on same pole) • RFID Transponder • Contains a unique identifier to route parking time to a user account

  5. Original Design Components • IPASS RFID Transponder • Texas Instruments TRF6903 RF Transceiver • PIC mProcesser

  6. Block Diagram

  7. Original Design

  8. Issues • Legal (and red tape) issues with IPASS • Technical • Encrypted data • Unnecessarily high bit rate (500kbps) • Complexity of TI TRF6903 • Low cost transceiver, but requires a significant number of components to operate • Many potential error sources • Crystal discriminator, capacitances, inductances, control word accuracy

  9. Final Design Components • Homemade RF Transponder • Linx HP-3 Transmitter/Receiver Chips • PIC mProcesser

  10. Challenges • Avoid & eliminate interference between multiple parking meters, hubs, and transponders • Timing (Very difficult) • Hardware consistency • Programming glitches

  11. Design Facts • Modular • Each unit consists of: • Linx HP-3 Transmitter & Receiver • PIC mProcesser • Software programming and some I/O differentiates each unit

  12. Final Design Operation • Utilize all available channels on Linx HP-3s • 1 common channel, 7 unique channels • Each meter has its own unique channel • When the button on the meter is pushed, the meter sends its unique channel via the common channel • The new transponder receives this data and sets its RX/TX channel to match the meter

  13. Final Design Operation • Hub unit sends poll signal sequentially on each individual channel • Each transponder responds to poll signal on individual respective channel by sending serial number to the parking meter unit • When hub unit polls the meter, the unit sends status word & transponder info to the hub

  14. Testing Procedures • Transponder • Made mock TX files • Checked status flags (LEDs, LCD)

  15. Testing Procedures • Meter-Transponder • Tested reception of meter signal (LCD, Scope) • Tested frequency hopping • Tested Transponder response (frequency and data content) • Timing (Most difficult part)

  16. Testing Procedures • Hub • Hub-Transponder communication (LEDs) • Transponder-Meter reception after Hub poll sent • Hub-Meter Poll • Overall Integration (Difficult)

  17. Testing Procedures • Hardware Issues • Added 47 µF Capacitors (Noise rejection) • Checked continuity on every PCB connection • Found consistent boards/programs to find faulty parts

  18. Plots

  19. Hub Frequency Hopping Demonstration

  20. Communication Protocol • <synch><start><type><data><parity><end> • <type> defines what type of data the packet is carrying: • TransponderID <0xC1> • ParkTime <0xC4> • Status <0xC6>

  21. Successes • Meter able to detect transponder and change frequency channel consistently • Hub able to communicate with meter and transponder • Hub able to tell if car has left

  22. Future • Utilize RFID windshield sticker tags • Develop Bluetooth / WiFi interface for hubs to wirelessly connect • Directional antennas for Parking Meter to Transponder communication • Antenna switching circuit to eliminate 2nd omni-directional antenna • Web interface so people can look online and see if parking spaces are available • Increasing availability of web-enabled mobile phones

  23. Recommendations • Compare cost vs. ease of use in design stage • Use directional antennas to simplify logic • Cheaper TX/RX chip • Optimize power consumption

  24. Questions ?

More Related