Individual Progress Report

Description

The Individual Progress Report (IPR) is a chance to put your contributions to the team's progress in writing. The report will discuss not only the components and subsystems you have personally been responsible for, but what components you have helped work on as well. It is important to talk about the relation between your work and your teammates' work as well.

Requirements and Grading

This report should be 5-12 pages of your own work. This means that you cannot take paragraphs/text from your Design Review document, since that was a collaborative effort. The IPR Grading Rubric describes what we look for in grading this assignment. The requirements are expanded on below:

  1. General: Concise writing is encouraged, but it is important that all pertinent information is conveyed. All figures should be labeled and formatted consistently.
  2. Formatting: Please refer to the Final Report Guidelines for general writing guidelines, since the format of this report should be very similar to that of the final report. Note that each component of the Final Report may be tailored to the parts of the project the individual has been active in.
  3. Introduction: First, discuss what portion of the system you have been active in designing connects to which portion of a different subsystem, and how these interact to complete an overall objective. Then discuss what you have accomplished, what you are currently working on, and what you still have left to do.
  4. Design: Discuss the design work you have done so far. It is expected that you have done calculations and/or found relevant equations, created circuits for your parts of the project, and simulated / drawn schematics for your parts. You may have already, at a high level, discussed how your part fits into the rest of the project, but you should expand on the technical details and interface between your module(s) and the other modules of the project.
  5. Verification: Testing and verification is also very important. Make sure you describe each test that was performed and its procedure in detail, and give quantitative, meaningful results. Also describe tests that have yet to be performed. We should be convinced that if all your tests will pass, your part of the project will work.
  6. Conclusion: Discuss a plan and timeline for completing your responsibilities and your project as a whole. Also explain the ethical considerations of your project by consulting the IEEE Code of Ethics, ACM Code of Ethics, or another relevant Code of Ethics.
  7. Citations: You need citations. Cite sources for equations, Application Notes you referenced in your design, and any literature you used to help design or verify your work. If you checked something from another course's lecture slides, Google'd for things related to your project, or anything similar, then you have something you need to cite. At the very least, since you have talked about the ethical considerations of your project as it relates to a published code of ethics (e.g., IEEE or ACM), you should cite those!

Submission and Deadlines

The IPR should be submitted on canvas in PDF format by the deadline listed on the Course Calendar.

Electronic Replacement for COVID-19 Building Monitors @ UIUC

Patrick McBrayer, Zewen Rao, Yijie Zhang

Featured Project

Team Members: Patrick McBrayer, Yijie Zhang, Zewen Rao

Problem Statement:

Students who volunteer to monitor buildings at UIUC are at increased risk of contracting COVID-19 itself, and passing it on to others before they are aware of the infection. Due to this, I propose a project that would create a technological solution to this issue using physical 2-factor authentication through the “airlock” style doorways we have at ECEB and across campus.

Solution Overview:

As we do not have access to the backend of the Safer Illinois application, or the ability to use campus buildings as a workspace for our project, we will be designing a proof of concept 2FA system for UIUC building access. Our solution would be composed of two main subsystems, one that allows initial entry into the “airlock” portion of the building using a scannable QR code, and the other that detects the number of people that entered the space, to determine whether or not the user will be granted access to the interior of the building.

Solution Components:

Subsystem #1: Initial Detection of Building Access

- QR/barcode scanner capable of reading the code presented by the user, that tells the system whether that person has been granted or denied building access. (An example of this type of sensor: (https://www.amazon.com/Barcode-Reading-Scanner-Electronic-Connector/dp/B082B8SVB2/ref=sr_1_11?dchild=1&keywords=gm65+scanner&qid=1595651995&sr=8-11)

- QR code generator using C++/Python to support the QR code scanner.

- Microcontroller to receive the information from the QR code reader and decode the information, then decide whether to unlock the door, or keep it shut. (The microcontroller would also need an internal timer, as we plan on encoding a lifespan into the QR code, therefore making them unusable after 4 days).

- LED Light to indicate to the user whether or not access was granted.

- Electronic locking mechanism to open both sets of doors.

Subsystem #2: Airlock Authentication of a Single User

- 2 aligned sensors ( one tx and other is rx) on the bottom of the door that counts the number of people crossing a certain line. (possibly considering two sets of these, so the person could not jump over, or move under the sensors. Most likely having the second set around the middle of the door frame.

- Microcontroller to decode the information provided by the door sensors, and then determine the number of people who have entered the space. Based on this information we can either grant or deny access to the interior building.

- LED Light to indicate to the user if they have been granted access.

- Possibly a speaker at this stage as well, to tell the user the reason they have not been granted access, and letting them know the

incident has been reported if they attempted to let someone into the building.

Criterion of Success:

- Our system generates valid QR codes that can be read by our scanner, and the data encoded such as lifespan of the code and building access is transmitted to the microcontroller.

- Our 2FA detection of multiple entries into the space works across a wide range of users. This includes users bound to wheelchairs, and a wide range of heights and body sizes.