Difference between revisions of "RFID CheckIn"

From ESE205 Wiki
Jump to navigation Jump to search
Line 33: Line 33:
  
 
==Gantt Chart==
 
==Gantt Chart==
•Learning how to code the Raspberry Pi/Arduino
+
*Learning how to code the Raspberry Pi/Arduino
  
•Creating the console using 3D-Printing
+
*Creating the console using 3D-Printing
  
•Testing with RFID chips
+
*Testing with RFID chips
  
•Programming the software
+
*Programming the software
  
•Setting up the server
+
*Setting up the server
  
•Debugging the software
+
*Debugging the software
  
•Connecting the software to the hardware
+
*Connecting the software to the hardware
  
•Creating the  poster
+
*Creating the  poster
  
•Demonstration
+
*Demonstration
  
 
==Weekly Log==
 
==Weekly Log==

Revision as of 12:10, 6 February 2018

Team Members

Eliot Stein

Zach Steinberg

Hannah Lester

Nathan (TA)

Project Description

Our project is an organization system designed to be used to keep track of tools in a lab. It involves RFID chipping/tagging the tools and creating software that monitors the time at which someone checks in and out the tools and can display this information, if requested. This could be used in labs to ensure that tools are not damaged or misplaced, and if they are, then the log will be able to determine when and by whom the tool was misplaced and/or damaged.

Challenges

Some that challenges we may face are:

-Connecting the software to the hardware, using RFID chips, and making the check in/check out console

-Learning how to properly implement our software to meet our desired goals.

-Learning how to use RFID chips and Raspberry Pi/Arduino.

-Making sure that each group member understands the software in its entirety.

Materials and Budget

Please note all prices do not include shipping and handling fees

  • Raspberry Pi
  • 3D Printer Filament

Gantt Chart

  • Learning how to code the Raspberry Pi/Arduino
  • Creating the console using 3D-Printing
  • Testing with RFID chips
  • Programming the software
  • Setting up the server
  • Debugging the software
  • Connecting the software to the hardware
  • Creating the poster
  • Demonstration

Weekly Log

Weekly log