Request for Approval

Description

The request for approval (RFA) is the very first step in successfully completing a senior design project. Once you are assigned a project, your team must submit an RFA through PACE under the My Project page. Once submitted, your project will be placed on the Web Board as a "Project Request" post, and you can also access this same post through the My Project page we used before.

Once you have submitted your RFA, the course staff will provide feedback on your idea (which will appear at the bottom of your project's page), or suggest changes in the scope of the project and ask you to re-submit an RFA. Based on your responses, your project will be approved, or in some cases, rejected. If your project is rejected, this does not mean failure! Your team just needs to resubmit an RFA that meets the expectations of the course staff. This can be done by repeating the above steps.

Once your project is approved, your team will be assigned a project number in the Projects list. Once all the projects are approved, you will also be assigned a dedicated Professor and TA. This would be the time to double check that all the information for your project in the My Project page is correct.

Video Lecture

Video, Slides

Requirements and Grading

The RFA is worth 5 points, graded credit/no credit based on whether your RFA was submitted before the deadline. The RFA is submitted through PACE under the My Project page, and should include the following information:

Projects must be legal and ethical. They must have significant scope and complexity commensurate with the size of the team. This is, of course, a subjective assessment of the course staff. To gain some insight into this judgment, please browse projects from previous semesters. The project must involve the design of signficant systems (cannot just be integration).

Submission and Deadlines

The RFA submission deadline may be found on the Course Calendar.

Quick Tips and Helpful Hints

Posting: Some general project ideas that are fraught with pitfalls:

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.