P16462: Wind Energy Base Station
/public/

# Problem Definition

 Table of Contents
Problem Definition Documents

In a glider energy generator, a glider travels around in a circular flight path while attached to a tether that is attached to a generator to create energy. Previous design efforts focused on the idea of a vertical flight path around a horizontal axis. However, the goal of our group is to create the base station to make use of a horizontal flight path around a vertical axis. Because the focus is entirely on the base station, a plane will be purchased to act as a glider and any energy generation would be part of future efforts.

The base station must include several functions and elements, including rotation, tether, reel, and bridle systems. The rotation component must allow the plane to fly in a horizontal flight path without tearing the base station from the ground. The tether system connects the plane to the base station and allows the plane to pull on the generator. The reel system allows ground personnel to bring the plane closer for safe landing and also allows for flight path adjustment. The bridle system is installed to maintain a constant bank angle for the plane to travel in the proper horizontal path.

The goal of this project is to design a functional base with a tether and manual reel system to fly a plane in a 360 degree horizontal flight path. This serves to test the validity of this particular energy harvesting system. Realistically, flight patterns will vary trial to trial due to weather conditions and plane condition. Also, due to recent laws, it is illegal for objects to fly beyond 100 ft above the ground without clearance, which limits the available flight of the glider.

Success of this project would result in a 'proof of concept.' If the base station with the pre-purchased plane can maintain proper flight for 50 revolutions with an 80% success rate, future teams can begin looking into installing a generator and other data collection systems to the base station and determine whether such a method would be feasible in creating power.

Project Summary

Use Case

## Project Goals and Key Deliverables

The goal of this project is to create the base station for an airborne manual glider that flies a horizontal circle around the vertical axis. The base should be designed to be portable and easily assembled and allow full 360 degree rotation while reeling the plane in and out. The base also needs to have a launch device and preferably a landing device to get the plane up into the air and to ground it safely.

## Customer Requirements (Needs)

Customer Requirements

## Engineering Requirements (Metrics & Specifications)

Engineering Requirements

## Constraints

Like all projects, our team has constraints. These include:
• "No Fly Zone" Regulation: By federal law, no unmanned vehicles are allowed to be airborne more than 100ft within 5 miles of an airport. RIT recently alerted its students that absolutely no airborne aircrafts may fly on campus, regardless of flight height.
• Weather: Rochester weather is not fun weather. The winter arrives quickly after school starts and lasts for the large majority of the school year. It also is windy due to the proximity to Lake Ontario. The plane can only fly in certain conditions, including no hail and low wind speeds.
• Budget: We were given a budget by the Kate Gleason College of Engineering. The plane and other materials may cause us to go over budget due to possible plane crashes and design constraints.
• Mobility of Base: The base needs to be designed to be able to fit through doorways and be able to be carried by a single person, as requested by the customer. Therefore, the dimensions should not be large and the material and design will need to be lightweight.
• Plane Type: The customer is pre-picking a plane for the team's use, leading the team to need to design with the plane's specs in mind.
• Flight Path Pattern: The flight path has been already determined by the customer, so the team has no room to innovate in this field.

House of Quality

## Risk Management

Risk Management Table

## Plans for next phase

• As a team, where do you want to be in three weeks at your next review?
Individual Contributions
Team Member Problem Definition Phase: What did I actually do? Problem Definition Phase: What did I learn? Systems Design Phase: What will I contribute?
Sarah Collmus
• Team Values
• Team Norms Rubric
• Problem Design Review slideshow and EDGE clean up
• EDGE constraints
• Front page summary of EDGE
• Phase II Project Planning make-over
• Being a leader is hard and makes me feel like a bully sometimes
• Double checking work is important
• Team values make sure everyone is on the same page
• Technical design should not be the first step in an engineering project
• How to program on the EDGE website
• Delegate tasks
• Decide on final base design
• Research on reel systems
• Research on RC launch/land systems
Laura Arciniegas
• Wrote up the first draft of the customer needs
• Help edit the Engineering Requirements
• Worked on the House of Quality
• Typed up notes for every meeting
• Organizing notes, files, emails makes everyone more efficient
• Several people need to review a document before it is publishable
• There can never be too much research, I am continuously learning about this project
• Draft final base design
• Research on RC launch/land systems
• Go to aero club meeting
• Base design brainstorming
Kevin Collins
• Worked on Customer/Engineering Requirements and Parameters, Benchmarking
• Base Concept Designs
• Designed Scenario
• Project Planning
• Learned how to handle our team dynamic
• Project Objectives
• Worked on the project planning/problem analysis and not jumping straight into design
• Running the simulation to prepare expectations, parameters
• Run test flights
• Design Launch/Landing
• Base design brainstorming
Aleksandr Kim
• Customer and Engineering requirements
• Plane research to order
• Problem Design Review slideshow
• In a large group, ownership of deliverables is very important and trust must be earned between team members so that things don't have to constantly be bounced against the group
• Run preliminary Aero analysis on the glider
• Assemble the plane
• Order base parts as required
Michael Ostaszewski
• Formulated and updated Use Case plot
• Organized and updated EDGE website
• Team Values
• Problem Design Review Slideshow
• Project Summary page for Problem Definition
• Design projects require an extensive amount of planning
• Use cases aid in developing an understanding of the problem that needs to be solved
• When working in a team, it is more beneficial to divide and conquer rather than work on the same problem all together
• Simulate stress of plane on reel
• Determine how to keep tether taught on launch
• Base design brainstorming
Kevin Larkin
• Helped create and set up plans for next phase
• Helped to complete house of Quality
• Researched Benchmarking
• Risk Management on the slideshow
• Inquired about finding a park for testing flights
• That taking on a project this large takes much more planning than I was expecting
• I'd never used benchmarking or a House of Quality before so those were interesting to see
• If you don't have a clear plan it's very easy not to realize you are a bit behind
• Find place to fly
• familiarize self with RC controls
• untethered flight, go to aero club meeting
Sukmin Lee
• Managed EDGE website (updates and updates)
• Recording & edited Customer Interview
• Edited and reformed documentations for problem definition
• transformed documentation files into photo files in order to publish at EDGE website.
• help set the plans for next phase
• Communication between team members is very important
• Keeping update their status is essential to be in the same page
• If you are stuck on your current work, it is better to ask a help not wait until someone finds out
• Inspect incoming transmitter
• Run simulation program
• Learn how to assemble and disassemble electrical components of the plane