Ethical Guidelines

University of Illinois trained engineers are the best and most highly sought in the world. Our graduates are superbly trained, highly competent, and creative. This, however, is not enough. Our engineers must also be trusted to conduct themselves according to the highest ethical standards. All teams must address ethical considerations in their projects. This requirement has two parts.

First, there is a stringent Code of Ethics published by professional societies, such as IEEE and ACM. The power of these Codes of Ethics is to provide guidance to engineers in decision making and to lend the weight of the collective community of engineers to individuals taking a stand on ethical issues. Thus the Code of Ethics both limits the professional engineer and empowers the professional engineer to stand firm on fundamental ethical bedrock. All teams must read the IEEE code and ACM code and comment on any sections of the code that bear directly on the project.

Second, we expect our students to have personal standards of conduct consistent with the IEEE and ACM Codes of Ethics, but also beyond it. That is, there are areas of ethics not addressed by these Codes that the engineer may consider in taking on projects or jobs or making other professional decisions. These are personal standards and choices. In the context of the class, there are no right or wrong answers here. Our students simply need to demonstrate that they are thinking deeply about their own decisions and the consequences of those decisions. We encourage our students to consider the wider impact of their projects and address any concerns raised by potential uses of the project. Students should ask themselves, "Would I be comfortable having my name widely attached to this project? Do I want to live in a society where this product is available or widely used? Would I be proud of a career dominated by the decision making demonstrated here?" Remember that UIUC engineers have a long history of inventions that really has changed the world.

If the students feel that these Codes of Ethics does not directly bear on their project and that there are no other reasonable concerns, they should not invent issues where there are none. Students will still be expected to be familiar with the IEEE Code of Ethics and ACM Code of Ethics.

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