1. MINNROCK CONCEPTUAL DESIGN REVIEW University of Minnesota William Ung Scott Balaban Tom Thoe Bryce Doug Carlson 11/14/2008

2.  Mission Overview (spend a lot of time here-Multiple Slides)  What is your objective?  What do you expect to prove, discover, or learn from your experiment?  Brief overview of underlying science/theory  What other related research/experimentation has been done in the past? Results?  Mission Requirements **NOTE: This can be a more refined rendition of the corresponding CoDR slides. Don’t plan on spending lots of time during the review here unless your mission has changed significantly

3. Objectives  To build a sensor package to characterize the flight of the rocket  To record changes in the magnitude of Earth’s magnetic field with respect to height  To record raw GPS data to plot 3-dimensional course of rocket and to see if it is possible to gather such data  To measure the spin rate of the rocket with an array of light sensors

4. Results  The conditions which will be experience by a payload on similar flights  Whether it is possible to record GPS data with the given conditions  Determine how the rocket’s trajectory changes over time  To determine the amount of light sensors that are necessary to calculate spin rate

5. Science Theory  The accelerometers, pressure sensor, temperature sensor, light sensors, vibration sensors, and camera will all record the environment over time. This will allow other payloads to design to meet these conditions. Accelerometers may be sampled at a rate high enough to allow them to function as vibration sensors, minimizing mass.  The magnetometer and GPS receiver will record data to test the possibility of recording such data from suborbital rockets.

6. History  RockOn! Workshop summer ’08 used identical accelerometers, similar pressure sensor, and had a temperature sensor  Results: A partial characterization of the flight. Accelerations were recorded, along with temperature, but pressure was beyond the sensor’s capability, and vibration was not recorded.  Spacecraft Senior Design ’08 designed a payload for a suborbital rocket to characterize the flight  Results: This design was a conceptual payload design and was never built.

7. Requirements  Weight: 4.25lbs  Center of Gravity is within.1x.1x1 inch (x,y,z) of the center  Max Height: 3.1 inch  Max Diameter: 9.2 inch  Withstand 20Gs in Z-direction and +/- 10 Gs in the X- and Y-directions  Self contained power system  No current flowing before rocket ignition  All sensors must not cause electromagnetic interference

8.  Subsystem Requirements - What subsystems do you have: power, C&DH, thermal, etc. - Power - Design Driver: Supply enough power for sensors (exact power required is unknown right now) - Power subsystem is required to be able to withstand a minimum temperature of 32 F and a maximum of ~150 F - Camera/Light Sensors - Face optical port - GPS - Antenna must be close to optical port

9. Special Requirements  The MinnRock team requires the dimensions of the optical port itself to configure sensors

10. Functional Block Diagram Vibration Sensors Power G- Switch

11. G-Switch Configuration From Power Supply To Sensors

12. Mechanical Drawings  There are currently no mechanical drawings of the payload because the masses of the sensors, etc., are not available. After sensors are purchased, a mechanical drawing will be available. The only requirements so far for the mechanical payload can be found on the “Requirements” slide.  While no drawing yet exists, we are working with the University of Wyoming to configure structural supports and dimensions of payloads.

13.  Commands and Sensors - Since the computer and connections are still being configured to our needs, we don’t know what states our payload will be in other than: Stand-by, ready to activate once the G-switch is activated; and Active, actively taking data. - The key items that we are looking for are data flow diagrams and budgets - Memory budgets – - We will be using at least one 2 GB SD card - How many samples, how long, do you have enough memory? - Sample frequencies and memory space calculated on memory slide - Where is data stored? - Flash memory SD card - How does the data get there? – - Sensors output analog, received by microcontroller, add time stamp, output to flash SD - What commands queue data acquisition?

