Design Review

Video Lecture

Video, Slides

updated Fa 2020

Description

The design review is a 30-minute meeting intended to make sure that the team has a successful project. Students will present and defend their design while instructors and TAs critique it, identifying any infeasible or unsafe aspects and steering the team toward success. Instructors and TAs will ask questions throughout and may choose the order of blocks to be discussed. Specifically, here is what the course staff are looking for:
  1. Evidence that the overall design and high-level requirements solve the problem stated.
  2. Check if the overall design has suitable difficulty for course standards and completion in one semester. Scope may need to be adjusted if otherwise.
  3. Check team members' engineering preparedness to implement each module.
  4. Check that each team member is assigned an equal portion of the project effort.
Prepare for the following sequence.
  1. Promptly project the design document on projector.
  2. Introduce team members (name, major, and the project part each is in charge of).
  3. Present problem statement and proposed solution (<1 minutes) following the template in DDC (see Description 1.a)
  4. Present design overview (<5 minutes)
    1. High-level requirements: check DDC
    2. Block diagram: check DDC
    3. Physical design
  5. For the remainder of the review, you will participate in a detailed discussion of the design. Plan to cover each block, one at a time, beginning with the most critical. The course staff will ask questions and may step in to guide the discussion. Be prepared to discuss all aspects of your design with a focus on the following.
    1. Requirements & Verification: (see DDC); We'll look at all the important block requirements. Prepare to justify the components chosen and compare with important alternatives.
    2. Evidence that the design meets requirements (use the following as applicable)
      • Simulations
      • Calculations
      • Measurements
      • Schematics
      • Flowcharts
      • Mechanical drawings
      • Tolerance analysis: check DDC
      • Schedule: Suggestions:
        1. Think about what you can do in parallel, what has to be sequential;
        2. Work on hardware before software;
        3. Perform unit testing before system testing;
        4. Unit test each module on a breadboard before starting PCB design);
        5. Leave margin for unexpected delays or accidents. You are mostly responsible for those exceptions, just as if you were the owner of this senior design business;
      • Cost:hourly rate is ~$50 not $10. In addition, apply the 2.5x overhead multiplier ($125/hr is the cost of your senior design business), which includes the cost of salaries of you, your boss, CxOs, sales, janitors, etc.

Grading

The DR Grading Rubric is available to guide your DR preparation. Two sample Design Review documents are available as examples of what we expect: a Good Sample DR, a Moderate Sample DR, and a good example R&V table as it was presented in a final report. Notes are made in red type to point out what is lacking. Note that the grading rubrics and point structure may have evolved since these reports were generated, so use them only as a guide as to what we are generally expecting.

Submission and Deadlines

Your design document should be uploaded to PACE in PDF format by Midnight the Friday before design review. If you uploaded a mock DR document to PACE, please make sure that it has been removed before uploading the final DR..

Tech must-know and FAQ for design

Here is the link of "Tech must-know and FAQ for design" which is accessible after logging into g.illinois.edu.

Over semesters, ECE445 course staff have encountered repeated mistakes from students. The document above is designed to provide students with the essential knowledge needed in order to have a good design. Spending 5 min reading it might save you 15 hours later. Also, there might be some quiz questions in your DDC or Design Review. Please help us improve this document. We value your feedback!

Decentralized Systems for Ground & Arial Vehicles (DSGAV)

Mingda Ma, Alvin Sun, Jialiang Zhang

Featured Project

# Team Members

* Yixiao Sun (yixiaos3)

* Mingda Ma (mingdam2)

* Jialiang Zhang (jz23)

# Problem Statement

Autonomous delivery over drone networks has become one of the new trends which can save a tremendous amount of labor. However, it is very difficult to scale things up due to the inefficiency of multi-rotors collaboration especially when they are carrying payload. In order to actually have it deployed in big cities, we could take advantage of the large ground vehicle network which already exists with rideshare companies like Uber and Lyft. The roof of an automobile has plenty of spaces to hold regular size packages with magnets, and the drone network can then optimize for flight time and efficiency while factoring in ground vehicle plans. While dramatically increasing delivery coverage and efficiency, such strategy raises a challenging problem of drone docking onto moving ground vehicles.

# Solution

We aim at tackling a particular component of this project given the scope and time limitation. We will implement a decentralized multi-agent control system that involves synchronizing a ground vehicle and a drone when in close proximity. Assumptions such as knowledge of vehicle states will be made, as this project is aiming towards a proof of concepts of a core challenge to this project. However, as we progress, we aim at lifting as many of those assumptions as possible. The infrastructure of the lab, drone and ground vehicle will be provided by our kind sponsor Professor Naira Hovakimyan. When the drone approaches the target and starts to have visuals on the ground vehicle, it will automatically send a docking request through an RF module. The RF receiver on the vehicle will then automatically turn on its assistant devices such as specific LED light patterns which aids motion synchronization between ground and areo vehicles. The ground vehicle will also periodically send out locally planned paths to the drone for it to predict the ground vehicle’s trajectory a couple of seconds into the future. This prediction can help the drone to stay within close proximity to the ground vehicle by optimizing with a reference trajectory.

### The hardware components include:

Provided by Research Platforms

* A drone

* A ground vehicle

* A camera

Developed by our team

* An LED based docking indicator

* RF communication modules (xbee)

* Onboard compute and communication microprocessor (STM32F4)

* Standalone power source for RF module and processor

# Required Circuit Design

We will integrate the power source, RF communication module and the LED tracking assistant together with our microcontroller within our PCB. The circuit will also automatically trigger the tracking assistant to facilitate its further operations. This special circuit is designed particularly to demonstrate the ability for the drone to precisely track and dock onto the ground vehicle.

# Criterion for Success -- Stages

1. When the ground vehicle is moving slowly in a straight line, the drone can autonomously take off from an arbitrary location and end up following it within close proximity.

2. Drones remains in close proximity when the ground vehicle is slowly turning (or navigating arbitrarily in slow speed)

3. Drone can dock autonomously onto the ground vehicle that is moving slowly in straight line

4. Drone can dock autonomously onto the ground vehicle that is slowly turning

5. Increase the speed of the ground vehicle and successfully perform tracking and / or docking

6. Drone can pick up packages while flying synchronously to the ground vehicle

We consider project completion on stage 3. The stages after that are considered advanced features depending on actual progress.

Project Videos