Project Proposal

Video Lecture

Video, Slides

Description

The proposal outlines your project's motivation, design, requirements, ethics, and safety. The project proposal is an expansion on the information provided in the RFA. Use the following format (Word template):

  1. Introduction

    • Problem: In a few paragraphs introduce the problem and why it is important. Discuss briefly how it relates to societal concerns such as public health, safety and welfare as well as to global, cultural, social, environmental, and economic factors. Include any relevant references to justify the existence or importance of the problem.
    • Solution: One to two paragraphs describing the solution. Give a high-level idea of what your solution is, then delve into detail as to how it is implemented. You do not have to commit to a particular implementation at this point, but your description should be explicit and concrete.
    • Visual Aid: A pictorial representation of your project that puts your solution in context. 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.

      Sample visual aid for project which remaps GameCube buttons on the fly.

    • High-level requirements list: A list of three quantitative characteristics that this project must exhibit in order to solve the problem. Each high-level requirement must be stated in complete sentences and displayed as a bulleted list. Avoid mentioning "cost" as a high level requirement.
  2. Design
    • Block Diagram: Break your design down into blocks and assign these blocks into subsystems. Label voltages and data connections. Your microcontroller can live in multiple subsystems if you wish, as in the example below.

      Sample block diagram for electric longboard + remote

    • Subsystem Overview: A brief description of the function of each subsystem in the block diagram and explain how it connects with the other subsystems. Every subsystem in the block diagram should have its own paragraph.
    • Subsystem Requirements: For each subsystem in your block diagram, you should include a highly detailed block description. Each description must include a statement indicating how the block contributes to the overall design dictated by the high-level requirements. Any interfaces with other blocks must be defined clearly and quantitatively. Include a list of requirements where if any of these requirements were removed, the subsystem would fail to function. Good example: Power Subsystem must be able to supply at least 500mA to the rest of the system continuously at 5V +/- 0.1V.
    • Tolerance Analysis: Identify an aspect of your design that poses a risk to successful completion of the project. Demonstrate the feasibility of this component through mathematical analysis or simulation.
  3. Ethics, safety and societal impact
    As engineers you have ethical and professional responsibilities in making design decisions. Assess the ethical and safety issues relevant to your project. Consider both issues arising during the development of your project and those which could arise from the accidental or intentional misuse of your project. Specific ethical issues should be discussed in the context of the IEEE and/or ACM Code of Ethics. Cite, but do not copy the Codes. Explain how you will avoid ethical breaches. Cite and discuss relevant safety and regulatory standards as they apply to your project. Review state and federal regulations, industry standards, and campus policy. Identify potential safety concerns in your project. Discuss the impact of your engineering solution in relevant societal, economic, environmental, and global contexts.

Submission and Deadlines

The Project Proposal document should be uploaded to My Project on PACE in PDF format before the deadline listed on the Calendar.

Illini Voyager

Cameron Jones, Christopher Xu

Featured Project

# Illini Voyager

Team Members:

- Christopher Xu (cyx3)

- Cameron Jones (ccj4)

# Problem

Weather balloons are commonly used to collect meteorological data, such as temperature, pressure, humidity, and wind velocity at different layers of the atmosphere. These data are key components of today’s best predictive weather models, and we rely on the constant launch of radiosondes to meet this need. Most weather balloons cannot control their altitude and direction of travel, but if they could, we would be able to collect data from specific regions of the atmosphere, avoid commercial airspaces, increase range and duration of flights by optimizing position relative to weather forecasts, and avoid pollution from constant launches. A long endurance balloon platform also uniquely enables the performance of interesting payloads, such as the detection of high energy particles over the Antarctic, in situ measurements of high-altitude weather phenomena in remote locations, and radiation testing of electronic components. Since nearly all weather balloons flown today lack the control capability to make this possible, we are presented with an interesting engineering challenge with a significant payoff.

# Solution

We aim to solve this problem through the use of an automated venting and ballast system, which can modulate the balloon’s buoyancy to achieve a target altitude. Given accurate GPS positioning and modeling of the jetstream, we can fly at certain altitudes to navigate the winds of the upper atmosphere. The venting will be performed by an actuator fixed to the neck of the balloon, and the ballast drops will consist of small, biodegradable BBs, which pose no threat to anything below the balloon. Similar existing solutions, particularly the Stanford Valbal project, have had significant success with their long endurance launches. We are seeking to improve upon their endurance by increasing longevity from a power consumption and recharging standpoint, implementing a more capable altitude control algorithm which minimizes helium and ballast expenditures, and optimizing mechanisms to increase ballast capacity. With altitude control, the balloon has access to winds going in different directions at different layers in the atmosphere, making it possible to roughly adjust its horizontal trajectory and collect data from multiple regions in one flight.

# Solution Components

## Vent Valve and Cut-down (Mechanical)

A servo actuates a valve that allows helium to exit the balloon, decreasing the lift. The valve must allow enough flow when open to slow the initial ascent of the balloon at the cruising altitude, yet create a tight seal when closed. The same servo will also be able to detach or cut down the balloon in case we need to end the flight early. A parachute will deploy under free fall.

## Ballast Dropper (Mechanical)

A small DC motor spins a wheel to drop [biodegradable BBs](https://www.amazon.com/Force-Premium-Biodegradable-Airsoft-Ammo-20/dp/B08SHJ7LWC/). As the total weight of the system decreases, the balloon will gain altitude. This mechanism must drop BBs at a consistent weight and operate for long durations without jamming or have a method of detecting the jams and running an unjamming sequence.

## Power Subsystem (Electrical)

The entire system will be powered by a few lightweight rechargeable batteries (such as 18650). A battery protection system (such as BQ294x) will have an undervoltage and overvoltage cutoff to ensure safe voltages on the cells during charge and discharge.

## Control Subsystem (Electrical)

An STM32 microcontroller will serve as our flight computer and has the responsibility for commanding actuators, collecting data, and managing communications back to our ground console. We’ll likely use an internal watchdog timer to recover from system faults. On the same board, we’ll have GPS, pressure, temperature, and humidity sensors to determine how to actuate the vent valve or ballast.

## Communication Subsystem (Electrical)

The microcontroller will communicate via serial to the satellite modem (Iridium 9603N), sending small packets back to us on the ground with a minimum frequency of once per hour. There will also be a LED beacon visible up to 5 miles at night to meet regulations. We have read through the FAA part 101 regulations and believe our system meets all requirements to enable a safe, legal, and ethical balloon flight.

## Ground Subsystem (Software)

We will maintain a web server which will receive location reports and other data packets from our balloon while it is in flight. This piece of software will also allow us to schedule commands, respond to error conditions, and adjust the control algorithm while in flight.

# Criterion For Success

We aim to launch the balloon a week before the demo date. At the demo, we will present any data collected from the launch, as well as an identical version of the avionics board showing its functionality. A quantitative goal for the balloon is to survive 24 hours in the air, collect data for that whole period, and report it back via the satellite modem.

![Block diagram](https://i.imgur.com/0yazJTu.png)