Project

# Title Team Members TA Documents Sponsor
43 Kitchen Dry Ingredient Tracker
 Anju Jain
Nynika Badam
Sanjana Kumar
 Vishal Dayalan design_document1.pdf
final_paper1.pdf
photo1.jpg
photo2.heic
photo3.heic
presentation1.pdf
proposal1.pdf
video
**Kitchen Dry Ingredient Tracker**

Team Members:
- Anju Jain (anjuyj2)
- Nynika Badam (nbadam2)
- Sanjana Kumar (spkumar4)

**Problem**

In our day to day lives, it's hard to keep track of ingredients in our kitchen and make sure we replenish it often. In order to remedy this, we propose a kitchen dry ingredient tracker.

**Solution**

Our system is designed to track and communicate with users about their ingredient necessities. Each individual ingredient tracker can be tailored to different lower weight threshold measurements.
Our system will use an app to maintain a digital grocery list. If an ingredient is running low, our system will add the ingredient to a digital grocery list. We also will have the option of adding the ingredient to the user's choice of online shopping cart. Users can remove ingredients' names from the list after purchase. ​​If a user is outside and is close to a grocery store (500 m), mobile app notification will be sent to the user's phone to notify them about necessary ingredient/s.

**Solution Components**

## Subsystem 1: LED
LED lights are placed at each ingredient and will light up when a certain percentage of total ingredients are low to indicate a more urgent grocery run.
Components: LEDs (from previous semester lab kits) or LED strip (12V-NB-CW-01M), LED Driver

## Subsystem 2: Weight Sensor
Our system will have 3 weight sensors to track 3 different ingredients. This can be extended for a system with more ingredients.
Each weight sensor will have a button to indicate if that weight sensor is active.
The weight sensor will be used to make sure the dry ingredient has not gone below the minimum weight limit.
Components: weight sensor Alpha (Taiwan) MF01A-N-221-A05, button (from previous lab kits)

## Subsystem 3: Microcontroller
Our system will be powered by plugging the microcontroller to the wall.
It will keep constant track of weight fluctuations for ingredients and send the data to the app.
It will be responsible for controlling individual ingredient’s LEDs.
Components: Microcontroller

## Subsystem 4: App
We will build an Apple based mobile app to provide connectivity between the user and the system.
User specifies which weight sensor station corresponds to what ingredient and its lower weight threshold (grams).
The app will maintain a digital grocery list.
If an ingredient is running low, our system will add the ingredient to a digital grocery list.
We also will have the option of adding the ingredient to the user's choice of online shopping cart.
Users can remove ingredients' names from the list after purchase.
​​If a user is outside and is close to a grocery store (500 m), mobile app notification will be sent to the user's phone to notify them about necessary ingredient/s.

# Criterion For Success
1. System should be able to measure changes in ingredient weights
- Add/Remove ingredient from grocery list/ online store shopping cart
2. Indicate when an ingredient needs replenishing through app
- mobile app should add ingredient name to digital shopping list
- Or add ingredient to an online store shopping cart
3. When many ingredients (2 out of 3) are low, LED lights should turn on around these ingredients
4. If the user’s phone is 500 m or less from a grocery store, mobile app should send reminder to visit the store if there are ingredients in the digital grocery list (if the user chose not to go the online shopping route)

Cloud-controlled quadcopter

Anuraag Vankayala, Amrutha Vasili

Cloud-controlled quadcopter

Featured Project

Idea:

To build a GPS-assisted, cloud-controlled quadcopter, for consumer-friendly aerial photography.

Design/Build:

We will be building a quad from the frame up. The four motors will each have electronic speed controllers,to balance and handle control inputs received from an 8-bit microcontroller(AP),required for its flight. The firmware will be tweaked slightly to allow flight modes that our project specifically requires. A companion computer such as the Erle Brain will be connected to the AP and to the cloud(EC2). We will build a codebase for the flight controller to navigate the quad. This would involve sending messages as per the MAVLink spec for sUAS between the companion computer and the AP to poll sensor data , voltage information , etc. The companion computer will also talk to the cloud via a UDP port to receive requests and process them via our code. Users make requests for media capture via a phone app that talks to the cloud via an internet connection.

Why is it worth doing:

There is currently no consumer-friendly solution that provides or lets anyone capture aerial photographs of them/their family/a nearby event via a simple tap on a phone. In fact, present day off-the-shelf alternatives offer relatively expensive solutions that require owning and carrying bulky equipment such as the quads/remotes. Our idea allows for safe and responsible use of drones as our proposed solution is autonomous, has several safety features, is context aware(terrain information , no fly zones , NOTAMs , etc.) and integrates with the federal airspace seamlessly.

End Product:

Quads that are ready for the connected world and are capable to fly autonomously, from the user standpoint, and can perform maneuvers safely with a very simplistic UI for the common user. Specifically, quads which are deployed on user's demand, without the hassle of ownership.

Similar products and comparison:

Current solutions include RTF (ready to fly) quads such as the DJI Phantom and the Kickstarter project, Lily,that are heavily user-dependent or user-centric.The Phantom requires you to carry a bulky remote with multiple antennas. Moreover,the flight radius could be reduced by interference from nearby conditions.Lily requires the user to carry a tracking device on them. You can not have Lily shoot a subject that is not you. Lily can have a maximum altitude of 15 m above you and that is below the tree line,prone to crashes.

Our solution differs in several ways.Our solution intends to be location and/or event-centric. We propose that the users need not own quads and user can capture a moment with a phone.As long as any of the users are in the service area and the weather conditions are permissible, safety and knowledge of controlling the quad are all abstracted. The only question left to the user is what should be in the picture at a given time.

Project Videos