280 likes | 432 Views
Fall 2010 Rev D 11/2/2010. Team Lightning Rod Final Presentation. 11/30/2010. Trevor Luke Chris Bennett Matt Holmes Sushia Rahimizadeh Alex Shelanski Matthew Dickinson Jesse Ellison. Mission Overview. Objective
E N D
Fall 2010 Rev D 11/2/2010 Team Lightning RodFinal Presentation 11/30/2010 Trevor Luke Chris Bennett Matt Holmes SushiaRahimizadeh Alex Shelanski Matthew Dickinson Jesse Ellison
Mission Overview • Objective • To determine if future spacecraft will be able to utilize energy generated by vibrational and rotational motion as additional energy sources • To determine if more energy can be generated from vibrational motion or rotational motion • What we hope to prove and discover • A significant amount of energy can be produced from the motion of the satellite • A satellite can generate enough energy to power some systems • Hypothesis • Rotational motion will produce more energy than vibrational motion • Why we are doing this mission • To develop an alternative method of generating power for spacecraft
Functional Block Diagram Storage Hobo Electromagnetic Generator Electromagnetic Generator Camera Power Battery Pack Switch Switch Heater Power Actual Flight
Launch Recap • Last minute adjustments during drive to launch site • Jesse launched satellite • Total flight time 2 hrs. 15 min. • Entire team retrieved satellite • Rotational Generator broke during flight • Vibrational Generator produced energy
Us gathering the voltage data Interior of Box after recovery
Results Expected Actual • Energy output (could not determine without accurate acceleration data) • Rotational Generator produce more energy than Vibrational Generator • Rotational Generator produced 0 joules • Vibrational Generator produced 4.76 kJ
Analysis • Did the generators capture energy? • Rotational Generator was damaged • Can assume that battery voltage increase was negligible • Vibrational Generator survived • Increased the battery voltage • Vibrational generator was completely responsible for battery pack voltage increase
DATA • Battery pack initial charge: 3.84 V • Battery pack final charge: 4.02 V • Increase: 0.18 V • 0.18 V increase on 7350 mAh pack • Translates to 1.323 Watt-Hours • Total electrical energy captured: 4672.8 J
Battery Arrangement • Asymmetrical
Reversed Battery Why didn’t it drain? Diode turn on threshold not reached
Temperature Burst
Failure Analysis • Computer Program • Mechanical failure of rotational generator • Temperature and humidity had no effect • Suspected failure prior to launch • Believed that rotor got jammed while assembling satellite • No motion, no energy captured
Recreating our Failure Recreating the Rotational Generator failure: We reattached the battery pack inside the satellite and attempted to simulate flight We calculated the time it took for the battery pack to fall We knew from the cold test that if a battery fell during flight, it would destroy the rotational generator and no energy would be produced. The battery pack fell off extremely quickly, making us believe it could’ve happened early in flight, thus the reason for the Rotational Generator Failure.
Recreating our failure Battery pack fell
Conclusions Both generators produce energy on ground The Vibrational Generator was successful and produced energy The Rotational Generator faced complications and failed during flight, thus producing no detectable energy
Lessons Learned Understand what data needs to be collected and start programming ASAP Manage time better (stick to the schedule) Have more buffers for failure Experiments that seem simple take more work and troubleshooting than expected. Simplify experiment as much as possible. Building your own components, even if it sounds simple, isn’t… ever. Utilize resources, especially people
Re-flight The payload should be stored anywhere that the magnetic fields within it will not interfere with its surroundings The payload can be activated by a switch. To fulfill the original design requirements, the satellite needs to be rewired, and the program finished
Message to Next Semester Dear next semester, Schedule to finish a few weeks ahead of time to leave time for troubleshooting. Understand what data is being collected and start programming at least a month before launch. Start all aspects of the project early because certain aspects will take more time than is expected. If experiment requires homemade components, stay up late to get them finished rather than put them off till ‘tomorrow’ because they will need modification. Divide into pairs and work on different aspects of the project, then go over everyone's work during weekly meetings. Set aside at least 10 hours per week to work on project. Do not take this course if you cannot make the time commitment. Your team-mates can’t afford to have members who do not carry enough of their own weight.