DTU

GRUPPE6

41030 MECHATRONICS ENGINEERING DESIGN

A chip off the block

Work on the RFID system is done! It began by fishing the MFRC522 out of the kit box, installing the library of the same name and running the example codes to work backwards from there. First point of order was to see how much info could be extracted from student ID cards and of course, credit cards. Luckily we were only able to get the unique and very much read-only UID's from these types of cards with the rest of the information nice and unavailable.

This was great news, since we are now able to use the ID's without having to worry about scooping up sensitive information, or treating it as such - Just a nice, dumb, empty and delightfully unique ID number!

Functionality requirements

We needed to have a master key for maintenance purposes, as well as the ability for a user to lock her stuff inside with a card. Now to test things out, we also wanted a couple of LED's to light up reassuringly and prohibitatively for a bit of feedback on the breadboard.

First steps

A main script for main things. We need both SPI and MFRC522 on the library account, get our pins in order and save our variables. Most importantly we wanted a user specified SecureID and a predetermined MasterID and a boolean variable to determine wether or not the presented card is novel or not.

Now the rest of the script is divided into two tabs, an LED script to give user feedback and the MFRC522 script which is the meat and potatoes of this script.

Flowchart of functionality

As seen in above flow, the logic uses a DoorOpen boolean, which is ready for use with the webApp side of things.