2011 CoDR Team Name Preliminary Design Review University/Institution Team Members Date 1

2011 CoDR User Notes You can reformat this to fit your design, but be sure to cover at least the information requested on the following slides This template contains all of the information you are required to convey at the PDR level. If you have questions, please don’t hesitate to contact me directly:

2011 CoDR Purpose of PDR Confirm that: –Science objectives and required system performance have been translated into verifiable requirements –Design-to specification can be met through proposed design (trade studies) –Project risks have been identified, and mitigation plans exist –Project management plan is adequate to meet schedule and budget –Project is at a level to proceed to prototyping of high risk items 3 gnurf.net

2011 CoDR PDR Presentation Content 4 Section 1: Mission Overview –Mission Overview –Organizational Chart –Theory and Concepts –Concept of Operations –Expected Results Section 2: System Overview –Subsystem Definitions –Critical Interfaces (ICDs?) –System Level Block Diagram –System/Project Level Requirement Verification Plan –User Guide Compliance –Sharing Logistics

2011 CoDR PDR Presentation Contents Section 3: Subsystem Design –Subsystem A (i.e. EPS) SSA Block Diagram SSA Key Trade Studies (1 – 2?) Subsystem Risk Matrix/Mitigation –Subsystem B (i.e. STR) SSA Block Diagram SSA Key Trade Studies (1 – 2?) Subsystem Risk Matrix/Mitigation –Etc., Etc… 5 jessicaswanson.com

2011 CoDR PDR Presentation Contents Section 4: Prototyping Plan –Item “A” to be Prototyped –Item “B” to be Prototyped –Etc., Etc… Section 5: Project Management Plan –Schedule –Budget –Work Breakdown Structure 6

2011 CoDR Mission Overview Name of Presenter 7

2011 CoDR Mission Overview Mission statement Break mission statement down into your overall mission requirements What do you expect to discover or prove? Who will this benefit/what will your data be used for? 8

2011 CoDR Organizational Chart What subsystems do you have? Who works on each subsystem? –Leads? Don’t forget faculty advisor/sponsor(s) 9 Project Manager Shawn Carroll System Engineer Riley Pack CFO Shawn Carroll Faculty Advisor Chris Koehler Sponsor LASP Faculty Advisory Emily Logan Safety Engineer Chris Koehler Testing Lead Jessica Brown EPS David Ferguson Riley Pack STR Tyler Murphy Aaron Russert DEP Aaron Russert Shawn Carroll PM Kirstyn Johnson Elliott Richerson

2011 CoDR Theory and Concepts Give a brief overview of the underlying science concepts and theory What other research has been performed in the past? –Results? 10

2011 CoDR Concept of Operations Based on science objectives, diagram of what the payload will be doing during flight, highlights areas of interest Example on following slide 11

2011 CoDR Example ConOps t ≈ 1.3 min Altitude: 75 km Event A Occurs t ≈ 15 min Splash Down t ≈ 1.7 min Altitude: 95 km Event B Occurs -G switch triggered -All systems on -Begin data collection t = 0 min t ≈ 4.0 min Altitude: 95 km Event C Occurs Apogee t ≈ 2.8 min Altitude: ≈115 km End of Orion Burn t ≈ 0.6 min Altitude: 52 km t ≈ 4.5 min Altitude: 75 km Event D Occurs Altitude t ≈ 5.5 min Chute Deploys

2011 CoDR Expected Results 13 This is vital in showing you understand the science concepts Go over what you expect to find –Ex. What wavelengths do you expect to see? How many particles do you expect to measure? How well do you expect the spin stabilizer to work (settling time?)? How many counts of radiation? etc

2011 CoDR System Overview Name of Presenter 14

