Difference between revisions of "ECE434 Project - AvailabilityDisplay"

From eLinux.org
Jump to: navigation, search
Line 27: Line 27:
<span>(Inline Comment)</span>
<span>(Inline Comment)</span>
<pre style="color:black">
== Executive Summary ==
== Executive Summary ==

Revision as of 08:50, 22 October 2020

thumb‎ Embedded Linux Class by Mark A. Yoder

Team members: Luke D Clinton] [User:Hydezc|Zach A Hyde

Grading Template

I'm using the following template to grade. Each slot is 10 points. 0 = Missing, 5=OK, 10=Wow!

00 Executive Summary
00 Packaging
00 Installation Instructions 
00 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work/Conclusions
00 Hackster.io
00 Demo/Poster
00 Late
Comments: Have a good day.


(Inline Comment)

Executive Summary

Picture that summarizes the project. <Insert Picture Here Once We Learn How> Give two sentence intro to the project. Displays whether the user is in a available or unavailable to people outside their room. Give two sentences telling what works. Our knowledge of Blynk and the LED Matrix allows us to use them independently. Give two sentences telling what isn't working. We are disallowed from using certain API on the ROSE-HULMAN network because it could lead to breaches in privacy. Although we are looking to use it on a network outside of ROSE-HULMAN for a proof of concept End with a two sentence conclusion. As for now, We have mostly done research for the project. We would like to have an API to be able to view availability, whether that is teams or zoom etc., We need to figure out the physical physical side of this project so that it will display and have a robust case for protection and mounting


Considering 3D printed packaging for protection and mount-ability on walls.

Installation Instructions

Install Blynk. https://elinux.org/EBC_Exercise_35_Blynk This link explains how to setup blynk.

User Instructions

Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.


This project is very nice for ensuring that you will not be walked in on during important meetings that may be discussing sensitive information. The current plan is for this to update automatically when you join a teams meeting with some form of manual override.

Theory of Operation

We plan on using a Blynk program to be able to constantly pull for updates on your teams status. When that status changes, the software will send an update to a display to accurately display your current availability. There will be buttons that can provide a manual override to this system. This will allow for status to be set by the user.

Work Breakdown

Research teams hooks | Luke Clinton Research Microsoft Graph API | Zach Hyde Contacted EIT about access to Microsoft Graph API (Denied) | Zach Hyde Research Bluetooth Modules for Manual Override Alternative | Zach Hyde Luke Clinton

Future Work

In the future we need to: write the code that will pull from Teams/Zoom to get the User's Status Make the manual override using Blynk or Bluetooth Design/manufacture the packaging Look into adding a doorbell


Its sad that we cant use graphs :( A possible addition could be a doorbell.
thumb‎ Embedded Linux Class by Mark A. Yoder