Project

# Title Team Members TA Documents Sponsor
26 ROBOTIC WAITER FOR RESTAURANTS
Cheng Jin
Jun Pun Wong
Kausik Venkat
Xinrui Zhu design_review
design_review
final_paper
other
other
other
other
presentation
proposal
We want to build a robot that can handle orders & deliver food in restaurants. Patrons would have a alert mechanism (button) to call the waiter (our robot). Our kitchen would have internal transmission network (between robot, kitchen and tables) that would receive this request and then the robot would be dispatched to assist the customer. Patrons would also be able to place orders using the robot (LED screen). The restaurant staff would also be notified of the various orders which they would dispatch through the robot later on.

For the navigation, we have talked to a TA and the machine shop for advice. The TA suggested for this one-semester project, we could use fixed locations for our tables and map that to the micro-controller on the robot to program it on where to go. Greg from the machine shop also helped us suggest what wheels, motors could be used to build the robot. Currently, we are looking at a 4 wheel with 2 wheels that are driving the movement and 2 that are just following (they help support the load on the robot). We also talked with Greg on how to get the distance moved by the robot. He recommended that we can calculate the distance moved using data from the encoders that are attached to the wheels of our robot.

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