14. Data Storage Requirements 400 Hz300 Hz200 Hz100 Hz50 Hz10Hz 1 input1.44 MB1.08 MB0.72 MB0.36 MB0.18 MB0.036 MB 20 inputs28.8 MB21.6 MB14.4 MB7.2 MB3.6 MB0.72 MB 14 2 bytes per sensor output data 19 sensors input 1 time stamp input 30 minutes per flight ( 15 minute safety factor) Memory = 2 (byte/input) * (20) (inputs) * 1800 (sec) * Freq. (samples/sec) C&P - William - This does not account for the video file - 2 GB SD card with high write speed

15. Test Plans - What type of testing can be performed on your payload pre-flight? - Mock can to test GPS unit and antenna and G-Switch - What is required to complete testing?: - Support Hardware - Purchase/borrow antenna - Purchase/receive from faculty the GPS unit - Connection cables are available to record data onto a computer - Software - Unknown, but a current faculty with the University of Minnesota researches GPS, and will be providing guidance and software for our team - Potential points of failure – G-switch doesn’t activate, G-switch cuts off power, short circuit, wires come loose, memory buffer overflow, memory shortage, - Testing/Troubleshooting/Modifications/Re-Testing Schedule – - Mock capsule should allow us to discover all likely problems with package. Multiple iterations of the mockup capsule test will be performed as necessary

16. Major Parts

17.  RockSat Payload Canister User Guide Compliance  Mass, Volume Estimated fraction of allotment vs. assigned fraction: 3.5lbs/4.25lbs Estimated volume: around 105 in 3, but definitely <210 in 3  Payload activation? G-switch activation Has been used in previous RockOn! workshop to activate payloads  Rocket Interface Shorting wires

18.  Shared Can Logistics Plan Update Chris and I on RSPC sharing logistics since CoDR  University of Minnesota  University of Wyoming (2 teams)  Plan for collaboration on interfacing Email correspondence The MinnRock team has the middle third of the can (includes access to the optical port)  Posts similar, if not identical, to the RockOn! workshop of 2008 will connect and support the payloads. Same posts will be used to the top and bottom bulkheads

19.  Management  Updated Organizational Chart  Updated Schedule  Updated mass/monetary budgets

20. Gantt Chart We are using a Gantt Chart and schedule provided in the RockOn! User’s Manual for scheduling

21. Schedule  08-18-2008 RockSat Payload User’s Guide Released  09-08-2008 Submit Intent to Fly Form  09-12-2008 Initial Down Selections Made  09-30-2008 Online Progress Report 1 Due  10-10-2008 Earnest Payment of $1,000 Due  10-15-2008 Conceptual Design Review (CoDR) Due  10-30-2008 Online Progress Report 2 Due  11-14-2008 Preliminary Design Review (PDR) Due  11-28-2008 Online Progress Report 3 Due  12-12-2008 Critical Design Review (CDR) Due  12-19-2008 Final Down Select—Flights Awarded  01-23-2009 First Installment Due ($5,500)  01-30-2009 RockSat Payload Canisters Sent to Customers

22. Schedule (cont.)  01-30-2009 Online Progress Report 4 Due  02-20-2009 Individual Subsystem Testing Reports Due  02-27-2009 Online Progress Report 5 Due  03-27-2009 Payload Subsystem Integration and Testing Report Due  04-10-2009 Final Installment Due ($5,500)  04-17-2009 First Full Mission Simulation Test Report Due  04-30-2009 Online Progress Report 6 Due  05-22-2009 Second Full Mission Simulation Test Report Due  05-29-2009 Online Progress Report 7 Due  06-10-2009 Launch Readiness Review (LRR) Teleconference  06-(22-24)-2009 MOI and Vibration Testing at WFF  06-24-2009 RockSat Payload Canister Integration with WFF  06-26-2009 Launch Day

23. Mass/Monetary Budget  Mass Budget: 4.25 lbs  Monetary Budget: $5000  Includes equipment to build  Includes spares for multiple flights/failures

24.  Conclusions  The MinnRock team is still looking for Computer Engineers to assist with the team which makes computer and general electrical layouts difficult to produce. A possible Computer Engineer has been referred to us, and we are hoping he will join.  The team will hopefully be able to begin testing on a mockup of the MinnRock payload soon.