1 / 28

Team Up, Up, and Away Final Presentation

Team Up, Up, and Away Final Presentation. Trevor Arrasmith, Ty Bailey, Cameron Coupe, Samuel Frakes, Brandon Harris, Carolyn Mason, Soo Park, Peter VanderKley 12/10/12. Mission Overview.

geri
Download Presentation

Team Up, Up, and Away Final Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Team Up, Up, and AwayFinal Presentation Trevor Arrasmith, Ty Bailey, Cameron Coupe, Samuel Frakes, Brandon Harris, Carolyn Mason, Soo Park, Peter VanderKley 12/10/12

  2. Mission Overview • The objective of team Up, Up, and Away is to prove the possibility and efficacy of a balloon-mounted mechanism for cloud seeding • Introduce a particle to clouds to induce precipitation • Normally done by plane or fireworks • Given the proper conditions and cloud seeding substance, a balloon-mounted system will prove a cost-efficient alternative to traditional methods

  3. Design Overview

  4. Design Overview

  5. Design Overview

  6. Functional Block Diagram

  7. Differences from Original Design: • - We flew two Arduino Unos instead of one • - Increased the size of the box • - Location of the batteries and heater • - Added wind gauge and chutes to direct salt Final Design Original Design

  8. Recovery

  9. Launch Events • Power on: 7:08 AM • Launch 7:10 AM • Burst: 8:57 AM • Landing: 9:30 AM (extrapolated from EOSS data) • Recovery: 12:13 PM • Flight time to apogee: 107 minutes • Average ascension rate: 326 m/min • Max Height: 30308.7 meters

  10. Altitude During Flight Apogee Launch

  11. Acceleration During Flight

  12. Internal and External Temperature Tropopause

  13. Pressure and Humidity Cloud Layer

  14. Wind Voltage During Flight Re-entry to thicker air Spinning quickly at launch Air too thin to get accurate readings

  15. Servos (14,500 meters)

  16. Battery Voltage

  17. Failure Analysis What failed: Servo 2 did not open Both Arduino 1 and 2 stopped recording data for a given time

  18. Failure Analysis Why it failed: The battery supplying power for Servo 1 and 2 lost power during flight Loose wiring during decent caused power supply failure

  19. Failure Analysis How we know: After recovery the power supply to the Servos had dropped from 6 volts to 2.4 volts Determined from the GoPro audio, Servo 1 was stuck and drained power from battery by trying to re-position itself Both Servos worked properly when given new power supply We were able to recreate the Servo jam in ground testing

  20. Failure Analysis How we know: During decent we had small, zero-second files indicating power supply shorts Power came back to the Arduinos after decent All switches were still on at recovery and batteries could supply power Other teams recorded their Arduinos working in cold temperatures, so failure due to cold internal temperatures was ruled out

  21. Conclusions • Our mechanism for cloud seeding was successful and it is also reusable • We saw the release of the salt on the GoPro footage • We saw that the program wrote the Servo events to the SD Card • We discovered that it is possible to cloud seed from a balloon-mounted device • Our mechanism was very cost-effective

  22. Conclusions • Our data told us that it is possible to relate the release of the salt to humidity, time and altitude • We saw that the salt did not clump due to condensation • Environmental data was what we expected

  23. Ready to Fly Again • Fresh batteries • Re-secure wiring and power connections • In particular the environmental data Arduino • Clear SD cards • Refill salt funnels • Re-seal box • Should be stored upright in a dry, room-temperature environment • Activated by external switches and camera buttons (activated with the “Activation Stick”

  24. Lessons Learned General Lessons: • Secure and re-secure each component • Even LEDs need resistors • Don’t be afraid to use both Arduinos • Don’t confirm mass budget last minute For Results: • Test and retest all components • Ensure that the programming runs consistently

  25. Compliance with RFP • All required sensors recorded flight data • Additional sensor (anemometer) • Digital camera • Switches to turn on power • Lights to indicate power is running • Exceeded original mass budget but with prior approval • Did not exceed budget of $250 • American flag sticker and contact information • Returned in working condition • Inside of box stayed above -10 degrees Celsius

  26. Mission Requirement Matrix

  27. Mass and Money Budgets

  28. Messages to Next Semester • Be prepared to do a large amount of work • Be creative with your design but keep it simple • Make a detailed test plan, the earlier the better • Get help from Tim May and from Space Grant • Leave lots of time for failures with your satellite • Work as a team

More Related