Low Altitude Balloon Experiment in Technology (LABET) Group Members – Richard George –...

Low Altitude Balloon Experiment in Technology (LABET)

Group Members – Richard George – Industrial TechnologyMike Svendsen – Computer EngineerSteve Towey – Computer EngineerBrian Walker – Architect

Advisor – Matt Nelson

Project Description

• The LABET project has been an ongoing project with the Space Systems and Controls Lab (SSCL) that aims at developing a blimp that can be flown for research and for outreach events for the SSCL.

• Past LABETs have been designed for indoor use only. • This project aims to develop a blimp system that can be

flown in outdoor conditions with winds under 10 mph. • Objective –

– Develop a new LABET frame – Develop new LABET avionics

RequirementsD/W Requirement

D R1. The LABET will fly at a maximum altitude of 500 feet.

D R2. The communication range shall be at least 1 mile.

W R3. The communication range should be at least 2 miles.

D R4. The LABET shall have a remote control.

D R5. The LABET shall have a weight of under 5 pounds.

D R6. The LABET electronics shall have a weight of under 1.5 pounds.

D R7. The LABET shall be able to carry a payload of 200 grams.

D R8. The LABET shall operate in wind speeds of up to 5 mph.

W R9. The LABET should operate in wind speeds of up to 10mph.

W R10. The LABET should be able to take and send video to a ground station.

D R11. The LABET shall have a flight time of 30 minutes.

D R12. The LABET shall have a pressure sensor to determine altitude.

D R13. The LABET shall have a GPS module to determine position.

D R14. The LABET shall have a rate gyro to keep it flying straight

Constraints and Technical Considerations

• All motors, electronics, and batteries must weigh under 1.5lbs.

• The motors must provide enough thrust to overcome 10 mph winds.

• Obtaining a small RF device that is still able to broadcast up to 2 miles.

On Board System Diagram

Frame Design

Balloon Design

Tasks/Schedule

ID Task Name Start Finish DurationOct 2010 Dec 2010Nov 2010Sep 2010

9/19 10/3 12/1210/319/26 12/511/14 11/219/5 9/12 10/1710/10 11/710/24 11/28

1 238d4/26/20119/1/2010LABET 6

4 29d10/5/20109/7/2010Research RC and Propulsion Systems

12d10/12/201010/1/2010Draft Project Plan

5 15d10/19/201010/5/2010Research RF, Sensors, Processors

6 15d10/19/201010/5/2010Decide on transmitter/receiver, sensors, processor

7 36d11/23/201010/19/2010Developing PCB

8 22d11/23/201011/2/2010Design program modules

9 11d12/3/201011/23/2010Draft Design Document

10 96d3/8/201112/3/2010Programming Microprocessor

11 14d12/16/201012/3/2010Control Logic

78d11/23/20109/7/2010Research and Construct Electronics

3

2

Tasks/Schedule

ID Task Name Start Finish DurationJan 2011 Feb 2011 Mar 2011 Apr 2011

1/9 1/16 1/23 1/30 2/6 2/13 2/20 2/27 3/6 3/13 3/20 3/27 4/3 4/10 4/17 4/24

2 96d4/15/20111/10/2011Programming Microprocessor

3 14d12/16/201012/3/2010Control Logic

4 14d1/23/20111/10/2011Altitude Controls

5 14d1/23/20111/10/2011Stabilize Logic – Rate Gyro

6 15d2/7/20111/24/2011Battery Level Monitor

7 14d2/21/20112/8/2011Receiving Logic

8 14d2/21/20112/8/2011Sending Logic

9 96d4/15/20111/10/2011Module Testing

10 29d4/5/20113/8/2011Programming Ground UI

11 7d3/14/20113/8/2011Google Maps

12 7d3/21/20113/15/2011Pressure Conversion

13 7d3/28/20113/22/2011Battery Display

14 21d3/28/20113/8/2011Controls

16 16d4/20/20114/5/2011Integration Testing

17 16d4/20/20114/5/2011Presentation Poster

15 29d4/5/20113/8/2011Module Testing

1 238d9/4/20111/10/2011LABET 6

Risks and MitigationRisk Mitigation

Schedule too aggressive The timeline for the subtasks is aggressive, but each overall task has extra time allocated for unexpected setbacks.

Lack of experience with RC devices. Research online and work closely with advisor.

Parts not performing as expected. Account for this and purchase slightly “overpowered” motors, so if they under perform requirements are still met.

Little experience with circuit board design and fabrication.

Work closely with advisor.

Cost Estimate

Questions?