Design Document Check

updated Fa 2020

Description

The Design Document Check (DDC) is intended to aid your team as it prepares its Design Document. The DDC focuses narrowly upon providing feedback on the preparation of historically problematic Design Document elements. If these elements fall short during your Design Review the following week, precious time is lost.

What are the course staff looking for? i) Evidence that the overall idea of the design is sound; ii) A check of a small subset of required components indicates that the project is on the right track.

Below is a checklist of things to have ready for the design document check. Refer to the design document page and grading rubric for a full description of each item.
  1. Introduction
    1. Start with a brief summary (30 sec) or elevator pitch following this template:

      I will build ___A___ (my core product) for ___B___ (my core customer: the person who pays my company or uses the product).

      My customer has a problem ___C___ (describe the problem your customer has)

      My product solves my customer’s problem by ___D___ (how do you solve the problem?)

    2. Be expected to explain further what the problem is, what’s your idea to solve it, and why your idea is novel.
  2. Visual Aid
  3. High-level Requirements
    1. HL requirements are derived from the problem you are trying to solve (put yourself into the customer's shoes). HL requirements should be the essential features that your customers/users really care about. These features distinguish your product from others (e.g. ones available in the market or previous 445 designs). Be abstract (no tech details, you may come up with different design due to other constraints but still solve this problem), quantifiable (no words like continuously, accurately, etc), and unambiguous. HL&RV slides(P.5) has a good example.
    2. We will look at your HL requirements and check if they are what your customers/users really care about. Be prepared to defend your requirements, so that when you get challenged, you can give a well thought out explanation.
  4. Block Diagram
    1. Block Diagram slides
    2. We will check whether this design appears to solve your problem. 
    3. We will check if formatting is clear (lines, legends, etc). Extra caution is needed as students often make mistakes here (but you shouldn't!).
  5. Requirements & Verification Tables
    1. HL&RV slides: from P. 1-17
    2. Block Module Requirements: Break down your HL requirements into block level requirements. These are the requirements in the RV table (they are not the specs of the parts you have chosen).
    3. Verification: A step-by-step approach allows another 445 student to test if the BL requirement is satisfied. This is like an instruction for your module's unit test (with some surrounding dummy modules, a.k.a, mock object(s)
    4. We will review one piece of it. Show us an important one.
  6. Plots
  7. Circuit Schematics
  8. Tolerance Analysis
    1. Identify an important part that you need to perform some quantitative analysis on. This part should have quantitative values critical to the design and require you do calculations and make trade-offs in order to achieve your best design.
    2. Common mistake: Many students do calculations for tangential parts to pad the space.
  9. Safety & Ethics
  10. Citations

During the DDC, your team will have 5-8 minutes to present an example of each of these elements. Expect to share the 30-minute DDC session with two other design teams. Come prepared to learn from their work - both the good and bad.

Your task is to prepare and upload the above elements in a single PDF document to the course website. During your DDC session, you will present directly from your submission, which will be projected for all to see.

The focus of the DDC is not on the details of your design but rather on the details of your formatting; the design of your project will be covered in-depth during the Design Review. Organize your submission in accordance with the Design Document guidance and the example Design Document.

The course staff will focus on providing feedback on the format of your sample DDC elements - the very limited available time will not afford detailed feedback on your design. Please go to office hours for further guidance.

Requirements and Grading

Upload your DDC submission to your project page on PACE (i.e. ECE 445 web board) before arriving at your DDC session.

As in your Design Document, number pages after the title page in your DDC submission.

Any material obtained from websites, books, journal articles, or other sources not originally generated by the project team must be appropriately attributed with properly cited sources in a standardized style such as IEEE, ACM, APA, or MLA.

The course staff at the DDC will assign individual grades to each student based on:

Submission and Deadlines

Sign-up for the Design Document Check on the ECE 445 course website - specifically at the Sign up for Team Presentation item on the PACE tab. Sign-up will open the Monday one week prior to the DDCs.

Upload your DDC submission (.pdf format) to the ECE 445 course website before your DDC session - specifically at the My Project item on the PACE tab.

While you will not complete peer reviews during the DDC, you are expected to actively contribute to the discussion.

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!

Phone Audio FM Transmitter

Madigan Carroll, Dan Piper, James Wozniak

Phone Audio FM Transmitter

Featured Project

# Phone Audio FM Transmitter

Team Members:

James Wozniak (jamesaw)

Madigan Carroll (mac18)

Dan Piper (depiper2)

# Problem

In cars with older stereo systems, there are no easy ways to play music from your phone as the car lacks Bluetooth or other audio connections. There exist small FM transmitters that circumvent this problem by broadcasting the phone audio on some given FM wavelength. The main issue with these is that they must be manually tuned to find an open wavelength, a process not easily or safely done while driving.

# Solution

Our solution is to build upon these preexisting devices, but add the functionality of automatically switching the transmitter’s frequency, creating a safer and more enjoyable experience. For this to work, several components are needed: a Bluetooth connection to send audio signals from the phone to the device, an FM receiver and processing unit to find the best wavelength to transmit on, and an FM transmitter to send the audio signals to be received by the car stereo.

# Solution Components

## Subsystem 1 - Bluetooth Interface

This system connects the user’s phone, or other bluetooth device to our project. It should be a standalone module that handles all the bluetooth functions, and outputs an audio signal that will be modulated and transmitted by the FM Transmitter. Note: this subsystem may be included in the microcontroller.

## Subsystem 2 - FM Transmitter

This module will transmit the audio signal output by our bluetooth module. It will modulate the signal to FM frequency chosen by the control system. Therefore, the transmitting frequency must be able to be tuned electronically.

## Subsystem 3 - FM Receiver

This module will receive an FM signal. It must be able to be adjusted electronically (not with a mechanical potentiometer) with a signal from the control system. It does not need to fully demodulate the signal, as we only need to measure the power in the signal. Note: if may choose to have a single transceiver, in which case the receiver subsystem and the transmitter subsystem will be combined into a single subsystem.

## Subsystem 4 - Control System

The control system will consist of a microcontroller and surrounding circuitry, capable of reading the power output of the FM receiver, and outputting a signal to adjust the receiving frequency, in order to scan the FM band. We will write and upload a program to determine the most suitable frequency. It will then output a signal to the FM transmitter to adjust the transmitting frequency to the band determined above. We are planning on using the ESP32-S3-WROOM-1 microcontroller given its built-in Bluetooth module and low power usage.

## Subsystem 5 - Power

Our device is designed to be used in a car, so It must be able to be powered by a standard automobile auxiliary power outlet which provides 12-13V DC and usually at least 100W. This should be more than sufficient. We plan to purchase a connector that can be plugged into this port, with leads that we can wire to our circuit.

# Criterion for Success

The device can pair with a phone via bluetooth and receive an audio signal from a phone.

The Device transmits an FM signal capable of being detected by a standard fm radio

The Device can receive FM signals and scan the FM bands.

The digital algorithm is able to compare the strength of different channels and determine the optimal channel.

The device is able to automatically switch the transmitting channel to the predetermined best channel when the user pushes a button.