Project

# Title Team Members TA Documents Sponsor
32 Automatic Cocktail Dispenser
Ben Thuma
Caleb Kong
Carson Van Pelt
Prannoy Kathiresan design_document1.pdf
final_paper1.pdf
photo1.jpg
photo2.jpg
presentation1.pdf
proposal1.pdf
video
# Automatic Cocktail Dispenser

Team Members:
- Carson Van Pelt (carsonv2)
- Caleb Kong (calebk3)
- Benjamin Thuma (bthuma2)

# Problem

Describe the problem you want to solve and motivate the need.

Enjoying a nice cocktail with friends is a common activity among eligible adults. However, mixing these delicious concoctions takes a lot of time, skill, and effort that can detract from quality time spent with friends. In most cases, people may not have the knowledge and practice to produce the drinks they desire. Time and skill are two shortcomings that can be resolved with a simple device that can create drinks on its own.

# Solution

Describe your design at a high-level, how it solves the problem, and introduce the subsystems of your project.

An automatic cocktail dispenser is better than manually mixing in many ways: it’s more consistent, time-efficient, more convenient, and even safer. First off, manually mixed drinks are often hard to replicate consistently, especially when the user is inexperienced with making their own drinks. An automatic cocktail dispenser eliminates the opportunity for poorly mixed cocktails such as the quantity of alcohol used. Secondly, an automatic cocktail dispenser would be able to produce drinks at the push of a button and be ready to consume shortly after. There’s no doubt that making a drink by hand would be less time-efficient, so being able to simply push a button would make more time to socialize with friends. Lastly, the dispenser could potentially eliminate the risk of using sharp tools and reduce the risk of accidents or injuries from happening.

The automatic cocktail dispenser would consist of 5 main components:
Liquid dispenser
Microcontroller
Refrigerator
Drink Stirrer
Power Supply

# Solution Components

## Subsystem 1 - Liquid Dispenser
Each liquid ingredient will be stored in its own original bottle and have its own tube, connected to a central dispensing area above the mixer. The tubes will be replaceable, for sanitary reasons, as well as to avoid mixing unwanted alcohol residue into the current cocktail. The liquids will be passed through the tubes using an electric pump. Smaller liquids such as syrups and juices may instead be connected directly through the refrigeration unit for convenience.

## Subsystem 2 - Microcontroller
The microcontroller’s main purpose is going to be ensuring the correct amount of each ingredient is dispensed for each cocktail, as well as selecting the cocktail that is chosen by the user via button inputs. This system can also notify the user what liquors and juices are required for their desired cocktail to ensure the proper ingredients are connected to the machine. Depending on price this may be done by a small display on the unit or something like a lightweight phone application.

## Subsystem 3 - Refrigeration
This component would keep specific ingredients safely stored and preserved prior to being dispensed for a cocktail, such as fruit-based juices and certain syrups. The liquors themselves will only need to be brought out of the user's main fridge when connected to dispensers, reducing the need for a large refrigeration unit.

## Subsystem 4 - Drink Stirrer
Most simple cocktails are stirred after being produced, so the final step in the process would be mixing the drink with a stirring spoon/rod after everything has been dispensed. The stirring utensil will also be powered by an electric motor. Depending on cost and materials, this may either drop down on its own using an additional motor or simply be easily user attached, requiring small user interaction during this step.

## Subsystem 5 - Power Supply
The design will simply be powered by any wall outlet. If units, such as refrigeration require their own plugs, we may connect them to a single power strip for convenience.

# Criterion For Success

Describe high-level goals that your project needs to achieve to be effective. These goals need to be clearly testable and not subjective.

- Releases the ingredients in the correct quantities, within 10% error
- Dispenses correct ingredients for the correct cocktail recipe with no selection error
- Safely refrigerate the perishable ingredients

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