2011 CoDR Subsystem Overview 15 MCU Choice A Choice B Choice C Arm Control Choice A Choice B Temp. Sensor Choice A Choice B Photomultiplier Choice A Choice B PWR Wallops Telem Wallops EPS Photomultiplier 25 ⁰ FOV EPS/STR Interface PM/STR Interface DEP/STR Interface Booms Material Choice A Material Choice B Material Choice C Probe Provided by: LASP Control Box Choice A Choice B Choice C DEP/EPS Interface Photomultiplier Provided by LASP 25 ⁰ FOV PM/EPS Interface STR DEP PM

2011 CoDR Critical Interfaces 16 At the PDR level you should at minimum identify these interfaces Interface NameBrief DescriptionPotential Solution EPS/STR The electrical power system boards will need to mount to the RockSat-X deck to fix them rigidly to the launch vehicle. The connection should be sufficient to survive 20Gs in the thrust axis and 10 Gs in the lateral axes. Buckling is a key failure mode. Heritage shows that stainless steel or aluminum stand-offs work well. Sizes and numbers required will be determined by CDR. PM/STR The photomultiplier will need to mount to the RockSat-X deck rigidly. The connection should be sufficient to survive 20Gs in the thrust axis and 10 Gs in the lateral axes. Most likely, the PM will hang, and the supports will be in tension. A spring and damper support will need to be developed. The system should decrease the overall amplitude of vibration no less than 50%. DEP/STR The deployment mechanism must rigidly connect to the RockSat-X deck. The actuator has pre-drilled and tapped 8-32 mounts cap head screws will mount the deployment mechanism to the plate. The screws will come through the bottom of the plate to mate with the DEP system. DEP/EPS The deployment mechanism has a standard, male RS-232 DB-9 connector to interface to a motor controller (male), which is provided with the DEP mechanism. The motor controller will be controlled by EPS. A standard, serial cable with female DB-9 connector on both ends will connect the motor controller to the DEP mechanism. The motor controller to EPS system interface is yet to be determined. PM/EPS The photomultiplier requires 800V DC and outputs pulses at TTL levels. The PM also requires a ground connection. A TBD 2 pin power connector (insulated) will connect the EPS board to the PM. A separate, TBD connector will transmit the pulse train to the asynchronous line at a TBD Baud rate.

2011 CoDR System Level Block Diagram 17 Buck Converter Boost Converter uController WFF Power Interface WFF Telem. Interface Motor Controller EPS DEP PM Photomultiplier STR Wallops PT Interfaces Low Voltage High Voltage Data/ Control Legend

2011 CoDR Requirement Verification 18 At the PDR level you should highlight the most critical (Top3?) system and project level requirements and how they will be verified prior to flight. Requirement Verification Method Description They deploable boom shall deploy to a height of no more than 12” DemonstrationBoom will be expanded to full length in the upright position to verify it doesn’t exceed 12” The boom shall extend to the full 12” height in less than 5 seconds from a horizontal position. AnalysisThe system’s dynamical characteristics will be derived from SolidWorks, and available torques will yield minimum response time. The full system shall fit on a single RockSat-X deck InspectionVisual inspection will verify this requirement The sytem shall survive the vibration characteristics prescribed by the RockSat- X program. TestThe system will be subjected to these vibration loads in June during testing week.

2011 CoDR RockSat-X 2011 User’s Guide Compliance 19 Rough Order of Magnitude (ROM) mass estimate Estimate on payload dimensions (will it fit in the payload space?) Deployables/booms? How many ADC lines? –Do you understand the format? Asynchronous use? –Do you understand the format? Parallel use? –Do you understand the format? Power lines and timer use? –What do you know so far? CG requirement –Do you understand the requirement Are you utilizing high voltage?

2011 CoDR Sharing Logistics 20 Who are you sharing with? –Summary of your partner’s mission (1 line) Plan for collaboration –How do you communicate? –How will you share designs (solidworks, any actual fit checks before next June)? Structural interface – will you be joining with standoffs or something else (again, be wary of clearance)? grandpmr.com

2011 CoDR Subsystem Design Name of Presenter 21

