Design Document

Description

The design document communicates the complete and detailed design of your project. It is substantially more detailed than the proposal and prepares you for the assembly phase of the semester. A quality design document is the key to a successful project (sample document). Use the following format:

  1. Introduction

    • Problem and Solution:

      One to two paragraphs explaining the context of the problem to be solved by your project, including any relevant references to justify the existence and/or importance of the problem (i.e., the need or want for a solution). Justify the novelty of your solution or explain the expected improvements of your solution over previous results.

    • Visual Aid

      A pictorial representation of your project that puts your solution in context. Not necessarily restricted to your design. Include other external systems relevant to your project (e.g. if your solution connects to a phone via Bluetooth, draw a dotted line between your device and the phone). Note that this is not a block diagram and should explain how the solution is used, not a breakdown of inner components.

    • High-level requirements list:

      A list of three to four objective characteristics that this project must exhibit in order to solve the problem. These should be selected such that if any of these requirements were not met, the project would fail to solve the problem. Avoid vague requirements that can be interpreted a number of ways (e.g. "The radio subsystem should work reliably."). Each high-level requirement must be stated in complete sentences and displayed as a bulleted list.

  2. Design

    • Block Diagram:

      A general block diagram of the design of your solution. Each block should be as modular as possible and represent a subsystem of your design. In other words, they can be implemented independently and re-assembled later. The block diagram should be accompanied by a brief (1 paragraph) description of the critical subsystems and what they do.

    • Physical Design (if applicable):

      A physical diagram of the project indicating things such as mechanical dimensions or placement of sensors and actuators. The physical diagram should also be accompanied by a brief one paragraph description.

    • [Subsystem X]

      For each subsystem in your block diagram, you should include a highly detailed and quantitative block description. Each description must include a statement indicating how the block contributes to the overall design dictated by the high-level requirements. Any and all design decisions must be clearly justified. Any interfaces with other blocks must be defined clearly and quantitatively.

      Include any relevant supporting figures and data in order to clearly illustrate and justify the design. Typically a well justified block design will include some or all of the following items: Circuit schematics, simulations, calculations, measurements, flow charts, mechanical diagrams (e.g. CAD drawings, only necessary for mechanical components).

      You must include a Requirements and Verifications table. Please see the R&V page for guidance on writing requirements and verification procedures.

    • [Subsystem Y]

      ...

    • [Subsystem Z]

      ...

    • Tolerance Analysis: Through discussions with your TA, identify the block or interface critical to the success of your project that poses the most challenging requirement. Analyze it mathematically and show that it can be feasibly implemented and meet its requirements. See the Tolerance Analysis guide for further guidance.
  3. Cost and Schedule

    1. Cost Analysis: Include a cost analysis of the project by following the outline below. Include a list of any non-standard parts, lab equipment, shop services, etc., which will be needed with an estimated cost for each.
      • Labor: (For each partner in the project)
        Assume a reasonable salary 
        ($/hour) x 2.5 x hours to complete = TOTAL
        Then total labor for all partners. It's a good idea to do some research into what a graduate from ECE at Illinois might typically make.
      • Parts: Include a table listing all parts (description, manufacturer, part #, quantity and cost) and quoted machine shop labor hours that will be needed to complete the project.
      • Sum of costs into a grand total
    2. Schedule:

      Include a time-table showing when each step in the expected sequence of design and construction work will be completed (general, by week), and how the tasks will be shared between the team members. (i.e. Select architecture, Design this, Design that, Buy parts, Assemble this, Assemble that, Prepare mock-up, Integrate prototype, Refine prototype, Test integrated system).

  4. Discussion of Societal Impact, Engineering Standards, Ethics, and Safety Considerations:

    1. Discuss how your project makes a positive contribution to public health, safety and welfare considering economic, environmental, social, cultural, and global factors.
    2. Identify the engineering standards (IEEE, ACM, UL, etc.) that apply to your project.
    3. Explain how IEEE/ACM codes of ethics and course ethics guidelines relate to your project. Discuss ethical concerns for your project.
    4. Discuss electrical and mechanical safety concerns referring to course safety guidelines page. Add any ethical and safety concerns that arose since your proposal.
    5. Document procedures to mitigate the safety concerns of your project. For example, include a lab safety document for batteries, human/animal interfaces, aerial devices, high-power, chemicals, etc. Justify that your design decisions sufficiently protect both users and developers from unsafe conditions caused by your project. Projects dealing with flying vehicles, high voltage, or other high-risk factors, will be required to produce a Safety Manual and demonstrate compliance with the safety manual at the time of demo.
  5. Citations:

    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.

Submission and Deadlines

Your design review document should be uploaded to PACE in PDF format by the deadline shown on the course calendar . If you have uploaded a mock DR document to PACE, please make sure that it has been removed before DR.

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.