Meeting with Your TA

Description

By the Thursday of the third week, you must have a project approved, and should be ready to get working! At this time, you'll need to log into PACE and submit your schedule for the semester. Please be sure to make this as accurate as possible because once it's submitted, it can only be changed manually. Making a block of your schedule red means that you are unavailable during that time.

Once each person on your team has submitted their schedule, your TA will be able to easily check for available times to schedule a weekly meeting. Your TA should contact you, usually by the fourth week, via email, to set up a weekly meeting schedule at mutual convenience. During the first weekly meeting, your TA will assign your team a locker and a lab kit.

Weekly meetings with your TA are required and will be held throughout the entire semester until demonstrations are completed. Your TA is your project manager. The "homework" of the course consists of preparing for the weekly meetings. Your TA will evaluate your lab notebook each week, provide feedback, and recommend improvements. At each meeting you will be expected to present your progress since your last meeting, plans for the coming week, and any technical or administrative questions you need to discuss with your TA. You are expected to arrive on time and prepared to make good use of your time with your TA. Your TA may require that each team member to fill out the Progress Report Template and submit it to them prior to each weekly meeting.

Requirements and Grading

Attendance and participation in weekly meetings is required and will affect Teamwork and Lab Notebook scores. If you can't make it to a particular weekly meeting, it is your responsibility to inform your TA prior to the meeting time and set up an alternate time.

Submission and Deadlines

Your schedule must be submitted by the end of the third week of class and you will receive an email from your TA shortly after. Your first meeting with your TA should be during the fourth week of the semester.

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