2011 CoDR EPS: Block Diagram 22 Show the subsystem block diagram with primary component choices highlighted. Power Data/ Control Legend

2011 CoDR EPS: Trade Studies 23 Show rationale for you choices in components. You basically weigh your options against your requirements and what each component can offer. Don’t forget things like: availability, cost, and prior knowledge. µController XMegaATMega 32 L Cost 810 Availability 10 Clock Speed 105 A/D Converters 95 Programming Language 88 Average: 97.6 You should have completed a trade study for each block, but you only need to present the 2-3 most important. Numbers are relatively subjective, but 10 should represent a perfect fit, 5 will work, but is not desirable, and 0 does NOT meet expectations. The component with the highest average should drive your choice for design.

2011 CoDR EPS: Risk Matrix 24 Consequence EPS.RSK.1 EPS.RSK.3 EPS.RSK.4 EPS.RSK.2 Possibility EPS.RSK.1: Microcontroller fails in-flight, and the mission objects aren’t met EPS.RSK.2: A suitable motor controller cannot be procured to meet mission objectives EPS.RSK.3: The EPS system can’t survive launch conditions, and the mission objectives aren’t met EPS.RSK.4: Flying monkeys delay the launch by an hour putting a strain on the power budget Risks for the subsystem under discussion should be documented here. The horizontal represents the likelihood of a risk, the vertical is the corresponding consequence. Risks placement should help drive mitigation priority

2011 CoDR Prototyping Plan Name of Presenter 25

2011 CoDR Prototyping Plan 26 Concern about mounting the PM to the deck has been expressed STR PM DEP EPS Concerns about testing the PM on the ground have been expressed Mounting the probe to the end of the boom will present a significant challenge The functionality of the microcontoller board needs to be verified by CDR Prototype this interface and verify the fit with the PM Develop a test plan and verify it with LASP mentors Mount a test probe and verify structural rigidity Prototype the micro board on a bread board to verify functionality Risk/ConcernAction What will you build/test between now and CDR to mitigate risk?

2011 CoDR Project Management Plan Name of Presenter 27

2011 CoDR Schedule 28 What are the major milestones for your project? (i.e. when will things be prototyped?) CDR When will you begin procuring hardware? Think all the way to the end of the project! Rough integration and testing schedule in the spring Etc, etc, etc Format: Gant charts Excel spreadsheet Simple list Whatever works for you! Don’t let the schedule sneak up on you!

2011 CoDR Budget 29 Present a very top-level budget (not nut and bolt level) A simple Excel spreadsheet will do Simply to ensure that at this preliminary stage you aren’t over budget It is suggested that you add in at least a 25% margin at this point Margin:0.25Budget:$1,300.00Last Update:9/30/ :50 ExampleSat ItemSupplierEstimated, Specific CostNumber RequiredToal CostNotes Motor ControllerDigiKey$ $ for testing PMLASP$0.001 LASP mentor deserves shirt MicrocontrollerDigiKey$18.003$ board revs Printed Circuit BoardsAdvanced Circuits$33.003$ board revs Misc. Electronics (R,L,C)DigiKey$80.003$ board revs Boom Materialonlinemetals.com$40.002$ test article ProbeLASP$0.001 Testing Materials???$ Estimated cost to test system Total (no margin):$ Total (w/ margin):$1,216.25

2011 CoDR WBS 30 Present a very top-level work break down schedule One can look up the tree for large scope goals One can look down the tree for dependencies Help each subsystem “see” the path ahead PMPEPSSTRPMDEP Obtain PM from LASP EEF Proposal for funding … Trade Studies Schematics Schematic Review ICDs First Revision of Boards … Trade Studies Order Materials Work Request Into Shop … Obtain PM from LASP EEF Proposal for funding … Obtain PM from LASP EEF Proposal for funding …

2011 CoDR Issues, concerns, any questions Conclusion 31